Comment 3 for bug 1683047

Hey guys,

 I'm facing this problem with MaaS 2.5 stable.

 How can I fix it without reinstalling it from scratch?

 So far, it wasn't my intention to overlap any network.

 Logs:

maas.log:
---
2019-01-15T11:15:59.338281-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:15:59.667179-05:00 wc maas.service_monitor: [info] Service 'bind9' is not on, it will be started.
2019-01-15T11:15:59.726226-05:00 wc maas.service_monitor: [error] Service 'bind9' failed to start. Its current state is 'dead' and 'Result: exit-code'.
2019-01-15T11:16:00.852280-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:15:59 maas-1 named[3491]: loading configuration from '/etc/bind/named.conf'
Jan 15 11:15:59 maas-1 named[3491]: /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:15:59 maas-1 named[3491]: loading configuration: failure
Jan 15 11:15:59 maas-1 named[3491]: exiting (due to fatal error)
Jan 15 11:15:59 maas-1 systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE
Jan 15 11:15:59 maas-1 systemd[1]: bind9.service: Failed with result 'exit-code'.
---

 What to do?

Best,
Thiago