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.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags removed: quantal wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048430
Title:
"dnsmasq not available on the bus"
To manage notifications about this bug go to:
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"
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048430
Title:
"dnsmasq not available on the bus"
To manage notifications about this bug go to:
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048430
Title:
"dnsmasq not available on the bus"
To manage notifications about this bug go to:
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]: DNS: starting
dnsmasq...
Mar 18 10:27:17 guillaume-box NetworkManager[885]: dnsmasq not
available on the
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]: DNS: plugin
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
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
This bug still exists in wily:
$ journalctl | grep dnsmasq
oct. 02 11:05:10 vougeot NetworkManager[1432]: 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
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
Same here while trying to follow: https://seravo.fi/2014/create-
wireless-access-point-hostapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048430
Title:
dnsmasq not available on the bus
To
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
--
You received this bug notification because you are a
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():
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 l.bonn...@laposte.net:
This bug still exists in Ubuntu 15.04. Here is
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
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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!
** Changed in: network-manager (Ubuntu)
Status: Expired = Incomplete
--
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
@#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
Still happens for me on Ubuntu 14.04... :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048430
Title:
dnsmasq not available on the bus
To manage notifications about this bug go to:
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,
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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!
--
You received this bug
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
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
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
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.
@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
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
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.
@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
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
@Benjamin: Hi. Please reboot, reproduce the problem, then run apport-
collect 1048430 to submit relevant information about the affected
machine.
** Description changed:
- Dnsmasq seems to be having some issues this occurs whenever I try to
- connect to my wireless network and sometimes it only
@Benjamin: Hi. Please reboot, reproduce the problem, then run apport-
collect 1048430 to submit relevant information about the affected
machine.
** Description changed:
- Dnsmasq seems to be having some issues this occurs whenever I try to
- connect to my wireless network and sometimes it only
38 matches
Mail list logo
