Replies: 9 comments 23 replies
-
|
Converted to a discussion as it's more tech support than bug report. A good place to start would be to post the error log. Check with something like |
Beta Was this translation helpful? Give feedback.
-
|
You might want to redo the ngnix steps from the installation documentation as the OS upgrade might have overwritten some config files. |
Beta Was this translation helpful? Give feedback.
-
|
If I had to guess without seeing the error, I'd say it's likely that the version of python is different between Ubuntu 21.10 and Ubuntu 22.04. If this is the case, then the solution is to re-run However, seeing the error from |
Beta Was this translation helpful? Give feedback.
-
|
Here is the log file from running $ journalctl -eu netbox |
Beta Was this translation helpful? Give feedback.
-
There's your error: you have requested a plugin "netbox_topology_views" in your configuration.py, but you haven't installed it. The best solution is to list the extra packages you want in |
Beta Was this translation helpful? Give feedback.
-
|
So what exactly do I need to do to resolve this. Sorry but I am a total Linux novice. |
Beta Was this translation helpful? Give feedback.
-
|
This is what I have now after fixing what I can. Netbox service still will not start. $journalctl -eu netbox |
Beta Was this translation helpful? Give feedback.
-
|
Can anyone assist me on resolving this? |
Beta Was this translation helpful? Give feedback.
-
|
You've somehow broken it in a way that even the error message doesn't display what's wrong (unless you've truncated the response to hide the real reason above). Probably best at this point to reinstall from scratch. If you take a backup of your postgres database first, and restore it into the new instance, you'll be able to keep your data. This process is documented under "replicating netbox". If you're not confident with Linux, then maybe you need to find someone locally to help you. |
Beta Was this translation helpful? Give feedback.
-
|
Since the last notes from Sucram92, We've managed to find a few more missing modules from when Python was upgraded from 3.8 to 3.10 during the upgrade. We inherited this netbox implementation from a previous sysadmin and have been struggling. The upgrade was triggered unintentionally from a previous sysadmin who didn't realize there were no backups of the server so we are kind of between a rock and a hardplace. We don't have any documentation that we've been able to find regarding which packages might have been part of the original installation... Would it be as easy as checking that "configuration.py" to see what other additional modules might have been part of that install and just migrate them to the new 3.10 folders? I know the error message are a little unclear at this point but I suspect that there was a simple step or two missed during the upgrade where the database didn't get it's new tables and or we missed some python modules during the python upgrade sort of situation... Any suggestions on what direction to take this would be appreciated. Current status of the journalctl command being run is now this: $ journalctl -eu netbox |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for that. I need to stop and read the full thing. Here is the Diff from your commands above: I'm back to the Checkout 2.11.12 version. |
Beta Was this translation helpful? Give feedback.
-
|
No idea what that "sentry_sdk" stuff is about, but later version of Netbox do configure it. I think maybe settings.py got copied from somewhere else. Anyway, ignore. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. So then if I have it reverted to the 2.11.12 version and run the upgrade script with that 3, 8 entry in there you think we might push past that: Then we should be able to push past that first error where it is looking for 3.6 or greater? Thoughts? I'm thinking if we get that far and still have issues, I'll head to the postgres back up restore idea. What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
So at the end of the day here. I had to modify that settings file as follows: I don't think the second section was needed but basically wanted to ensure that in the two places checking the python version that it ignored the versions. I ran the upgrade script and it completed successfully. Once it completed successfully. I did a Your suggestion of using: Didn't work. It didn't like the sys.version method of checking the version. But even using the if platform that was there, it still didn't like 3, 8 for version number... so once we did 3, 10 like I noted above it worked. I know I took up a good chunk of your day @candlerb but I really appreciate the help. While I know my way around linux pretty decently, Netbox is a new app for me. It's nice to have had a friend help me out with understanding what I was looking at for this one! If there's a way to upvote you for the right answer in here, just let me know. You helped tremendously! -Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
Glad it worked. Once you got to v2.11.12 I was going to suggest you tested that version, then took a backup of the database at that point, before moving to v3.4.2. Now make sure you take backups regularly! :-) There is documentation here. I use a very simple script run from cron daily: ... but better if you can do that on a remote host - or copy the backup to a remote host after you've done it. And don't forget to backup the media, scripts and reports directories, if you are using them. |
Beta Was this translation helpful? Give feedback.
-
Any plugins will be listed in the PLUGINS section of configuration.py. Conversely, anything not listed in configuration.py won't be loaded.
That looks very broken. What happens if you try running Netbox in development mode? EDIT: Ignore that, if your migrations haven't completed properly then the database is in an intermediate/broken state so there's no point trying to run Netbox. |
Beta Was this translation helpful? Give feedback.
-
|
I'm assuming you've gotten a good chunk of the spam from us today. If you have an opportunity to mark the case as closed and hand out any points to @candlerb, please do. We managed to get that box up and running again after a good chunk of troubleshooting on all sides.... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
NetBox version
v2.9.7
Python version
3.10
Steps to Reproduce
Hello I recently upgraded my Ubuntu Server from 21.10LTS to 22.04LTS and it has broken Netbox.
Error I get when loading the page post upgrade is Error 502 bad gateway nginx/1.18.0 (Ubuntu)
Expected Behavior
For the webpage to load as expected with no errors
Observed Behavior
netbox.service - NetBox WSGI Service
Loaded: loaded (/etc/systemd/system/netbox.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Mon 2022-10-17 19:11:31 MDT; 23s ago
Docs: https://netbox.readthedocs.io/en/stable/
Process: 7339 ExecStart=/opt/netbox/venv/bin/gunicorn --pid /var/tmp/netbox.pid --pythonpath /opt/netbox/netbox --config /opt/netbox/gunicorn.py netbox.wsgi >
Main PID: 7339 (code=exited, status=1/FAILURE)
CPU: 1.031s
Beta Was this translation helpful? Give feedback.
All reactions