Not a smooth upgrade this time...

[skywalker007]

I think I have been spoiled by all the smooth upgrades I had in the past. This time it was all but smooth.
The server went unresponsive multiple times (had to hard-reboot), web gui not responding, LAN interface got unresponsive after a few minutes being up. I finally have it running now, but still occasionally can't connect to the web UI.
I have submitted a crash report. What else can I do to help?

I also now have this error message popping up in backend log every hour:

Code: [Select]

[07bbd436-4c8f-446a-9205-24455d9ba5f5] Script action stderr returned "b'Traceback (most recent call last):\n File "/usr/local/opnsense/scripts/OPNsense/Zenarmor/sensei-db-version.py", line 11, in <module>\n from packaging import version\nImportError: cannot import name \'version\' from \'packaging\' (unknown location)'"Is Zenarmor fully supported with this release?
Thank you for your great work!

[lshantz]

I did an audit in System/Firmware Status/Security and it looks like there some serious issues:
OPNsense repository update completed. 863 packages processed.
All repositories are up to date.
Checking connectivity for host: mirror.sfo12.us.leaseweb.net -> 2605:fe80:2100:b001::5187
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/23.7
Updating OPNsense repository catalogue...
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/23.7/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/23.7/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/23.7/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!

[skywalker007]

That doesn't look related to my problem. Did you check you can resolve these addresses?
I can:

Code: [Select]

> set q=AAAA
> mirror.sfo12.us.leaseweb.net
Server: 2003:e6:7744:8501:242:43ff:feae:1c
Address: 2003:e6:7744:8501:242:43ff:feae:1c#53

Non-authoritative answer:
mirror.sfo12.us.leaseweb.net has AAAA address 2605:fe80:2100:b001::5187
So it might be a DNS problem on your end.

[lshantz]

Yes, I can go to the site directly, but here is what an audit says:
hecking connectivity for host: mirror.sfo12.us.leaseweb.net -> 2605:fe80:2100:b001::5187
ping: UDP connect: No route to host
Checking connectivity for repository (IPv6): http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.1
Updating OPNsense repository catalogue...
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.1/latest/meta.txz: Non-recoverable resolver failure
repository OPNsense has no meta file, using default settings
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.1/latest/packagesite.pkg: Non-recoverable resolver failure
pkg: http://mirror.sfo12.us.leaseweb.net/opnsense/FreeBSD:13:amd64/24.1/latest/packagesite.txz: Non-recoverable resolver failure
Unable to update repository OPNsense
Error updating repositories!