OPNsense Forum

Archive => 21.7 Legacy Series => Topic started by: lukepower on October 05, 2021, 08:16:49 am

Title: Error when upgrading from 21.1 to 21.7
Post by: lukepower on October 05, 2021, 08:16:49 am

Hi there,

I wanted to document what happened to our installation of Opnsense while upgrading to the latest version.
Let me start that, at the end, I had to reinstall, but the configuration has been imported from the system so it was quick and painless - nice feature, btw  :)

So, I started the upgrade as ofthen through the web interface and all went seemingly smoothly.
After the first reboot, the system didn't come back online, so I checked. The console was full of errors, with the mayor seemingly a Python error (more on this later) and the complaint, that systemd is not running. I was able to get to a shell, but with no internet connection and my limited experience on FreeBSD, I was not able to do much.

One of the errors that I saw was a Python error, while running /usr/local/opnsense/service/configd.py, complaining about a missing module "jinja2". Goinbg at it with the "pkg" package manager, there were several missing Python modules marked as required but not installed. And, as I had no connection, I decided to reinstall.

Maybe this was only a localized issue, but I still wanted to report it. If there are any logfiles that could be helpful please let me know and I will gladly collect anything usable.

best regards
Lukas

Title: Re: Error when upgrading from 21.1 to 21.7
Post by: franco on October 05, 2021, 09:30:08 am

Hi Lukas,

> that systemd is not running.

Maybe you mean configd, and that's normal during upgrades...

> complaining about a missing module "jinja2".

That is a FreeBSD package manger ordering issue with 21.1 -> 21.7 transition due to Python version (essentially a new package with fresh dependencies) change. It deinstalls old Jinja2 for Python 3.7 but does not yet install Jinja2 for Python 3.8.

But again, since configd is irrelevant during upgrade runs this doesn't matter.

Which begs the question what else was wrong... The answer usually lies with manual package installs from FreeBSD (introduces incompatibilities), from ports tree (can introduce stale dependencies) or third party repository usage with overlapping packages. Other problems could be e.g. lack of available disk space.

Does any of the latter might make sense here?


Cheers,
Franco