severity 809773 important thanks On Sun, Jan 03, 2016 at 10:53:24PM +0100, Christoph Anton Mitterer wrote:
> Severity: critical
> Justification: breaks unrelated software
[...]
> I've just upgraded from 0.7.54 to 0.8.5 and after rebooting the server,
> all kinds of daemons didn't come up anmore, e.g. BIND, Apache HTTP,
> SKS
First, this is not a critical bug. No unrelated software is actually
broken, it's just that at boot, apparently some services are started
earlier than your network devices are configured.
> Jan 03 22:31:50 kronecker named[956]: listening on IPv4 interface lo,
> 127.0.0.1#53
> Jan 03 22:31:50 kronecker named[956]: listening on IPv6 interface lo, ::1#53
> Jan 03 22:31:50 kronecker named[956]: generating session key for dynamic DNS
> Jan 03 22:31:50 kronecker named[956]: sizing zone task pool based on 45 zones
> Jan 03 22:31:50 kronecker named[956]: acache 0x7f80f01535d0 cleaning interval
> set to 3600.
> Jan 03 22:31:50 kronecker named[956]: could not get query source dispatcher
> (1.2.3.199#0)
> Jan 03 22:31:50 kronecker named[956]: loading configuration: address not
> available
> Jan 03 22:31:50 kronecker named[956]: exiting (due to fatal error)
> Jan 03 22:31:50 kronecker systemd[1]: bind9.service: Main process exited,
> code=exited, status=1/FAILURE
> Jan 03 22:31:51 kronecker rndc[1166]: rndc: connect failed: 127.0.0.1#49153:
> connection refused
>
> => seems as if even lo wouldn't be ready at that point in time?!
That would be really weird, because lo should already be up at boot time
(it's actually not necessary anymore to have an "auto lo" in
/etc/network/interfaces). I suspect it's that named exited while trying
to configure the eth0 address, and only afterwards is the rndc processes
called which fails to connect to the no longer running named.
From your /etc/network/interfaces:
> allow-hotplug eth0
If you do this, eth0 will be brought up by hotplugging events, which are
handled completely asynchronous wrt. the normal bootup sequence. So it
could very well be that systemd tries to start named, bind and sks
before eth0 is configured. Please change that line to:
auto eth0
I suspect that will fix the issue. But if not, please send me the output
of the following command:
systemd-analyze dump
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
