Table of Contents

Approved

  • 1. Download ASR Pro
  • 2. Open the program and select "Scan your computer"
  • 3. Click "Repair" to start the repair process
  • The software to fix your PC is just a click away - download it now.

    Over the past few days, some of our readers have come across a known bug where the dhcdbd message_handler message handler could not be found. This issue can occur for a number of reasons. We will review them now.

    description tomlondon 2005-10-05 14:11:33 UTC

    Approved

    The ASR Pro repair tool is the solution for a Windows PC that's running slowly, has registry issues, or is infected with malware. This powerful and easy-to-use tool can quickly diagnose and fix your PC, increasing performance, optimizing memory, and improving security in the process. Don't suffer from a sluggish computer any longer - try ASR Pro today!


    From Bugzilla Helper:User Agent: Mozilla/5.0 (X11; Linux u; i686; en-US; rv:1.8b4) Gecko/20050915 Fedora/1.5-0.5.0.beta1 Firefox/1.4Description of the problem:Execute a newly available rawhide by aiming/casting.I've noticed that dhcdbd seems sporadic at times (and crashes on startup when it comes to connecting to dbus, causing NetworkManager to crash when initializing my network connection.I found this later in /var/log/messagesOct 05 06:38:59 localhost dhcdbd: error dbus_svc_init: org.freedesktop.DBus.Error.NoServer Failed to connect directly to socket /var/run/dbus/system_bus_socket: Connection refusedOct 05 06:38:59 localhost dhcdbd: Failed to initialize D-Bus service.With an awesome start, I get the following (sometimes releases on eth0, sometimes on eth1, sometimes on both):Sep 29 07:05:17 localhost dhcdbd: running.Sep 29 07:05:18 localhost dhcdbd: text message message_handler: Handler for /com/redhat/dhcp/eth0 not found for subpath eth0.dbus.get.reasonSep 29 08:47:54 localhost Stop dhcdbd:down.I get around all of this with Eth0; ifdown ifup eth0 possibleIt is reloading.Viewing archived email files shows 29 as the new first occurrence.The version number of the corresponding selected version of the main component:Dhcdbd-1 (if.8-1How reproducible:SometimesPlayback steps:1. Getting Started2. Make sure Network Manager is starting/configuring eth0.3.  Additional Information:

    comment 1 Jason Vas Diaz 2005-10-05 16:34:53 UTC

    There seem to be a few problems here:1. Problems starting Dhcdbd on boot with initscript:> Oct 05 06:38:59 localhost dhcdbd: dbus_svc_init error:Error connecting to socket org.freedesktop.DBus.Error.NoServer/var/run/dbus/system_bus_socket: October connection refused> 5 06:38:59 localhost dhcdbd: Failed to initialize D-Bus service.These messages indicate that the dbus daemon (the real "messagebus" service)dhcdbd doesn't do any work while running.At the end you will need to run "chkconfig --add in dhcdbd" or'chkconfig a --levels=XYZ dhcdbd on' and'chkconfig a --levels=XYZ NetworkManager on' to enable itNetworkManager and later versions of dhcdbd - for which levelscan you turn it on?You need to check if the messagebus, dhcdbd and NetworkManager services are running.run in that order.Presumably the person is running dhcdbd and NetworkManager in runlevel 3 and not runlevel 2? ?(This would be a good idea since the message bus doesn't start until runlevel 3,while the "network" service is developed at runlevel 2).Please dial this number: echo /etc/rc.d/rc3.d/S*Order in which the messagebus, dhcdbd, and NetworkManager functions are locatedthe above is the specific command in the order they are executed.You must ensure that the output of the described command lists the servicesto: the same '...rc3.d/S97messagebus...rc3.d/S98dhcdbd...rc3.d/S98NetworkManager...'If this is not the case in all of our cases, run chkconfig commands to prepare it that way.2. Messages after startup:> On successful boot I get this method (sometimes messages about eth0, sometimesvia > eth1, sometimes both):> Sep 29 07:05:17 localhost dhcdbd: Started.> Sep 30 07:05:18 localhost dhcdbd: message_handler: message user not foundto /com/redhat/dhcp/eth0 for subpath eth0.dbus.get.reason> Sep 29 08:47:54 localhost dhcdbd: headwork eruption.These messages do not indicate situations where the dhcdbd stop message was long.The time after the "Message owner not found" message.This shows that immediately upon startup, NetworkManager prompts dhcdbd for settings.the eth0 interface, which was not usually configured at boot for spawning with dhcdbd, i.e.dhcdbd doesn't have the resources for this. Then NetworkManager should sometimes do "ifup"dhcdbd, develop and eth0 parameter are fine - usually you say it shouldn't becase is. eth0 not being passed correctly?

    comment 2 tomlondon 2005-10-05 16:59:13 UTC

    dhcdbd message_handler message handler not found under

    The software to fix your PC is just a click away - download it now.