Bug 452550 - dhcpd no longer starts from startup script
dhcpd no longer starts from startup script
Status: CLOSED DUPLICATE of bug 448014
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: dhcp (Show other bugs)
x86_64 Linux
low Severity high
: rc
: ---
Assigned To: David Cantrell
Depends On: 448014
  Show dependency treegraph
Reported: 2008-06-23 13:38 EDT by Colin Simpson
Modified: 2008-06-25 09:15 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-25 09:15:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Colin Simpson 2008-06-23 13:38:14 EDT
Description of problem:
On boot or by running command /etc/init.d/dhcpd start, dhcpd
claims to start but isn't running when you ps for it.

Version-Release number of selected component (if applicable):
Version RH Enterprise Linux Server release 5.2

How reproducible:
Every time

Steps to Reproduce:
1. Run /etc/init.d/dhcpd restart
2. Claims to have started.
3. ps -ef  |grep dhcp , it isn't running. 
Actual results:
This seems to be a regression, as it worked in 5.1, failed on 5.2 update.

Expected results:
Daemon to be running. 

Additional info:

The daemon seems to start up i.e it puts the correct log entries into
/var/log/messages. It looks like it's the forked child that dies. The program
runs fine with a "-f" flag put in. In fact my present workaround is rather
horrible with:

daemon $dhcpd $DHCPDARGS -f 2>/dev/null &
, in the startup file.
Comment 1 Colin Simpson 2008-06-25 05:32:43 EDT
Replying to my own problem, this seem to be related to and caused by Bug
#448014. Downgrading to nss_ldap-253-5.el5 resolved this issue. 
Comment 2 David Cantrell 2008-06-25 09:15:13 EDT

*** This bug has been marked as a duplicate of 448014 ***

Note You need to log in before you can comment on or make changes to this bug.