Matthew Vernon wrote: > I have unbound & systemd on a jessie system, and every time there's an > update to unbound, it ends up not running. I /think/ it's this bug > biting us, but I'm not entirely sure. > > For instance, we recent upgraded to 1.4.22-3+deb8u1 and unbound was no > longer running. daemon.log output: > > Apr 18 11:18:40 boarstall unbound[50877]: Stopping recursive DNS server: > unbound. > > [then follows info about processing times] > > Apr 18 11:18:40 boarstall unbound-anchor: /var/lib/unbound/root.key has > content > Apr 18 11:18:40 boarstall unbound-anchor: success: the anchor is ok > Apr 18 11:18:40 boarstall unbound[50885]: Starting recursive DNS server: > unbound. > > ...except at this point unbound is not running (I think that last entry > is actually from systemd). > > Is it plausible that this is caused by this bug? If so, a jessie update > with a working systemd service file might be warranted - having your DNS > go away on upgrade is annoying...
Hi, Matthew: Thank you for this follow-up, up until now I had thought this behavior could only be triggered when using "unbound-control" to stop unbound. Could you try using the "very basic native unbound.service unit file" from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807132#10 as a drop-in, and see if the behavior goes away? -- Robert Edmonds edmo...@debian.org