Open killua-eu opened 1 month ago
I suspect the fact that the server has been updated from initially ubuntu 18.04 as I see some arcane networking bash scripts all over /etc
That usually means that you have something like dnsmasq or bind9/named already listening on port 53 and conflicting with dnsmasq.
You may want to look at the netstat -lnp | grep 53
output or similar to see what's going on.
@killua-eu have you been able to figure out what's going on? Still seems most likely to be a conflict with another DNS or DHCP server on the system.
I encountered this just now when I tried to run sudo incus admin init
,
It warns me that
Error: Failed to create local member network "incusbr0" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to bind DHCP server socket: Address already in use")
But I have no process binding to 53 port.
sudo netstat -lnp | grep ":53 "
returns nothing.
@rogtino maybe it's the DHCP side that's conflicting with something? :67
?
Thanks for your reply.
sudo netstat -lnp | grep ":67 "
returns nothing.
Just FYI,
I have set DNSStubListener=no
in /etc/systemd/resolved.conf because there seems to be a conflict between dnsmasq and systemd-resolved.
@killua-eu did you have any luck?
@rogtino on your end, if this is still an unresolved issue, maybe look at /var/log/syslog
or the systemd journal to see if dnsmasq
gives more of a hint as to what port it's conflicting with?
Also a full netstat -lnp
output would be useful.
Or are you saying that the stub resolver was the source of the conflict? If so, that's pretty odd as it normally runs on a specific loopback address (127.0.0.53 if I recall correctly) and so shouldn't get in the way of something trying to bind a random 10.X.Y.1
address.
Required information
Issue description
Incus cannot initialize its bridge. /var/log/incus/incusd.log
the same error will be emitted on trying to create a new network.