Public bug reported:
We recently had a bind9 package upgrade take out DNS services for a
production cloud because named failed to come up after the postinst
restarted it. So obviously, a) our DNS shouldn't be a SPOF and b) we
shouldn't let our config files get into a state where named refuses to
start, but, with that said, the bind9 postinst could be more robust
against this kind of failure mode.
Specifically it could run named-checkconf against /etc/bind/named.conf
and, if it returns 1, either:
a) skip the restart and scream loudly to warn the admin
or
b) abort the package install by erroring out of the postinst at that
point
** Affects: bind9 (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492212
Title:
postinst should validate config before restarting bind
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1492212/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
