"dnsmasq not available on the bus"

[Benjamin Kerensa]

Dnsmasq seems to be having some issues. This occurs whenever I try to connect to my wireless network; sometimes it only happens once, but sometimes the error loops for a while.

Sep 9 17:43:51 bkerensa NetworkManager[935]: <info> DNS: starting dnsmasq...
Sep 9 17:43:51 bkerensa NetworkManager[935]: <error> [1347237831.899067] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers.
Sep 9 17:43:51 bkerensa NetworkManager[935]: <error> [1347237831.899142] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Sep 9 17:43:51 bkerensa NetworkManager[935]: <warn> DNS: plugin dnsmasq update failed
Sep 9 17:43:51 bkerensa NetworkManager[935]: <info> ((null)): writing resolv.conf to /sbin/resolvconf

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: dnsmasq (not installed)
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep 9 17:47:22 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)

[Thomas Hood (jdthood)]

@Benjamin: Hi. Please reboot, reproduce the problem, then run "apport-collect 1048430" to submit relevant information about the affected machine.

[Peder Chr. Nørgaard (pcn)]

This is a "me too" comment - I ran into exactly the same problem when I upgraded my Kubuntu 12:04 system to 12:10 Beta 1 last on Monday Sept 17th. And the problem is still there, today on Sept 20th - I mention this because the Beta 1 system is a fast-moving target, many new updates every day.

There is a simple work-around for the problem, pull the DNS server out of /var/log/syslog (grep for 'using nameserver' ), and edit it manually into /etc/resolv.conf. But then you have to do that again every time you move your computer.

I tried to run an "apport-collect", but obviously only the original submitter of the report is allowed to do that.

I think the problem may be the one that is discussed on the network-manager mailing list - see <https://mail.gnome.org/archives/networkmanager-list/2012-August/msg00094.html>

Best regards

Peder Chr. Nørgaard, M.Sc.
Senior SW Developer
www.actua.dk - Software that transforms the business of Energy

[Thomas Hood (jdthood)]

@Peder: It's not advisable to edit /etc/resolv.conf by hand. Your workaround is to avoid using NM-controlled dnsmasq. Here is a better way to do that. First, make sure that /etc/resolv.conf is still a symbolic link to ../run/resolvconf/resolv.conf. Second, edit /etc/NetworkManager/NetworkManager.conf and comment out the line "dns=dnsmasq". Third, reboot.

[Mathieu Trudel-Lapierre (cyphermox)]

I'm reassinging this to network-manager. The issue here is not related to that upstream thread. Unfortunately, we don't have enough information to debug this. Please answer the following questions:

Is 'dnsmasq' (the package), installed? (check with "dpkg -l dnsmasq")
 If so, what is its configuration; in /etc/dnsmasq.conf and what files are in /etc/dnsmasq.d?

Is there another dnsmasq process running at the time?

What is the exact content of /etc/resolv.conf when resolution doesn't work?

What files are present in /run/resolvconf/interface?

Is there another nameserver installed on the system (like bind?)

[Peder Chr. Nørgaard (pcn)]

I agree with the reassignment - it is a network-manager issue.

Here is the information requested, plus some more. Please ask for more if needed, and I you wish me to run some tests, tell me.

The system affected was originally created by Kubuntu 12:04 installer - to the best of my knowledge I have not deviated from what is default in that distribution with regards to network manager and dns configuration. The only vaguely relevant change I have made is to configure an IPSec based VPN.

I included a piece of the syslog, mainly because it is a little different from the one in the original report:

Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): DHCPv4 state changed nbi -> preinit
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Listening on LPF/eth0/5c:26:0a:75:8f:b0
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Sending on LPF/eth0/5c:26:0a:75:8f:b0
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Sending on Socket/fallback
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPREQUEST of 10.10.129.108 on eth0 to 255.255.255.255 port 67
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPOFFER of 10.10.129.108 from 10.10.129.2
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPACK of 10.10.129.108 from 10.10.129.2
Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: bound to 10.10.129.108 -- renewal in 3421 seconds.
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): DHCPv4 state changed preinit -> bound
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> address 10.10.129.108
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> prefix 24 (255.255.255.0)
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> gateway 10.10.129.1
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> nameserver '192.168.253.250'
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> nameserver '192.168.253.251'
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> domain name 'intern.it-huset.dk'
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
Sep 21 07:57:15 pcn-Latitude-E6520 charon: 02[KNL] 10.10.129.108 appeared on eth0
Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper)
Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper)
Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Successfully activated service 'org.freedesktop.colord-sane'
Sep 21 07:57:15 pcn-Latitude-E6520 charon: 02[KNL] fe80::5e26:aff:fe75:8fb0 appeared on eth0
Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Sep 21 07:57:16 pcn-La...

