dnsmasq is lying and will not run

camosoul · 2021-10-18 04:46:36

Oct 18 00:16:08 dnsmasq[817]: failed to create listening socket for port 53: Address already in use

This statement is a lie. Address is NOT in use.

How do I make it stop lying?
How do I force it to run?

Last edited by camosoul (2021-10-18 04:48:59)

camosoul · 2021-10-18 05:23:07

Turns out there's a secret, undocumented service I have to shut off that is preventing dnsmasq from running.

https://askubuntu.com/questions/191226/ … ady-in-use

Oh, but it gets better!

As soon as I shut it off, then it complains that it's been shut off!

Oct 18 01:08:10 dnsmasq[463]: directory /etc/resolv.conf for resolv-file is missing, cannot poll

So:

If systemd-resolvd is running, dnsmasq refuses to run.
but
If systemd-resolvd is not running, dnsmasq refuses to run.

I can't win.

This is insane.

Last edited by camosoul (2021-10-18 05:23:43)

camosoul · 2021-10-18 05:50:49

Everything I searched on the Internet was lies.

Why would it complain that something doesn't exist, which it is supposed to be creating itself? Error message was a lie.

/etc/resolv.conf did exist, in spite of the error that was lying and saying it did not exist. It was a symlink to some crazy nonsense that nobody seems to know anything about.

So, I deleted it.

Poof. Everything started working.

Serves me right for expecting anything useful on the internet these days. Everything was a lie. Even the error messages were lies.

seth · 2021-10-18 06:22:28

1. stop bumping, edit your post if nobody has replied.
2. Don't rant around - maybe re-read the CoC
3. You're running into systemd-resolved, which isn't a "secret, undocumented service " but despite being one of lennarts more questionable brainafarts very much documented, https://wiki.archlinux.org/title/Systemd-resolved
4. The system isn't "lying", your uninformed assumptions were incorrect
5. Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Edit: I will give you though that depending the behavior on the type of a file is crazy and for the future: if you had simply checked which process holds port 53 open (… before you google more "lies", ss and netstat can do that …), you'd have found that it's systemd-resolved and then looking up the wiki would have explained the situation.

Last edited by seth (2021-10-18 06:28:16)

Arch Linux

#1 2021-10-18 04:46:36

dnsmasq is lying and will not run

#2 2021-10-18 05:23:07

Re: dnsmasq is lying and will not run

#3 2021-10-18 05:50:49

Re: dnsmasq is lying and will not run

#4 2021-10-18 06:22:28

Re: dnsmasq is lying and will not run

Board footer