You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Frank Ren (JIRA)" <ji...@apache.org> on 2013/06/30 07:26:20 UTC

[jira] [Commented] (DIRSERVER-1835) ApacheDS not able to restart/start when the process shown in apacheds-default.pid is not running

    [ https://issues.apache.org/jira/browse/DIRSERVER-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696276#comment-13696276 ] 

Frank Ren commented on DIRSERVER-1835:
--------------------------------------

I need to delete the file, /var/lib/apacheds-2.0.0-M11/default/run/apacheds-default.pid, manually. It won't be deleted automatically by rebooting the operation system. It's suggested to improve the start script, so that it can detect stale pid. Here is a sample output from tomcat6 start script in similar situation.

 * Tomcat servlet engine is not running, but pid file exists.

Upon restarting, tomcat6 just ignores the stale pid as if it doesn't exist.
                
> ApacheDS not able to restart/start when the process shown in apacheds-default.pid is not running
> ------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1835
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1835
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M11
>         Environment: Linux CentOS
>            Reporter: James C. Wu
>            Priority: Minor
>
> I have a default instance of ApacheDS 2.0.0.M11. 
> I could not restart the apacheDS service using 
> /etc/init.d/apacheds-2.0.0-M11-default restart or /etc/init.d/apacheds-2.0.0-M11-default start
> after a system reboot. 
> The problem is fixed by deleting the pid stored in the  apacheds-default.pid file /var/lib/apacheds-2.0.0-M11/default/run/apacheds-default.pid

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira