On Sun, Jun 24, 2018 at 10:28:55AM -0500, Bruce Dubbs wrote: > On 06/23/2018 10:11 PM, Ken Moffat wrote: > > > > Which, I guess, promptes the question - does anybody else actually > > use unbound ? > > I do not use it, but I might suggest watching udp traffic with wireshark > while it is starting. > > Also, you might want to see if you get the same delays with the bind server. > What you describe seem to me to be timeouts and that could be upstream or > ISP issues. > If I stop it after booting, and then start it again, it starts immediately.
There have been recent kernel changes regarding entropy, and when I managed to find an online page about unbound and random it mentioned that if running in a chroot, /dev/random needs to accessible. https://www.unbound.net/documentation/unbound.conf.html My impression is that the kernel now needs more entropy before /dev/random can beaccessed without hanging. And google has a report re running in a KVM - https://www.unbound.net/pipermail/unbound-users/2018-May/005273.html From my last cold boot: Jun 22 20:01:13 origin kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0x7f/0x57f with crng_init=0 ... Jun 22 20:01:13 origin kernel: [ 0.428419] random: fast init done ... Jun 22 20:01:13 origin smartd[823]: smartd has fork()ed into background mode. New PID=823. (an S21 script) Jun 22 20:01:16 origin kernel: [ 5.283445] r8169 0000:25:00.0 eth0: link up Jun 22 20:01:16 origin kernel: [ 5.283453] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jun 22 20:01:25 origin kernel: [ 14.684668] random: crng init done Jun 22 20:01:25 origin kernel: [ 14.684671] random: 5 urandom warning(s) missed due to ratelimiting Jun 22 20:01:25 origin unbound: [870:0] notice: init module 0: validator Jun 22 20:01:25 origin unbound: [870:0] notice: init module 1: iterator Jun 22 20:01:25 origin unbound: [870:0] info: start of service (unbound 1.7.2). So I'm guessing that keying Ctrl-C one or more times, and possibly <enter>, generates enough entropy. I have the random script at S25, but unbound is at S21. The script intialises /dev/urandom, of course, but unbound is supposed to fall back to that (although the post on unbound-users suggests it didn't in that setup). According to the documentation for the unbound bootscript, it relies on network (S20) so moving random to S21 would give me S20network S21random S21smartd S21unbound I'm not intending to reboot at the moment (on this machine I suspend, on the other main desktop I hibernate), will try to remember to change that on whichever machine I next intend to reboot. ĸen -- Keyboard not found, Press F1 to continue -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
