NetBox DNS 0.21.8 is compatible with NetBox 3.7 out of the box #118
Replies: 9 comments 5 replies
-
I'm running NetBox 3.7 and ran into some issues with ipam-coupling. Basically netbox keeps restarting when I enable this feature. It works fine as soon as I disable it. I'm new to the plugin, but I think it's all setup correctly. |
Beta Was this translation helpful? Give feedback.
-
I'm not so sure, at least it definitely isn't a general issue. Can you please provide
We'll find out what's wrong and where. |
Beta Was this translation helpful? Give feedback.
-
Thanks for getting back to me so quickly! I wanted to spin up a new dev instance to see if issue persists with a fresh install and no existing data. Appreciate the plugin and support :) |
Beta Was this translation helpful? Give feedback.
-
Hi @bitcollector1, I'm pretty sure it will work - but it also should do so with existing data, if NetBox keeps restarting there's something seriously wrong and it should not depend on data in the database, at least not the IPAM coupling stuff (which is just some data in custom fields and some object relations, after all). |
Beta Was this translation helpful? Give feedback.
-
Okay, it;s looking like I've got some issues on my end I need to sort through. I've been running into this error in GUI fairly often as of late --> FATAL: remaining connection slots are reserved for non-replication superuser connections restarting the service seems to be the "band-aid" but it usually comes back :( Looks like I have some issues to fix on my end that I was not aware of. pretty sure these are the error messages from when I enabled the plugin
|
Beta Was this translation helpful? Give feedback.
-
That looks like a misconfiguration on the PostgreSQL end - how is your database configured? It could also be a very high configured number of workers for |
Beta Was this translation helpful? Give feedback.
-
looks like that fixed my issue, wanted to say thanks again for everything :) I can now see the IPAM IP Address has been created for the new entry! |
Beta Was this translation helpful? Give feedback.
-
You're welcome, glad I could give some useful hints :-) |
Beta Was this translation helpful? Give feedback.
-
One more thing: PostgreSQL does not really like it if you are running too many connections in parallel, which has both performance impacts and high resource requirements (especially RAM). If you really need such a high number of workers, you should possibly look into connection poolers like |
Beta Was this translation helpful? Give feedback.
-
I just ran the test suite with a database updated from 3.6.7 to 3.7 and all tests succeeded. Same result with a fresh 3.7 database.
Beta Was this translation helpful? Give feedback.
All reactions