[
https://issues.apache.org/jira/browse/DIRSERVER-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144600#comment-15144600
]
Peter Jamieson commented on DIRSERVER-1843:
-------------------------------------------
have noticed that the function to clean this up is commented out: -
{code}
getpid() {
if [ -f "$PIDFILE" ]
then
if [ -r "$PIDFILE" ]
then
pid=`cat "$PIDFILE"`
#if [ "X$pid" != "X" ]
#then
# # It is possible that 'a' process with the pid exists but that
it is not the
# # correct process. This can happen in a number of cases, but
the most
# # common is during system startup after an unclean shutdown.
# # The ps statement below looks for the specific wrapper
command running as
# # the pid. If it is not found then the pid file is
considered to be stale.
# pidtest=`$PSEXE -p $pid -o args | grep "$WRAPPER_CMD" | tail
-1`
# if [ "X$pidtest" = "X" ]
# then
# # This is a stale pid file.
# rm -f "$PIDFILE"
# echo "Removed stale pid file: $PIDFILE"
# pid=""
# fi
#fi
else
echo "Cannot read $PIDFILE."
exit 1
fi
fi
}
{code}
> Unable to Start/Stop Apache DS on RHEL
> --------------------------------------
>
> Key: DIRSERVER-1843
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1843
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M10
> Environment: RHEL 6.1
> Reporter: RakeshAcharya
> Priority: Blocker
>
> Unable to start/Stop apache DS, there seems to be a stale process running
> even after restarting the server it didn't resolve the issue.
> STOP:
> [root]# sudo service apacheds-2.0.0_M10-default restart
> Stopping ApacheDS - default...
> /opt/apacheds-2.0.0_M10/bin/apacheds: line 418: kill: (8440) - No such process
> Unable to stop ApacheDS - default.
> START:
> [root@]# sudo service apacheds-2.0.0_M10-default start
> Starting ApacheDS - default...
> ApacheDS - default is already running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
