Hi,
My unbound service won't start after upgrading from 26.1 to 26.1.1. I tried it with a clean install, but the same problem persist. I also tried upgrading to 26.1.2 and 26.1.3 with no success.
Unbound logs shows these error messages:
2026-03-04T17:01:08 Critical unbound [86957:0] fatal error: failed to init modules
2026-03-04T17:01:08 Error unbound [86957:0] error: module init for module python failed
2026-03-04T17:01:08 Error unbound [86957:0] error: python exception in Py_InitializeFromConfig: Failed to import encodings module
My machine is Protectli V1211 with coreboot firmware v0.9.4.
Any ideas?
Any extra repositories enabled? The normal reboot did go through? Anything in the health output?
I assume this is part of the Python 3.13 switch.
Cheers,
Franco
Can you grab "opnsense-update -g" output for me?
Thanks,
Franco
No extra plugins. Installed 26.1 image and everything works with defaults. Upgrade to 26.1.3, machine reboots and everything else works, but unbound is stopped and wont's start manually from gui.
thanks
Isn't the default DNSmasq, now?
Quote from: iddqd on March 04, 2026, 06:38:34 PMNo extra plugins. Installed 26.1 image and everything works with defaults. Upgrade to 26.1.3, machine reboots and everything else works, but unbound is stopped and wont's start manually from gui.
thanks
What is the output of
opnsense-update -p
root@OPNsense:~ # opnsense-update -p
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (74 candidates): 100%
Processing candidates (74 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: 100%
Nothing to do.
Flushing temporary package files... done
pkg install -f unbound
See if unbound starts after, and please post the full output from the reinstall command above
Installed and rebooted but the problem persist. Same error messages.
root@OPNsense:~ # pkg install -f unbound
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):
Installed packages to be REINSTALLED:
unbound-1.24.2_1
Number of packages to be reinstalled: 1
2 MiB to be downloaded.
Proceed with this action? [y/N]: y
[1/1] Fetching unbound-1.24.2_1.pkg: 100% 2 MiB 1.6MB/s 00:01
Checking integrity... done (0 conflicting)
[1/1] Reinstalling unbound-1.24.2_1...
===> Creating groups
Using existing group 'unbound'
===> Creating users
Using existing user 'unbound'
[1/1] Extracting unbound-1.24.2_1: 100%
root@OPNsense:~ #
Perhaps I did not make myself clear: is DNSmasq already running and listening on ports 53 TCP and UDP so Unbound cannot start up?
Yeah that wasn't clear for me.
I don't think unbound would fail with those errors in case other service is running on 53...
Unbound is still the default resolver. Dnsmasq does DHCP and local DHCP client hostname resolving to Unbound.
At first glance I don't see why a new install would fail. But also didn't see a health audit or update log.
Cheers,
Franco
Quote from: franco on March 04, 2026, 09:25:56 PMUnbound is still the default resolver. Dnsmasq does DHCP and local DHCP client hostname resolving to Unbound.
Good to know, thanks.
Quote from: franco on March 04, 2026, 09:25:56 PMUnbound is still the default resolver. Dnsmasq does DHCP and local DHCP client hostname resolving to Unbound.
At first glance I don't see why a new install would fail. But also didn't see a health audit or update log.
Cheers,
Franco
I posted those as an attachement earlier, because of the charatcter limit exceeded.