Comment 2 for bug 93360

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

I have the same problem after upgrading to Feisty. As a result, avahi-daemon does not start when booting.

This is the relevant extract from syslog:

Mar 27 10:55:50 dedekind dhcdbd: Started up.
Mar 27 10:55:51 dedekind NetworkManager: <information>^Istarting...
Mar 27 10:55:51 dedekind NetworkManager: <information>^Ieth0: Device is fully-supported using driver 'skge'.
Mar 27 10:55:51 dedekind NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Mar 27 10:55:51 dedekind avahi-daemon[4935]: Found user 'avahi' (UID 105) and group 'avahi' (GID 109).
Mar 27 10:55:51 dedekind avahi-daemon[4935]: Successfully dropped root privileges.
Mar 27 10:55:51 dedekind NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Mar 27 10:55:51 dedekind NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Mar 27 10:55:51 dedekind NetworkManager: <information>^IDeactivating device eth0.
Mar 27 10:55:51 dedekind avahi-daemon[4935]: avahi-daemon 0.6.17 starting up.
Mar 27 10:55:51 dedekind dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Mar 27 10:56:16 dedekind NetworkManager: <information>^IError from dhcdbd on 'reason' request because: name 'org.freedesktop.DBus.Error.NoReply', message 'Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.'.
Mar 27 10:56:16 dedekind NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.
Mar 27 10:56:16 dedekind NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Mar 27 10:56:16 dedekind avahi-daemon[4935]: dbus_bus_get_private(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Mar 27 10:56:16 dedekind avahi-daemon[4935]: WARNING: Failed to contact D-Bus daemon.