Public bug reported:
We have several machines where unbound was updated tonight by automated
security updates to 1.5.8-1ubuntu1.1. Afterwards there was no unbound
process running, output from systemctl status says:
systemctl status unbound
● unbound.service
Loaded: loaded (/etc/init.d/unbound; bad; vendor preset: enabled)
Drop-In: /run/systemd/generator/unbound.service.d
└─50-insserv.conf-$named.conf, 50-unbound-$named.conf
Active: active (exited) since Fri 2018-06-08 06:39:21 UTC; 5h 17min ago
Docs: man:systemd-sysv-generator(8)
Process: 25819 ExecStop=/etc/init.d/unbound stop (code=exited,
status=0/SUCCESS)
Process: 25857 ExecStart=/etc/init.d/unbound start (code=exited,
status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 0.065536 0.131072
12826
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 0.131072 0.262144
15352
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 0.262144 0.524288 5310
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 0.524288 1.000000 1067
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 1.000000 2.000000 357
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 2.000000 4.000000 84
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 4.000000 8.000000 12
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 64.000000 128.000000 16
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 128.000000 256.000000 12
Jun 08 06:39:22 ze02 unbound[1681]: [1681:0] info: 256.000000 512.000000 52
After a restart everything is fine again. Looking at the extend log with
journalctl it looks like the old process was too slow with stopping and
systemd was too eager starting the new one. But it is not clear to me
why there is no error logged from the new process, then. See
http://paste.openstack.org/show/722969/ for that log.
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775833
Title:
unbound not running after automatic update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1775833/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
