Release 2.4.3 debdiff. ** Description changed:
- Am running an HA MAAS, but every few days named gets stuck on one of the - region controllers. + [Impact] - systemd thinks the service is running, but it doe not respond to any + * systemd thinks the service is running, but it does not respond to any commands or requests. Also, it doesn't respond to signals other than kill -9. service restarts hang, rndc hangs. - I have attached logs and a core dump of named. + * being that the deadlock is in bind9 that ships in bionic the issue + needs to be backported to 2.4.3 so MAAS from the archive in bionic can + handle the deadlock and get bind9 unstuck. + + * change in MAAS watches for this case to occur with bind9, then MAAS + will force kill the service and restart it. + + [Test Case] + + * very hard to reproduce but the issue occurs when bind9 deadlocks, it + response to nothing over the network or rndc. SIGTERM does not kill it + only SIGKILL works to force kill the process and get systemd to restart + it. + + + [Regression Potential] + + * possible that bind9 will not be started correctly or possible that + bind9 will be placed into a forever restart loop ** Patch added: "maas_2.4.3.debdiff" https://bugs.launchpad.net/maas/+bug/1710278/+attachment/5302068/+files/maas_2.4.3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
