[
https://issues.apache.org/jira/browse/BIGTOP-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470776#comment-13470776
]
Roman Shaposhnik commented on BIGTOP-729:
-----------------------------------------
Brian, this is definitely unsettling. Now, the good news is that we've got
BIGTOP-22 (which I really hope to fix for the upcoming Bigtop 0.5.0 release).
As part of that JIRA I would like to transition to the LSB-compliant code for
checking status of services, etc.
> zookeeper initd script status doesn't work
> ------------------------------------------
>
> Key: BIGTOP-729
> URL: https://issues.apache.org/jira/browse/BIGTOP-729
> Project: Bigtop
> Issue Type: Bug
> Components: Init scripts
> Reporter: Brian Sutherland
> Priority: Minor
>
> I have a situation where puppet is continually attempting to restart
> zookeeper. It appears as if {{/etc/init.d/zookeeper-server status}} returns
> the wrong answer in some cases. I can workaround this by setting the COLUMNS
> environment variable just before the {{ps}} in hadoop_is_process_alive().
> What is actually setting (or unsetting) this is a mystery, but I don't think
> its right for the init script to break.
> {noformat}
> $ COLUMNS=80 ps -fp 2539 | grep 2539 | grep zookeeper >/dev/null ; echo $?
> 1
> $ COLUMNS=1000 ps -fp 2539 | grep 2539 | grep zookeeper >/dev/null ; echo $?
> 0
> {noformat}
> It seems to me as if this method of using ps to check the daemon status is
> too fragile.
--
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
