On 06/23/2018 10:11 PM, Ken Moffat wrote:
On Sat, Jun 02, 2018 at 10:02:39PM +0100, Ken Moffat wrote:
I've been seeing problems on some of my machines with recent kernels
(first noticed in 4.17-rc, but it also now happends in 4.16.4 or
later). The problem is that instead of unbound taking a handful of
seconds to start (often, it is all-but immediate), on the affected
machines it now takes up to two and a half minutes.
[...]
So, for the moment I'm offering a workaround (patch the bootscript,
if anybody uses systemd and unbound this will obviously not help).
Just a minor update on this - I've updated one of the machines where
I didn't have a problem - a new system on 4.17.1 seemed a little
slower to boot unbound, but succeeded. But I've now updated it to
4.17.2 and it *appears* to hang (maybe not exactly the same, keying
a _single_ Ctrl-C after the message about the keyfile seems to let
it continue).
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.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
