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

ASF GitHub Bot commented on SOLR-7169:
--------------------------------------

GitHub user dsiebel opened a pull request:

    https://github.com/apache/lucene-solr/pull/212

    SOLR-7169: Use proper exit code in `status` command to signal process status

    As reported in [SOLR-7169](https://issues.apache.org/jira/browse/SOLR-7169) 
the solr run script always return `0` as exit code. This causes provisioners 
like Puppet or Saltstack assume that he process is already running.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dsiebel/lucene-solr 
SOLR-7169-proper-exit-code-for-runscript

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/212.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #212
    
----
commit b6d279ae19bf8d4c0cca8a0bcf0be50aa15ca3ec
Author: dsiebel <[email protected]>
Date:   2015-11-23T13:01:10Z

    SOLR-7169 use proper exit code in `status` command to signal process status

----


> init.d status command has incorrect return value
> ------------------------------------------------
>
>                 Key: SOLR-7169
>                 URL: https://issues.apache.org/jira/browse/SOLR-7169
>             Project: Solr
>          Issue Type: Bug
>          Components: scripts and tools
>    Affects Versions: 5.0
>         Environment: Debian stable
>            Reporter: Martin Skøtt
>            Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according 
> to the LSB 0 means that the service is running 
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet 
> which uses the status command to determine if a service should be started. 
> Puppet simply doesn't start the service because it thinks its already 
> running. Any other script depending on the result of the status command will 
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the 
> service definition works for me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to