Hi, this seems to be a service that fails on upgrade. Setting up bind9 (1:9.9.5.dfsg-3ubuntu0.19) ... * Starting domain name service... bind9 fail
In the logs I can further see: Mar 4 09:14:52 named[3701]: loading configuration from '/etc/bind/named.conf' Mar 4 09:14:52 named[3701]: /etc/bind/named.conf.options:22: expected IP address near 'dnssec-validation' Mar 4 09:14:52 named[3701]: loading configuration: unexpected token So it seems there is a local modification to that config file that is breaking the server restart. I checked and none of the recent updates to bind9 has messed with conffile handling in any way. So most likely this isn't a regression due to the upgrade, but instead a config file that was in a bad state and the package upgrade now makes you aware of that. Please look into your config file, fix the issue and restart named. Once that works, the package upgrade will likely work as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917774 Title: package bind9 1:9.9.5.dfsg-3ubuntu0.19 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1917774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