[Joey Stanford (joey)]

Same here on quantal beta 2

Sep 28 11:45:45 localhost NetworkManager[1121]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0]
Sep 28 11:45:46 localhost NetworkManager[1121]: <info> DNS: starting dnsmasq...
Sep 28 11:45:46 localhost NetworkManager[1121]: <error> [1348854346.26373] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers.
Sep 28 11:45:46 localhost NetworkManager[1121]: <error> [1348854346.26405] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Sep 28 11:45:46 localhost NetworkManager[1121]: <warn> DNS: plugin dnsmasq update failed
Sep 28 11:45:46 localhost NetworkManager[1121]: <info> ((null)): writing resolv.conf to /sbin/resolvconf

[Mathieu Trudel-Lapierre (cyphermox)]

Peter: the issue here is that this "error" is expected: on the very first update after boot, dnsmasq will get spawned during the update phase, but is likely not going to be ready yet -- the update will "fail" and fallback to writing the dns names directly to resolv.conf, instead of writing 127.0.1.1 and using dnsmasq. Then when dnsmasq appears on the bus the update is re-tried, and should succeed.

There's no indication of anythign wrong in the response you've given or the log excerpt. Could you have run chattr +i on /etc/resolv.conf? See what 'sudo lsattr /etc/resolv.conf' returns. Otherwise, make sure it's properly a symlink to /run/resolvconf/resolv.conf, which should contain the proper dns data already.

If all this fails, then we'll need to look at NetworkManager debug logs (http://wiki.ubuntu.com/DebuggingNetworkManager) because something else might be failing.

[Peder Chr. Nørgaard (pcn)]

Thank you for your response.

Fortunately (or regrettably, depending on your point of view), the bug has disappeared on me. Earlier, when I restored the link from /etc/resolv.conf to /run/resolvconf/resolv.conf, no DNS worked, even though the syslog file showed that dnsmasq had received correct server IP addresses. But now: it works. Either I did something wrong earlier, or some update (running Beta, I run dist-upgrade daily) has fixed whatever the problem were.

Whatever has happened, I hereby withdraw any claim that this is really a bug in Kubuntu 12:10 Beta.

(BTW, I am not allowed to set the attributes that you recommend - I get a mysterious error: "lsattr: Operation not supported While reading flags on /etc/resolv.conf". Preventing modification of /etc/resolv.conf would not be the solution anyway.)

[Luis Alvarado (luisalvarado)]

Can you explain what you did since I am using 12.10 and I am getting this error. It somehow relates to freezing the system if I use any wireless device.

[Anton Reshin (anton-reshin)]

Luis, you should do the following:

sudo apt-get purge dnsmasq

