Comment 38 for bug 93360

Revision history for this message
Skou (skou) wrote : Re: Dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason

I can confirm this issue on Gusty 2.6.22-14-generic with a wireless connection.
Just upgraded to Gusty from Feisty. A snip from /var/log/messages:
Oct 24 21:01:40 AMD-XP-1700 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_domain
Oct 24 21:01:40 AMD-XP-1700 dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.nis_servers

I don't know if this is what is causing my problem, but it seems that randomly I can not resolve domain names.
This seems to happen if I'm checking for package updates. The following output is from before checking for updates:
$ ping google.com
PING google.com (72.14.207.99) 56(84) bytes of data.
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=1 ttl=237 time=107 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=2 ttl=237 time=107 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=3 ttl=237 time=107 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=4 ttl=237 time=107 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 107.003/107.332/107.663/0.341 ms

And after checking for updates, which by the way fails, I get the following:
$ date && ping google.com
ons okt 24 21:43:01 CEST 2007
ping: unknown host google.com
$ date && ping -c4 72.14.207.99
ons okt 24 21:43:36 CEST 2007
PING 72.14.207.99 (72.14.207.99) 56(84) bytes of data.
64 bytes from 72.14.207.99: icmp_seq=1 ttl=237 time=106 ms
64 bytes from 72.14.207.99: icmp_seq=2 ttl=237 time=105 ms
64 bytes from 72.14.207.99: icmp_seq=3 ttl=237 time=105 ms
64 bytes from 72.14.207.99: icmp_seq=4 ttl=237 time=105 ms

--- 72.14.207.99 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 105.249/105.804/106.635/0.686 ms

So somehow something is triggering domain name lookup to fail.

By the way, restarting NetworkManager solves the problem temporary.

Any one got a similar problem?