-
Hi everyone, I just took over a NetBox install from a previous employee and it hasn't been upgraded for over a year. It's currently running 2.10.5 and I am trying to get it upgraded to the latest. The server is Ubuntu 20.04.2 LTS and has Python 3.8.10 and PostgreSQL 12.9. I'm following the process in this video and I am stuck at the error:
Attached is the full log. netbox upgrade attempt.txt I've seen some other people run into this same error and it seems like it has to do with a incompatible version of MarkupSafe but when I try to downgrade it, I run into the same problem. I first tried to upgrade from 2.10.5 to 2.10.6 and also tried going straight to 2.11.12 and ran into the same issue. I read that some folks just give up and create a new instance of 2.11.12, import their database, and then do the upgrades but I'd like to avoid that if possible. I'm a network admin and don't have much Linux experience so I'm hoping someone can help me out or point me in the right direction. Thanks, Scott |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Thanks for providing the full log, as it makes it clear what's happening. You're running some script (that you found on the Internet?) that outputs some shell commands. You're then blinding pasting that in, all at once, and ignoring all the errors it returns. I suggest you try pasting it one line at a time, looking at the errors returned from that command, and fixing them before proceeding to the next one. For example, the first command:
generates the following response:
There's a strong clue as to what is happening. Why do you think it might be? Once you've understood that, it should be pretty clear why the next command fails:
Response:
If you don't understand any of the above, then I think you'd be best served by a local friendly sysadmin who can help you step through it line by line.
It's a safe and robust approach. It's certainly less risky than an in-place upgrade, which can leave your system in a broken state if something goes wrong (although if you have VM snapshots that you can roll back to, that mitigates the risk) |
Beta Was this translation helpful? Give feedback.
Thanks for providing the full log, as it makes it clear what's happening.
You're running some script (that you found on the Internet?) that outputs some shell commands. You're then blinding pasting that in, all at once, and ignoring all the errors it returns.
I suggest you try pasting it one line at a time, looking at the errors returned from that command, and fixing them before proceeding to the next one. For example, the first command:
generates the following response: