Unbound won't start 26.1.1 ->

Started by iddqd, March 04, 2026, 05:20:29 PM

Previous topic - Next topic
No problem. If it is some upgrading error, that wouldn't explain that the clean install from 26.1.1 image didn't work, no? I can try fresh install from the latest image later.

root@OPNsense:~ # find /var/unbound/unbound-dnsbl -type f -name "*.pyc"
/var/unbound/unbound-dnsbl/lib/__pycache__/log.cpython-313.pyc
/var/unbound/unbound-dnsbl/lib/__pycache__/dnsbl.cpython-313.pyc
/var/unbound/unbound-dnsbl/lib/__pycache__/utils.cpython-313.pyc
/var/unbound/unbound-dnsbl/lib/__pycache__/__init__.cpython-313.pyc

At this point it seems that this is a more fundamental OS/Python issue than update related. We've found forum posts from the past regarding similar issues. Not a lot of clues on why this happened, but they all seem to have tainted Python load orders.

Did you install anything via pip?  Just trying to find out what's wrong that the audits aren't telling us.


Cheers,
Franco

24 and 25 versions worked well and upgrading to 26.1 went smoothly. Problems started after upgrading 26.1.1. I thought something went wrong when upgrading so I did a fresh install with 26.1.1 image, but got the same problem and error messages. Then I did fresh install with 26.1 image and everyhting worked. Tried upgrading from 26.1 to 26.1.2 and 26.1.3, but the same problem persist. All with defaults and nothing extra installed. 26.1 is the last working image.

Today at 03:01:28 PM #18 Last Edit: Today at 03:03:18 PM by franco
My theory is if you do an "opnsense-bootstrap" the error will persist through a complete reinstall, which means it's a local issue with some stray file left for whatever reason and not a global one.

It's worth a try but chances are it doesn't help.

Just as an additional data point:

> community/24.7/24.7:OpenVPN DCO support, FreeBSD 14.1, Python 3.11 plus much more.

So we've had 3.11 for 1,5 years in total which roughly matches your "24" and "25" were working.

Cheers,
Franco

Downloaded the latest image OPNsense-26.1.2-vga-amd64.img and created bootable usb. Installation went ok, but the problem persist.
Guess I go back with OPNsense-26.1-vga-amd64.img and wait for a fix.

Thanks

I'd suggest migrating your dhcp handling to kea and disabling dnsmasq entirely and seeing if that fixes your issue. Depends on how much work it'd take.

@iddqd

Can you unplug everything from your firewall for 10 minutes -including power cable- before making another attempt?

My OPNSense complained about an "unknown error" but I cannot find the log of it yet. Any pointers to reviewing logs for upgrades welcomed!!

My upgrade did work however, and I have modded my OPNSense a little out-of-band.
Custom: ASRock 970 Extreme3 R2.0 / AMD FX-8320E / 32 GB DDR3 1866 / X520 & I350 / 500GB SATA