Mark, Do you have any updated repro steps?
I'm seeing this failure with MAAS v2.5.3. I suspect when v2.5 moved the DNS logic from region to rack controller, that some of the mitigation logic was lost and thus this bug manifests more frequently. When I compare our v2.5.3 install from our v2.4.2 install, the amount of rndc reloads is vastly more on v2.5.3. [2.4.2] journalctl -b -u bind9.service |grep received.control Jun 22 00:22:05 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 22 00:22:08 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 22 00:22:54 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 24 16:27:06 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 25 13:53:34 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 25 13:53:41 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 25 13:54:51 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' Jun 25 13:55:22 wdc1-p01-s01-maas-18 named[907]: received control channel command 'reload' [2.5.3] journalctl -b -u bind9.service |grep received.control Jun 26 14:23:59 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:04 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:09 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:11 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:15 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:18 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:22 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:27 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:31 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:36 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:40 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' Jun 26 14:24:42 ch31-p01-s01-maas-18 named[1041]: received control channel command 'reload' I had to trim the 2.5.3 output because it was way too long to fit in this comment, but as you can see 2.5.3 is spamming reload as compared to 2.4.2. 2.4.2 it may reload 4 times for the _entire day_ whereas 2.5.3 is doing hundreds if not thousands a day. -- 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
