Arch Linux

7744 readers

4 users here now

The beloved lightweight distro

founded 4 years ago

MODERATORS

[email protected]

dnsmasq fails to create listening socket (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

I have already created a post for this on the Arch Linux Forum two days, but I didn't recieve any reply there, so I'm trying it here.

I have multiple KVM virtual machines thatI use on a semi regular basis. After reinstalling dnsmasq, because it wasn't installed for some reason, I get the error message that network default is not active every time I try to boot one of them.

Running virsh net-start default doesn't solve the problem though, as it outputs error: Failed to start network default error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/bin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: dnsmasq: failed to create listening socket for 192.168.122.1: Address already in use

I don't know how to proceed from here and I couldn't really find anyone that ran into the same problem.

Any advice would be appreciated. Thank you in advance.

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 5 months ago

Address already in use is the key - something else has already bound to that address:port combination. Next step is to find out what process is listening on it. Try ss, netstat, lsof to name a few hints.

[–] [email protected] 1 points 5 months ago (1 children)

I had the exact same issue! I was going crazy troubleshooting this, anyway it turned out to be the firewall on my arch install. I disabled ufw and everything started working as usual. I really should enable the firewall again and check what rules are screwing it up.

[–] [email protected] 1 points 5 months ago (1 children)

I tried disabeling my firewall, but I still got the same error. So that's not it

[–] [email protected] 1 points 5 months ago

Maybe try creating a new virtual network with a different subnet?