dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

j1simon · 2021-11-22 13:57:14

KDE Plasma
NetworkManager with dnsmasq enabled (https://wiki.archlinux.org/title/NetworkManager#dnsmasq).

All seems work but in journalctl output:

...
dnsmasq[2145]: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed: Operation not allowed
....

$ ls -l /var/run/NetworkManager/dnsmasq.pid
-rw-r--r-- 1 root root 5 nov 22 14:25 /var/run/NetworkManager/dnsmasq.pid

j1simon · 2021-11-23 08:43:31

I just checked that it shows me another warning (below the previous one):

dnsmasq[2245]: warning: no upstream servers configured

What does it mean?

Morta · 2021-11-25 17:36:32

j1simon wrote:

I just checked that it shows me another warning (below the previous one):
dnsmasq[2245]: warning: no upstream servers configured
What does it mean?

It's mean that no DNS-Server are configured. I think so.

https://askubuntu.com/questions/1031260 … er-upgrade

Remove dns=dnsmasq in the config or set DNS Server

progandy · 2021-11-25 17:45:03

I believe that warning can be ignored. networkmanager should set upstream servers later, after dnsmasq has started without upstream servers. dnsmasq is started first, then later when dns servers are received with dhcp they are given to the already running dnsmasq.

Last edited by progandy (2021-11-25 17:46:15)

Morta · 2021-11-25 20:22:49

progandy wrote:

I believe that warning can be ignored. networkmanager should set upstream servers later, after dnsmasq has started without upstream servers. dnsmasq is started first, then later when dns servers are received with dhcp they are given to the already running dnsmasq.

Ok then you can remove dns=dnsmasq anyway, nor?

progandy · 2021-11-25 20:35:55

Morta wrote:

Ok then you can remove dns=dnsmasq anyway, nor?

That is possible if you do not want to use dnsmasq to forward all dns queries. Using dns=dnsmasq is one option, though. Alternatives would be systemd-resolved, resolv.conf (managed through openrsolv/resolvconf) or resolv.conf (written directly).
Using either dnsmasq or systemd-resolved can have advantages with caching and/or conditional forwarding, though. (If you need or want that)

Last edited by progandy (2021-11-25 20:38:04)

j1simon · 2021-11-26 08:08:24

I don't understand that if NetworkManager is the one that raises this dnsmasq service it doesn't do it correctly to avoid these unnecessary messages. I have opened a issue: https://gitlab.freedesktop.org/NetworkM … issues/859

Last edited by j1simon (2021-11-26 08:39:29)

Arch Linux

#1 2021-11-22 13:57:14

dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#2 2021-11-23 08:43:31

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#3 2021-11-25 17:36:32

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#4 2021-11-25 17:45:03

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#5 2021-11-25 20:22:49

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#6 2021-11-25 20:35:55

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

#7 2021-11-26 08:08:24

Re: dnsmasq: chown of PID file /var/run/NetworkManager/dnsmasq.pid failed

Board footer