[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: bind9 (Ubuntu Eoan) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Released Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Released Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: Won't Fix Status in bind9 source package in Eoan: Won't Fix Bug description: [Impact] * 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. * 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 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: bind9 (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Released Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Released Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: Won't Fix Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * 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. * 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 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Released Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Released Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * 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. * 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 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: bind Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Committed Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Committed Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * 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. * 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 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: maas (Ubuntu Bionic) Assignee: (unassigned) => Blake Rouse (blake-rouse) ** Also affects: maas/2.4 Importance: Undecided Status: New ** Changed in: maas/2.4 Status: New => Fix Committed ** Changed in: maas/2.4 Milestone: None => 2.4.3 ** Changed in: maas/2.4 Assignee: (unassigned) => Blake Rouse (blake-rouse) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: New Status in MAAS: Fix Committed Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Committed Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * 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. * 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 To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: maas/2.6 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: New Status in MAAS: Fix Committed Status in MAAS 2.2 series: Fix Released Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Committed Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: Confirmed Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: Am running an HA MAAS, but every few days named gets stuck on one of the region controllers. systemd thinks the service is running, but it doe 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. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** No longer affects: maas (Ubuntu Xenial) ** No longer affects: maas (Ubuntu Eoan) ** No longer affects: maas (Ubuntu Disco) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: New Status in MAAS: Fix Committed Status in MAAS 2.2 series: Fix Released Status in MAAS 2.6 series: Fix Committed Status in MAAS 2.7 series: Fix Committed Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: New Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: New Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: Am running an HA MAAS, but every few days named gets stuck on one of the region controllers. systemd thinks the service is running, but it doe 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. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Also affects: bind9 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: bind9 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: bind9 (Ubuntu Xenial) Status: New => In Progress ** Changed in: bind9 (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: New Status in MAAS: New Status in MAAS 2.2 series: Fix Released Status in MAAS 2.6 series: New Status in MAAS 2.7 series: New Status in bind9 package in Ubuntu: In Progress Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in bind9 source package in Disco: In Progress Status in bind9 source package in Eoan: In Progress Bug description: Am running an HA MAAS, but every few days named gets stuck on one of the region controllers. systemd thinks the service is running, but it doe 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. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
