Description of problem: NetworkManager loops forever if dhcdbd isn't running, continuously hitting the hard drive (mostly like logging output). Version-Release number of selected component (if applicable): NetworkManager-0.6.4-5.fc6 How reproducible: Always Steps to Reproduce: 1. service dhcdbd stop 2. killall NetworkManager 3. NetworkManager --no-daemon Actual results: <information> Will activate connection 'eth0'. <information> Device eth0 activation scheduled... <information> Activation (eth0) started... <information> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... <information> Activation (eth0) Stage 1 of 5 (Device Prepare) started... <information> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... <information> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. <information> Activation (eth0) Stage 2 of 5 (Device Configure) starting... <information> Activation (eth0) Stage 2 of 5 (Device Configure) successful. <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. <information> Activation (eth0) Stage 2 of 5 (Device Configure) complete. <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... <WARNING> nm_dhcp_manager_begin_transaction (): dhcdbd not running! <information> Activation (eth0) failure scheduled... <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. <information> Activation (eth0) failed. <information> Deactivating device eth0. <information> SWITCH: no current connection, found better connection 'eth0'. <WARNING> nm_dhcp_manager_get_state_for_device (): dhcdbd not running! Expected results: I would like NetworkManager to somehow notify me of a problem rather than looping. Additional info:
NetworkManager-0.6.5-0.cvs20061025.fc7 removes the code to start dhcdbd in /etc/init.d/NetworkManager, causing this situation. Should dhcdbd be started before NetworkManager, or should this revert back? tom --- /tmp/NetworkManager 2006-10-27 06:32:04.000000000 -0700 +++ ./NetworkManager 2006-10-24 22:35:42.000000000 -0700 @@ -36,11 +36,6 @@ { echo $"Setting network parameters... " sysctl -e -p /etc/sysctl.conf >/dev/null 2>&1 - - if [ ! -e /var/lock/subsys/dhcdbd ]; then - service dhcdbd start - fi - echo -n $"Starting NetworkManager daemon: " daemon --check $servicename $processname --pid-file=$pidfile RETVAL=$?
In my case, the services had been setup, but not made to start when the init level changed. So when I started NetworkManager from the command line (as root), the service dhcdbd was not running. This condition should be handled or the rpms should add the up levels and start the service when they are installed.
Also, its not clear that when you enable the NetworkManager service you ALSO have to enable the dhcdbd service. And unlike before, one can't just start NetworkManager and use it, now one has to start NetworkManager _and_ dhcdbd. This should be fixed before Test1.
This isn't fixed in development as of 2/26/2007. dhcdbd-2.5-1.fc7 Build Date: Thu 08 Feb 2007 10:41:24 AM EST NetworkManager-0.6.5-0.3.cvs20061025.fc7 Build Date: Thu 08 Feb 2007 02:58:56 PM EST
Yeah, I'm getting it too. Update from fc6->rawhide, this service was not configfured to run on start.
This looks like a duplicate, just thought i'd save you guys time and close it, reopen if its not. *** This bug has been marked as a duplicate of 204322 ***