You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unbound DNS service repeatedly crashes due to Python mounting issues within the chroot environment. Service restarts are required multiple times per day to maintain DNS resolution.
Core symptoms:
Unbound service fails 1-2 times daily requiring manual restart
Python mount errors in logs related to the chroot environment
Issue persists even with DNS Blocklist functionality disabled in UI
Logs show that Unbound is being stopped and started every one minute, as follows. Perhaps the crashes are related to occasional failures starting after being stopped by this automation.
plugins_configure unbound_stop (1)
plugins_configure unbound_start (1)
The command '/bin/kill -'TERM' 'PID''(pid:/var/run/unbound.pid) returned exit code '1', the output was 'kill: PID: No such process'
Additionally, Python initialization errors occur:
[9897:0] fatal error: failed to init modules
[9897:0] error: module init for module python failed
[9897:0] error: python exception in Py_InitializeFromConfig: init_fs_encoding: failed to get the Python codec of the filesystem encoding
To Reproduce
The issue occurs spontaneously after several hours of operation, and I haven't found a specific trigger. The problem has been persistent across reboots and OPNsense updates and appears to happen regardless of network load.
Expected behavior
Unbound DNS service should run continuously without requiring manual intervention.
Describe alternatives you considered
Disabled DNS Blocklist feature through the UI, but Python dependencies continue to load and cause failures
Attempted to unmount Python directories manually, but they remain busy with Python processes that continually respawn when killed
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Unbound DNS service repeatedly crashes due to Python mounting issues within the chroot environment. Service restarts are required multiple times per day to maintain DNS resolution.
Core symptoms:
Logs consistently show these errors:
mount_nullfs: /var/unbound/usr/local/lib/python3.11: Resource deadlock avoided
mount_nullfs: /var/unbound/usr/local/lib/python3.11: Device busy
Logs show that Unbound is being stopped and started every one minute, as follows. Perhaps the crashes are related to occasional failures starting after being stopped by this automation.
Additionally, Python initialization errors occur:
To Reproduce
The issue occurs spontaneously after several hours of operation, and I haven't found a specific trigger. The problem has been persistent across reboots and OPNsense updates and appears to happen regardless of network load.
Expected behavior
Unbound DNS service should run continuously without requiring manual intervention.
Describe alternatives you considered
Relevant environment information
Relevant configuration
From unbound.conf:
Python module configuration:
Relevant log entries
Repeated Python mount failures:
Extensive service flapping (occurring every minute):
Additional information
Python processes remain persistent and respawn immediately after being killed:
Despite the service showing as not running, Python processes related to unbound continue to run:
I think the issue first appeared after updating to OPNsense 25.1.
DNS resolution generally works despite the flapping, but it does cause dropped connections with API sessions.
The text was updated successfully, but these errors were encountered: