lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Skøtt (JIRA) <j...@apache.org>
Subject [jira] [Updated] (SOLR-7169) init.d status command has incorrect return value
Date Thu, 26 Feb 2015 22:41:05 GMT

     [ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Skøtt updated SOLR-7169:
-------------------------------
    Description: 
{{/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.



  was:
{{/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.




> 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
>
> {{/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.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message