Hi all, I currently face an issue, where I don?t know further on why this happens and what I could do about it. I hope that this is the correct list to ask my question. If not please let me know where else I might try my luck. I installed unbound from ports, configured it and can start / stop it from command line with service unbound start without any problems. But whenever I reboot the machine it just doesn?t get started. The only information I was able to find out so far can be found in /var/log/messages: root: /etc/rc: WARNING: failed to start unbound I tried to run with rc_debug=?YES? and got the following: root: /etc/rc: DEBUG: checkyesno: unbound_enable is set to YES. root: /etc/rc: DEBUG: run_rc_command: start_precmd: start_precmd root: /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. root: /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon /usr/local/sbin/unbound -c /usr/local/etc/unbound/unbound.conf root: /etc/rc: WARNING: failed to start unbound uname -a: FreeBSD h01dc01 11.2-RELEASE-p9 FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 15:30:36 UTC 2019 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Thanks for any useful hints in advance Markus
On Apr 30, 2019, at 3:44 PM, Markus Wipp <m.wipp at BlueBird-AG.com> wrote:> Hi all, > > I currently face an issue, where I don?t know further on why this happens > and what I could do about it. > I hope that this is the correct list to ask my question. If not please > let me know where else I might try my luck. > I installed unbound from ports, configured it and can start / stop it > from command line with service unbound start without any problems. > But whenever I reboot the machine it just doesn?t get started. The only > information I was able to find out so far can be found in > /var/log/messages: > root: /etc/rc: WARNING: failed to start unbound > > I tried to run with rc_debug=?YES? and got the following: > root: /etc/rc: DEBUG: checkyesno: unbound_enable is set to YES. > root: /etc/rc: DEBUG: run_rc_command: start_precmd: start_precmd > root: /etc/rc: DEBUG: checkyesno: rc_startmsgs is set to YES. > root: /etc/rc: DEBUG: run_rc_command: doit: limits -C daemon > /usr/local/sbin/unbound -c /usr/local/etc/unbound/unbound.conf > root: /etc/rc: WARNING: failed to start unbound > > uname -a: > FreeBSD h01dc01 11.2-RELEASE-p9 FreeBSD 11.2-RELEASE-p9 #0: Tue Feb 5 > 15:30:36 UTC 2019 > root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Thanks for any useful hints in advanceI don't know how useful this is, but depending upon how the unbound startup script is defined to start (e.g., the REQUIRE: and BEFORE: lines in the startup script), maybe it is set to start up too early, e.g., before /usr/local is mounted? This at least would be one reason why it doesn't start up at boot but will start up manually from the command line. Cheers, Paul.
On 2019-Apr-30 19:44:36 +0000, Markus Wipp <m.wipp at BlueBird-AG.com> wrote:>I currently face an issue, where I don?t know further on why this happens and what I could do about it. >I hope that this is the correct list to ask my question. If not please let me know where else I might try my luck. >I installed unbound from ports, configured it and can start / stop it from command line with service unbound start without any problems. >But whenever I reboot the machine it just doesn?t get started. The only information I was able to find out so far can be found in /var/log/messages: >root: /etc/rc: WARNING: failed to start unboundI have seen unbound fail to start for a variety of reasons but in all cases, it has written a useful hint to the console. Can you confirm that it's not writing anything to your console. Are you able to share your configuration? -- Peter Jeremy -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20190501/69c71ccd/attachment.sig>
> On 1. May 2019, at 00:02, Peter Jeremy <peter at rulingia.com> wrote: > >> On 2019-Apr-30 19:44:36 +0000, Markus Wipp <m.wipp at BlueBird-AG.com> wrote: >> I currently face an issue, where I don?t know further on why this happens and what I could do about it. >> I hope that this is the correct list to ask my question. If not please let me know where else I might try my luck. >> I installed unbound from ports, configured it and can start / stop it from command line with service unbound start without any problems. >> But whenever I reboot the machine it just doesn?t get started. The only information I was able to find out so far can be found in /var/log/messages: >> root: /etc/rc: WARNING: failed to start unbound > > I have seen unbound fail to start for a variety of reasons but in all cases, it has > written a useful hint to the console. Can you confirm that it's not writing anything > to your console. Are you able to share your configuration? > > -- > Peter JeremyHi Peter, many thanks to you! By looking at the console output I was able to determine that the interface/up I bound unbound to was not yet available during the boot process (it was tun0 for my VPN). After finding this cause it was just a matter of ensuring tun0 gets created and configured as cloned interface. So now everything works as it should! Thanks again to all! Have a nice day! Markus