[ https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027471#comment-15027471 ]
ASF GitHub Bot commented on SOLR-7169: -------------------------------------- Github user dsiebel commented on the pull request: https://github.com/apache/lucene-solr/pull/212#issuecomment-159714390 Changes merged via JIRA/SVN: * trunk: https://svn.apache.org/viewvc?view=revision&revision=r1716516 * branch_5x: https://svn.apache.org/viewvc?view=revision&revision=r1716517 * lucene_solr_5_4: https://svn.apache.org/viewvc?view=revision&revision=r1716518 > 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 > Fix For: 5.4 > > > {{/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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org