Description of problem: Unable to do a service network stop and service network start successfully after booting. Version-Release number of selected component (if applicable): RHEL5.2-Server-20080313.0 How reproducible: Always Steps to Reproduce: 1. service network stop 2. service network start Actual results: The start will fail because dhclient is already running. It was restarted by netplugd over dbus. Expected results: Should work the same way it did in RHEL5.1 Additional info:
The difference here seems that we are starting netplugd by default now. Seems netplugd shouldn't monitor an interface if its not configured to.
Hi Bill, are you sure that this worked before. I'm not able to see the problem you are experiencing. The only change which was done in netplugd init script is the following shift of network test to start section --- net-tools-1.60/netplug-1.2.9/scripts/rc.netplugd.old 2007-06-08 13:03:45.000000000 +0200 +++ net-tools-1.60/netplug-1.2.9/scripts/rc.netplugd 2007-06-08 13:04:01.000000000 +0200 @@ -17,11 +17,6 @@ # Source networking configuration. . /etc/sysconfig/network -# Check that networking is up. -[ ${NETWORKING} = "no" ] && exit 0 - -[ -x /sbin/netplugd ] || exit 0 - if [ -f /etc/sysconfig/netplugd ]; then . /etc/sysconfig/netplugd fi @@ -30,6 +25,8 @@ case "$1" in start) # Start daemon. + [ ${NETWORKING} = "no" ] && exit 1 + [ -x /sbin/netplugd ] || exit 1 echo -n $"Starting network plug daemon: " daemon /sbin/netplugd ${NETPLUGDARGS} -p /var/run/netplugd.pid RETVAL=$? @@ -57,7 +54,7 @@
Steps to reproduce: Install RHEL5.2-Server-20080313.0. Log into the gnome (Start X) service netplugd start service network stop Service network start That should do it. Note on my system here netplugd was started or added to checkconfig "on" by something/someone other then me. I have reproduced this on a second system here. Jeff
It was set to "on" in my serviceconf and would start up automatically on my desktop. I specifically did not turn it on. So either it is on by default or another service enabled it. My desktop is the only place I run RHEL5.2 client. So I don't have a lot of data points.
I just did a test install of 5.2 snapshot 3 - netplugd is not started by default.
That is a great data point. It may not be as big of a issue in the field. I was wondering if you were able to duplicate it with the steps I put into Comment #3
I can duplicate the issue, but I can also duplicate it with the GA versions of net-tools and initscripts. Frankly, I think this is an unsupported configuration, similarly to attempting 'service network restart' while NetworkManager is running; it's intentionally enabling conflicting services. Now, if something is causing netplugd to be enabled by default, we need to fix that. But without reproducing that, I can't say what the fix would be. Jeff: does 'chkconfig netplugd reset' disable the service for you? Can you reproduce it being enabled across other installations? If so, may need a dump of the packages that you're installing.
Jeff: does 'chkconfig netplugd reset' disable the service for you? - Yes it did disable it. I have not duplicated it with out manually starting netplugd. I am at a loss as to how netplugd was enabled. It was very coincidental to my yum update to RHEL5.2 beta from U1. Bill: If you want to close this as NOTABUG since I can't duplicate it on a RHEL5.2 install. Or do you think a kb article in this case would be a safe way to go?
Not sure aboug a kb article; if we did, we'd need one for NetworkManager too.