Facing old bug LP:1683047 with MaaS 2.5 stable - bind9 fails to start, duplicated entry


#1

Guys,

I was running MaaS just fine and “out of blue”, I’m facing the BUG LP:1683047.

Thing is that it wasn’t my intention to overlap anything!

But, somehow, MaaS duplicated entries on bind9 and it fails to start.

Errors:

maas.log:


2019-01-15T11:20:58.138832-05:00 wc maas.dns: message repeated 19 times: [ [error] Reloading BIND failed (is it running?): Command rndc -c /etc/bind/maas/rndc.conf.maas reload returned non-zero exit status 1:#012rndc: connect failed: 127.0.0.1#954: connection refused]
2019-01-15T11:20:59.670150-05:00 wc maas.service_monitor: [info] Service ‘bind9’ is not on, it will be started.
2019-01-15T11:20:59.673999-05:00 wc maas.dns: [error] Reloading BIND failed (is it running?): Command rndc -c /etc/bind/maas/rndc.conf.maas reload returned non-zero exit status 1:#012rndc: connect failed: 127.0.0.1#954: connection refused
2019-01-15T11:20:59.725717-05:00 wc maas.service_monitor: [error] Service ‘bind9’ failed to start. Its current state is ‘dead’ and ‘Result: exit-code’.
2019-01-15T11:21:01.134416-05:00 wc maas.dns: [error] Reloading BIND failed (is it running?): Command rndc -c /etc/bind/maas/rndc.conf.maas reload returned non-zero exit status 1:#012rndc: connect failed: 127.0.0.1#954: connection refused

systemctl status bind9:

Jan 15 11:20:29 maas-1 named[4646]: loading configuration from ‘/etc/bind/named.conf’
Jan 15 11:20:29 maas-1 named[4646]: /etc/bind/maas/named.conf.maas:112: zone ‘56.84.10.in-addr.arpa’: already exists previous definition: /etc/bind/maas/named.conf.maas:12
Jan 15 11:20:29 maas-1 named[4646]: loading configuration: failure
Jan 15 11:20:29 maas-1 named[4646]: exiting (due to fatal error)
Jan 15 11:20:29 maas-1 systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE
Jan 15 11:20:29 maas-1 systemd[1]: bind9.service: Failed with result ‘exit-code’.

What to do?

:-/


#2

Fixed!

I created an overlap by accident.

Bad thing is that MaaS doesn’t provide ANY warning and jut breaks itself.

It should print an error message, similar with “IP already in use”, or something like that… Right?!


#3

Yes, you’re right. MAAS shouldn’t allow you to create an overlap so that bind won’t start.

Could you please file a bug and explain how to reproduce it?

https://launchpad.net/maas/+filebug