Rejected send message, 10 matched rules; type="method_return", sender=":1.84"

[Michael Heuberger]

Seeing lots of those log entries. Here an example

Aug 24 20:14:36 M1 NetworkManager[748]: <error> [1440404076.494991] [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

Aug 24 20:14:36 M1 dbus[792]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.84" (uid=0 pid=3300 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=748 comm="/usr/sbin/NetworkManager --no-daemon ")

Attached info might help locating the issue. Thanks for any clues.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dnsmasq 2.72-3ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
Date: Mon Aug 24 23:08:37 2015
InstallationDate: Installed on 2014-10-31 (297 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Importance -> Low for now, since the only reported user impact is additional log entries.

[Jean-Pierre Rupp (xenog)]

When connecting to an OpenVPN network with NetworkManager, I see these same messages just after dnsmasq reports "using nameserver ...," then the system fails to use those nameservers. This means that my system is not using the DNS servers that correspond to the VPN, but those that were already set in the system. The upgrade that caused this must have happened earlier today. It was working fine less than two hours ago.

[Jean-Pierre Rupp (xenog)]

Possible culprits:

libdns100_1:9.9.5.dfsg-9ubuntu0.3_amd64.deb
libdns-export100_1:9.9.5.dfsg-9ubuntu0.3_amd64.deb

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jean-Pierre Rupp (xenog)]

I downgraded these packages and the problem got solved:

libbind9-90
dnsutils
libisccfg90
libdns100
libisc95
liblwres90
bind9-host

Version those packages downgraded to: 1:9.9.5.dfsg-9

[Jean-Pierre Rupp (xenog)]

I have determined it is one of the packages related to bind9, as comments show.

[Michael Heuberger (michael.heuberger)]

Jean-Pierre, what if I do not want to downgrade these? Is a new update planned with a bugfix for this?

[Jean-Pierre Rupp (xenog)]

I have no idea, I am just a guy that happened to do a little research on this bug. I do not maintain this package and I haven't read its source code.

[Michael Heuberger (michael.heuberger)]

Who then maintains this package?

[Robie Basak (racb)]

@Jean-Pierre:

You downgraded those packages from what version? Please could you confirm what versions work and what versions don't? I've also looked at the changelog entries for the security updates that were applied to bind9 in 15.04 since release, and none of the changes seem related. So it seems unlikely to me to be the culprit. On this basis, please could you double check that this change, and no other change, is causing you a regression?

For example, please:

1) Reboot, follow your reproduction steps and confirm that the failure does not reproduce.
2) Upgrade bind9 packages (and nothing else) to the latest updates.
3) Reboot, follow your reproduction steps (exactly as in step 1) and confirm that the failure does reproduce the issue.

Please report exactly what you did to reproduce the issue, the output of "dpkg -l" for each of the cases when you can reproduce and when you cannot reproduce, and then set the bug status back to New. Thanks!

[Robie Basak (racb)]

Importance -> High since you are now reporting a regression in DNS resolution after an update, rather than just spurious log messages.

[Jean-Pierre Rupp (xenog)]

I removed the holds on all aforementioned packages, and upgraded them to the latest versions from repositories a few minutes ago. I am not experiencing problems anymore. DNS works fine.

[Michael Heuberger (michael.heuberger)]

@Jean-Pierre Great! When will this be available via apt-get? This bug is bugging me for a long time ...

[Jean-Pierre Rupp (xenog)]

@michael.heuberger, it works fine for me already with the packages currently available from the Ubuntu repositories. If you downgraded the DNS packages, you can upgrade them to the latest version. It works very well for me. Just upgrade your whole Ubuntu 15.04 system.

[Michael Heuberger (michael.heuberger)]

i already have the latest ubuntu 15.04 - my log files should indicate this. still, i experience weird dns issues.

[Launchpad Janitor (janitor)]

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

[Dana Goyette (danagoyette)]

I have an Ubuntu 15.10 that's up to date, and I'm still seeing the "rejected" message.

The seemingly most relevant file is /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, from the network-manager config file. None of the rules in that file seem to handle all the "(unset)" fields.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[axonic (guiltypixel-com)]

Also affecting Kubuntu 16.04 (kubuntu 15.10+dist-upgrade)

dbus[] [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.47" (uid=0 pid=2075 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.2" (uid=0 pid=846 comm="/usr/sbin/NetworkManager --no-daemon ")