[
https://issues.apache.org/jira/browse/CASSANDRA-13436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092933#comment-16092933
]
Felix Paetow edited comment on CASSANDRA-13436 at 7/19/17 11:34 AM:
--------------------------------------------------------------------
ok, my solution is now to add
{code:bash}
ExecStartPost=cqlsh -e exit
{code}
The cqlsh statemant is in a while loop though.
But I'm still not sure if this is the best way to test cassandra is up and
reachable. Any suggestions?
was (Author: hoall):
ok, my solution is now to add
{code:bash}
ExecStartPost=cqlsh -e exit
{code}
But I'm still not sure if this is the best way to test cassandra is up and
reachable. Any suggestions?
> Stopping Cassandra shows status "failed" due to non-zero exit status
> --------------------------------------------------------------------
>
> Key: CASSANDRA-13436
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13436
> Project: Cassandra
> Issue Type: Sub-task
> Components: Packaging
> Reporter: Stefan Podkowinski
>
> Systemd will monitor the process from the pid file and save the return status
> once if has been stopped. In case the process terminates with a status other
> than zero, it will assume the process terminated abnormaly. Stopping
> Cassandra using the cassandra script will send a kill signal to the JVM
> causing it to terminate. If this happen, the JVM will exit with status 143,
> no matter if shutdown hooks have been executed or not. In order to make
> systemd recognize this as a normal exit code, the following should be added
> to the yet to be created unit file:
> {noformat}
> [Service]
> ...
> SuccessExitStatus=0 143
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