then reboot (that's not really need, but is better), and then

sudo apt-get install dnsmasq

and all be fine!

This is the problem neither dnsmasq nor networkmanager! This is the problem of upgrade!

[Curtis Cox (curtislcox)]

Hi All,

I'm just getting started on the Linux Train so bare with me. I think I might be having the same issue. I searched the WEB for the error I see in my syslog and it lead me here. I'd appreciate any help and if my issue is not related then my apologies.

I been unable to connect wirelessly for about a week now as near as I can tell on this Latitude E6400.
I can connect using the ethernet on the same device and I can connect wirelessly on my smart phone to my Latitude E6400 and other PCs. However when i try to connect using this router on KDE desktop(4.9.2) config I get the same error reported in this bug. Keep in mind that my wireless connection using the same device works perfectly in Ubuntu 12.10 and linuxmint 13 and Win7, etc... I pasted a couple inserts from my log and the associated error "dnsmasq" recorded throughout my log.

Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> DNS: starting dnsmasq...
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <error> [1353956653.871572] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers.
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <error> [1353956653.871601] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <warn> DNS: plugin dnsmasq update failed
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> ((null)): writing resolv.conf to /sbin/resolvconf
Nov 26 12:04:13 curtis-Latitude-E6400 dnsmasq[1515]: started, version 2.63rc6 cache disabled
Nov 26 12:04:13 curtis-Latitude-E6400 dnsmasq[1515]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack
Nov 26 12:04:13 curtis-Latitude-E6400 dnsmasq[1515]: DBus support enabled: connected to system bus
Nov 26 12:04:13 curtis-Latitude-E6400 dnsmasq[1515]: warning: no upstream servers configured
Nov 26 12:04:13 curtis-Latitude-E6400 vpnagent[1213]: Function: tableCallbackHandler File: RouteMgr.cpp Line: 1694 Invoked Function: recv Return Code: 11 (0x0000000B) Description: unknown
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> Policy set 'CTR35-96e' (eth1) as default for IPv4 routing and DNS.
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> Activation (eth1) successful, device activated.
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> Activation (eth1) Stage 5 of 5 (IPv4 Commit) complete.
Nov 26 12:04:13 curtis-Latitude-E6400 dbus[852]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <warn> dnsmasq appeared on DBus: :1.13
Nov 26 12:04:13 curtis-Latitude-E6400 NetworkManager[926]: <info> ((null)): writing resolv.conf to /sbin/resolvconf
Nov 26 12:04:13 curtis-Latitude-E6400 dnsmasq[1515]: setting upstream servers from DBus
.
.
.
Nov 26 13:30:16 curtis-Latitude-E6400 NetworkManager[879]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Nov 26 13:30:16 curtis-Latitude-E6400 NetworkManager[879]: <info> Activa...

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[Steve White (stevan-white)]

Hi Mathieu (especially):

Yes dnsmasq is installed. It is a dependency of network-manager.
Purging it is therefore not a realistic option for me.

The errors *do not* only happen after an update. They are happening every time the system restarts.

The only line in the only config file,
     /etc/dnsmasq.d/network-manager
is
    bind-interfaces

I don't know how to tell if there's another dnsmasq process running at the time.

There is one file
     /run/resolvconf/interface/
it is
     NetworkManager
which contains one line
    nameserver 127.0.1.1

The "bind9" package is not installed.

Is anything further incomplete about this bug report?

[Ionică Bizău (bizauionica)]

Still happens for me on Ubuntu 14.04... :-(

[apostle (apostlesq)]

@#10

Running 'Ubuntu 14.04' (it's a fresh installation, not an upgrade);
'dnsmasq' package is not installed by default;
'dnsmasq-base' package is installed by default.

syslog at boot, regularly:
NetworkManager[870]: <error> [1402564901.517900] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
NetworkManager[870]: <warn> DNS: plugin dnsmasq update failed

The workaround proposed by #10 refers to 'dnsmasq', as if it was installed.
In my case 'dnsmasq' it's not installed, is it ok to try with 'dnsmasq-base'?

Thank you

[Mathieu Trudel-Lapierre (cyphermox)]

The thing is, this error in and of itself is not a problem, it's just traces of what NetworkManager is doing, to start dnsmasq on boot. The fact that this message is showing is not a bug.

However, if you don't get nameservers properly set (ie. Firefox or Chrome can't resolve web addresses), then I'd like you to please file your own bug so we can get to the bottom of it. Use 'ubuntu-bug network-manager' to do so, so all the necessary information will be there to debug the problems.

This isn't an issue with dnsmasq itself or dnsmasq-base (the latter being more likely the package installed on your system). Please don't purge and reinstall these packages unless requested by a developer: it's not likely to change much.

[Mathieu Trudel-Lapierre (cyphermox)]

Setting this back to incomplete so we don't miss comments, but please file new bugs for any issues you find -- piling comments on older bugs, for different machines and circumstances make debugging very hard.

Thanks!

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[Gannet (ken20001)]

Kubuntu 14.10
Linux 3.18.RC1 x86_64

The same issue:

grep -i error /var/log/syslog

Oct 24 03:15:29 p5q3 NetworkManager[1064]: <error> [1414109729.384414] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Oct 24 16:26:52 p5q3 NetworkManager[1040]: <error> [1414157212.476590] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name

[Laurent Bonnaud (laurent-bonnaud)]

This bug still exists in Ubuntu 15.04. Here is what I see in journalctl:

Apr 21 22:01:15 xeelee NetworkManager[1493]: <warn> dnsmasq not available on the bus, can't update servers.
Apr 21 22:01:15 xeelee NetworkManager[1493]: <error> [1429646475.907895] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Apr 21 22:01:15 xeelee NetworkManager[1493]: <warn> DNS: plugin dnsmasq update failed

[Anton Reshin (anton-reshin)]

Wow! I thought that this bug was corrected about three years ago!
Since 2012 I do not use my "big" computer as WiFi router, so this
problem was disappeared from my horizon...

Anton

2015-04-22 15:42 GMT+03:00, Laurent Bonnaud <email address hidden>:
> This bug still exists in Ubuntu 15.04. Here is what I see in
> journalctl:
>
> Apr 21 22:01:15 xeelee NetworkManager[1493]: <warn> dnsmasq not available on
> the bus, can't update servers.
> Apr 21 22:01:15 xeelee NetworkManager[1493]: <error> [1429646475.907895]
> [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus:
> Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no
> such name
> Apr 21 22:01:15 xeelee NetworkManager[1493]: <warn> DNS: plugin dnsmasq
> update failed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1048430
>
> Title:
> "dnsmasq not available on the bus"
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> Dnsmasq seems to be having some issues. This occurs whenever I try to
> connect to my wireless network; sometimes it only happens once, but
> sometimes the error loops for a while.
>
> Sep 9 17:43:51 bkerensa NetworkManager[935]: <info> DNS: starting
> dnsmasq...
> Sep 9 17:43:51 bkerensa NetworkManager[935]: <error> [1347237831.899067]
> [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't
> update servers.
> Sep 9 17:43:51 bkerensa NetworkManager[935]: <error> [1347237831.899142]
> [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not
> get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
> Sep 9 17:43:51 bkerensa NetworkManager[935]: <warn> DNS: plugin dnsmasq
> update failed
> Sep 9 17:43:51 bkerensa NetworkManager[935]: <info> ((null)): writing
> resolv.conf to /sbin/resolvconf
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: dnsmasq (not installed)
> ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
> Uname: Linux 3.5.0-13-generic x86_64
> ApportVersion: 2.5.1-0ubuntu7
> Architecture: amd64
> Date: Sun Sep 9 17:47:22 2012
> EcryptfsInUse: Yes
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
> (20120425)
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: dnsmasq
> UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions
>

[Gannet (ken20001)]

The same is on Kubuntu 15.04:

NetworkManager[783]: <error> [1431508253.012747] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name

[Vindicator (vindicator)]

Same here while trying to follow: https://seravo.fi/2014/create-wireless-access-point-hostapd

[Stéphane Berthelot (sberthelot)]

I also encounter this bug on fresh Kubuntu 15.04 install. I'm on SSD I don't know if the daemons starting speed has somthing to do with this.
I suppose NM gets the DNS info (from DHCP), tries to notify dnsmasq. Since dnsmasq is not yet started it launches it but I don't see any retry afterwards to send DNS info to dnsmasq once started.
The symptoms for me are working IP stacks (both 4 and 6), correct routing, but with all DNS requests "refused" (by 127.0.1.1).
Restarting NM after makes everything work as expected (dnsmasq is then already started)
How can I see if NM retries to pass the DNS info to dnsmasq once started ?

That's what I get on boot, nothing about NM or dnsmasq after, until I restart NM service.

juil. 22 09:27:17 architect NetworkManager[973]: <info> NetworkManager state is now CONNECTED_LOCAL
juil. 22 09:27:17 architect NetworkManager[973]: <info> NetworkManager state is now CONNECTED_GLOBAL
juil. 22 09:27:17 architect NetworkManager[973]: <info> Policy set 'Connexion filaire 1' (eth0) as default for IPv6 routing and DNS.
juil. 22 09:27:17 architect NetworkManager[973]: <info> DNS: starting dnsmasq...
juil. 22 09:27:17 architect NetworkManager[973]: <warn> dnsmasq not available on the bus, can't update servers.
juil. 22 09:27:17 architect NetworkManager[973]: <error> [1437550037.972824] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner
juil. 22 09:27:17 architect NetworkManager[973]: <warn> DNS: plugin dnsmasq update failed
juil. 22 09:27:17 architect NetworkManager[973]: <info> Writing DNS information to /sbin/resolvconf
juil. 22 09:27:17 architect whoopsie[946]: [09:27:17] Cannot reach: https://daisy.ubuntu.com
juil. 22 09:27:17 architect dnsmasq[1150]: démarrage avec le cache désactivé (version 2.72)
juil. 22 09:27:17 architect dnsmasq[1150]: options à la compilation : IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ip
juil. 22 09:27:17 architect dnsmasq[1150]: Support DBus autorisé : connecté au bus système
juil. 22 09:27:17 architect dnsmasq[1150]: attention : aucun serveur amont n'est configuré
juil. 22 09:27:18 architect kernel: random: nonblocking pool is initialized
juil. 22 09:27:18 architect org.kde.kded5[1135]: Saving

[Laurent Bonnaud (laurent-bonnaud)]

This bug still exists in wily:

$ journalctl | grep dnsmasq
oct. 02 11:05:10 vougeot NetworkManager[1432]: <info> DNS: loaded plugin dnsmasq
oct. 02 11:05:10 vougeot dnsmasq[1621]: started, version 2.75 cachesize 150
oct. 02 11:05:10 vougeot dnsmasq[1621]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
oct. 02 11:05:10 vougeot dnsmasq-dhcp[1621]: DHCP, IP range 10.0.3.2 -- 10.0.3.254, lease time 1h
oct. 02 11:05:10 vougeot dnsmasq-dhcp[1621]: DHCP, sockets bound exclusively to interface lxcbr0
oct. 02 11:05:10 vougeot dnsmasq[1621]: no servers found in /etc/resolv.conf, will retry
oct. 02 11:05:10 vougeot dnsmasq[1621]: read /etc/hosts - 16 addresses
oct. 02 11:05:14 vougeot NetworkManager[1432]: <info> DNS: starting dnsmasq...
oct. 02 11:05:14 vougeot NetworkManager[1432]: <warn> dnsmasq not available on the bus, can't update servers.
oct. 02 11:05:14 vougeot NetworkManager[1432]: <error> [1443776714.530733] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
oct. 02 11:05:14 vougeot NetworkManager[1432]: <warn> DNS: plugin dnsmasq update failed
[many more error messages]

[TJ (tj)]

I've been looking at this on Wily with a user suffering the bug, and it looks at first glance to be a timing issue - namely, that NM doesn't wait long enough after starting dnsmasq to query the name on the bus.

The code is Ubuntu specific, and introduced via

debian/patches/0001-dns-use-DBus-to-make-dnsmasq-nameserver-changes.patch

[johnnynobody (engage1)]

I'm having the same issue on Ubuntu 64 bit 14.04.03.

user@xps15:~$ uname -a
Linux xps15 3.19.0-47-generic #53~14.04.1-Ubuntu SMP Mon Jan 18 16:09:14 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

user@xps15:~$ cat /var/log/syslog | grep dnsmasq
Jan 23 10:19:48 xps15 NetworkManager[883]: <warn> DNS: plugin dnsmasq update failed
Jan 23 10:19:48 xps15 dnsmasq[2831]: setting upstream servers from DBus
Jan 23 10:19:48 xps15 dnsmasq[2831]: exiting on receipt of SIGTERM
Jan 23 10:20:05 xps15 NetworkManager[3753]: <info> DNS: loaded plugin dnsmasq
Jan 23 10:20:10 xps15 NetworkManager[3753]: <info> DNS: starting dnsmasq...
Jan 23 10:20:10 xps15 NetworkManager[3753]: <warn> dnsmasq not available on the bus, can't update servers.
Jan 23 10:20:10 xps15 NetworkManager[3753]: <error> [1453569610.971673] [nm-dns-dnsmasq.c:396] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Jan 23 10:20:10 xps15 NetworkManager[3753]: <warn> DNS: plugin dnsmasq update failed
Jan 23 10:20:10 xps15 dnsmasq[3764]: started, version 2.68 cachesize 1000
Jan 23 10:20:10 xps15 dnsmasq[3764]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth
Jan 23 10:20:10 xps15 dnsmasq[3764]: DBus support enabled: connected to system bus
Jan 23 10:20:10 xps15 dnsmasq[3764]: warning: no upstream servers configured
Jan 23 10:20:10 xps15 dnsmasq[3764]: cleared cache
Jan 23 10:20:11 xps15 NetworkManager[3753]: <warn> dnsmasq appeared on DBus: :1.98
Jan 23 10:20:11 xps15 dnsmasq[3764]: setting upstream servers from DBus
Jan 23 10:20:11 xps15 dnsmasq[3764]: using nameserver 127.0.2.1#53

user@xps15:~$ dpkg -l network-manager
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii network-manage 0.9.8.8-0ubu amd64 network management framework (dae

user@xps15:~$ dpkg -l dnsmasq-base
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii dnsmasq-base 2.68-1ubuntu amd64 Small caching DNS proxy and DHCP/

[johnnynobody (engage1)]

user@xps15:~$ apt-show-versions network-manager
network-manager:amd64/trusty-updates 0.9.8.8-0ubuntu7.2 uptodate
user@xps15:~$ apt-show-versions dnsmasq-base
dnsmasq-base:amd64/trusty-security 2.68-1ubuntu0.1 uptodate

[gberche (guillaume-berche)]

I had a similar issue after upgrading from 15.04 to 15.10 yesterday

I was loosing DNS resolution ramdomly few minutes after VM start

Mar 18 10:27:17 guillaume-box NetworkManager[885]: <info> DNS: starting dnsmasq...
Mar 18 10:27:17 guillaume-box NetworkManager[885]: <warn> dnsmasq not available on the bus, can't update servers.
Mar 18 10:27:17 guillaume-box NetworkManager[885]: <error> [1458293237.010557] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Mar 18 10:27:17 guillaume-box NetworkManager[885]: <warn> DNS: plugin dnsmasq update failed
Mar 18 10:27:17 guillaume-box NetworkManager[885]: <info> Writing DNS information to /sbin/resolvconf
[...]
Mar 18 10:27:17 guillaume-box dnsmasq[965]: DBus support enabled: connected to system bus
Mar 18 10:27:17 guillaume-box dnsmasq[965]: warning: no upstream servers configured

I was observing, dnsmaq process indeed running but not consistently resolving name requests. I was observing empty dnsmasq conf files:

guillaume@guillaume-box:/etc/NetworkManager/dnsmasq.d$ ls -al
total 8
drwxr-xr-x 2 root root 4096 avril 17 2015 .
drwxr-xr-x 7 root root 4096 mars 17 23:11 ..
guillaume@guillaume-box:/etc/NetworkManager/dnsmasq.d$ ls -al /var/run/NetworkManager/dnsmasq.conf
-rw-r--r-- 1 root root 0 mars 18 10:27 /var/run/NetworkManager/dnsmasq.conf

Whereas the network manager was properly displaying the DHCP provided DNS servers in the its UI.

Trying to turn off and on network in the network manager did not solve the issue.

I ended up turning off dnsmasq by eding /etc/NetworkManager/NetworkManager.conf and comment out the following line from
    dns=dnsmasq (as suggested into http://www.ubuntugeek.com/how-to-disable-dnsmasq-in-ubuntu-12-04precise.html)

This seems to have worked around the issue. I understand the limitation of the workaround (disabling dnsmasq) is that I don't have anymore a local DNS cache, and only the 1st respondind DNS server is queried for address resolution.

I ran into a reported bug (sorry I lost its reference) that claimed this to be a distribution upgrade problem, and was suggesting to uninstall dsnmaq and reinstall it. I haven't tried yet.

Hope this helps narrowing this nasty bug which was quite time consuming to me.

[Laurent Bonnaud (laurent-bonnaud)]

This bug no longer exists in yakkety:

# journalctl -b |grep dnsmasq
Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" operation="profile_load" name="/usr/sbin/dnsmasq" pid=1052 comm="apparmor_parser"
Feb 26 20:12:47 xeelee audit[1052]: AVC apparmor="STATUS" operation="profile_load" name="/usr/sbin/dnsmasq//libvirt_leaseshelper" pid=1052 comm="apparmor_parser"
Feb 26 20:12:47 xeelee NetworkManager[1088]: <info> [1488136367.5567] dns-mgr[0x55d53a357a80]: init: dns=dnsmasq, rc-manager=resolvconf, plugin=dnsmasq
Feb 26 20:12:50 xeelee NetworkManager[1088]: <info> [1488136370.2108] dns-plugin[0x55d53a37b500]: starting dnsmasq...
Feb 26 20:12:50 xeelee dnsmasq[1397]: started, version 2.76 cachesize 1000
Feb 26 20:12:50 xeelee dnsmasq[1397]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
Feb 26 20:12:50 xeelee dnsmasq[1397]: DBus support enabled: connected to system bus
Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.4.4#53
Feb 26 20:12:50 xeelee dnsmasq[1397]: using nameserver 8.8.8.8#53
Feb 26 20:12:50 xeelee dnsmasq[1397]: cleared cache
Feb 26 20:12:50 xeelee NetworkManager[1088]: <info> [1488136370.2832] dnsmasq[0x55d53a37b500]: dnsmasq appeared as :1.13
Feb 26 20:12:50 xeelee dnsmasq[1397]: setting upstream servers from DBus
[...]

[Karsten S. Opdal (karsten-s-opdal)]

Just had the same problem on a embedded system with network-manager system install. I had to disable use of an IPv4 setting called "never-default" when I set it to "true" this bug occurred. Might be the problem.