[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

It's maas itself pulling bind9 as a dependency for the dns infra it offers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609798 Title: dnsmasq failed to create listening socket. Address already

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

Well, again a fresh install which fails to run 'lxd init'. This time, it's the dnsmasq which seems to be involved. In fact, dnsmasq enters in conflict with named (bind9). I removed the bind9 which doesn't seem to have dependencies, but it was installed by... something (who knows what). We should

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

I'd like to add that I've replicated this issue twice. The resolution of adding specific listeners to maas's bind works temporarily, but we need a way to have maas specify the listeners in bind by network address/network by default. Restarting maas resets the bind settings and the issue with

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609798 Title: dnsmasq failed to create listening socket. Address already in use. To manage

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

Agh... Misregard that config, it was mistaken as I was trying to use an existing bridge, that is not existing. When I passed the dpkg- reconfigure -p medium lxd, and asked for using a new bridge it went ahead, and now the bridge is visible. 7: lxdbr0: mtu 1500

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

here it goes: ● lxd-bridge.service - LXD - network bridge Loaded: loaded (/lib/systemd/system/lxd-bridge.service; static; vendor preset: enabled) Active: active (exited) since Fri 2016-08-05 11:07:08 BST; 10s ago Docs: man:lxd(1) Process: 14983 ExecStop=/usr/lib/lxd/lxd-bridge stop

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

What happens if you run "systemctl start lxd-bridge"? And then the "systemctl status lxd-bridge" output. The content of /etc/default/lxd-bridge may also be useful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

Thanks for the quick reply. As it seems maas is using bind9, I configured it to listen on the physical network using the following line in /etc/bind/maas/named.conf.options.inside.maas: listen-on { 192.168.0.28; 192.168.122.1; }; And listen-on-v6 { none; }; in /etc/bind/named.conf.options

[Bug 1609798] Re: dnsmasq failed to create listening socket. Address already in use.

This typically happens when you already have a DNS server running on your machine. Do you have bind9 (named) installed by any chance? If so, either remove it (if you don't use it) or configure it to only bind to the IP addresses that you want it to respond on, otherwise its default configuration