Bug 246647

Summary: Can't start DS when PID in the PID files matches the PID of non-DS process
Product: [Retired] 389 Reporter: Noriko Hosoi <nhosoi>
Component: Command Line UtilitiesAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED DUPLICATE QA Contact: Orla Hegarty <ohegarty>
Severity: low Docs Contact:
Priority: low    
Version: 1.0.4CC: taruishi
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-07-03 19:11:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 152373, 240316    

Description Noriko Hosoi 2007-07-03 16:57:27 UTC 
Description of problem:
When the Directory Server abnormally exits and leaves PID files, the pid rarely
matches the pid of other existing process.  It prevents the server's start.

Step to reproduce:
$ ps -ef | egrep 1111
nhosoi    1111  9492  0 Jun22 pts/2    00:00:00 vim bogus
# stop the server:
$ lib/fedora-ds/slapd-laputa/stop-slapd
# create pid files that store the existing pid 1111:
$ echo 1111 > var/run/fedora-ds/slapd-laputa.pid
$ echo 1111 > var/run/fedora-ds/slapd-laputa.startpid
# start the server:
$ lib/fedora-ds/slapd-laputa/start-slapd
There is an ns-slapd process already running: 1111

The check is being done in start-slapd.  We could check the process name and
remove the pid files and start the server if the process is not ns-slapd.
Comment 1 Noriko Hosoi 2007-07-03 19:11:54 UTC 

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