Unbound failed to start after boot

Started by sarkyscouser, October 12, 2023, 09:09:23 AM

Previous topic - Next topic
I am running 23.7.5 on a N100/i226 mini PC.  I have a pppoe WAN connection (FTTP BT, UK). At boot the unbound service isn't starting, here are the relevant logs filtering for "unbound":


2023-10-12T07:58:32 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '87338''(pid:/var/run/unbound.pid)  returned exit code '1', the output was 'kill: 87338: No such process'
2023-10-12T07:58:32 Notice opnsense /usr/local/sbin/pluginctl: plugins_configure unbound_start (execute task : unbound_configure_do(1))
2023-10-12T07:58:32 Notice opnsense /usr/local/sbin/pluginctl: plugins_configure unbound_start (1)
2023-10-12T07:58:31 Notice opnsense /usr/local/sbin/pluginctl: plugins_configure unbound_stop (execute task : unbound_service_stop(1))
2023-10-12T07:58:31 Notice opnsense /usr/local/sbin/pluginctl: plugins_configure unbound_stop (1)
2023-10-12T07:46:12 Error opnsense /usr/local/sbin/pluginctl: The command '/bin/kill -'TERM' '64293''(pid:/var/run/unbound.pid)  returned exit code '1', the output was 'kill: 64293: No such process'
2023-10-12T07:41:04 Notice opnsense /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,wan))
2023-10-12T07:40:52 Notice kernel <118>Starting Unbound DNS...done.
2023-10-12T07:40:50 Notice opnsense /usr/local/etc/rc.bootup: plugins_configure bootup (execute task : unbound_configure_do(1))
2023-10-12T07:40:50 Notice kernel <118>Starting Unbound DNS...done.
2023-10-12T07:40:49 Notice opnsense /usr/local/etc/rc.bootup: plugins_configure dns (execute task : unbound_configure_do(1))
2023-10-12T07:40:48 Notice opnsense /usr/local/etc/rc.bootup: plugins_configure early (execute task : unbound_cache_flush(1))


I don't have any domain overrides and I am using DNS over TLS for forward to 2x ipv4 upstreams and 2x ipv6 upstreams.

If I start unbound manually it fires right up and works but will fail on next reboot.

Just upgraded to 23.7.6 and restarted and unbound did start this time so it's hit and miss, what else can I do to diagnose?