cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Paetow (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13436) Stopping Cassandra shows status "failed" due to non-zero exit status
Date Wed, 12 Jul 2017 13:45:00 GMT


Felix Paetow commented on CASSANDRA-13436:

[~muru] thank you for this, exactly what I was looking for. There's still a peace missing
though. In our setup I have multiple services that have to start in the moment the cassandra
database is up and reachable. Do you know a way to ensure this? Is there a parameter for the
startup script that I missed?

Otherwise my services will fail to start because of the "Type=forking".

> Stopping Cassandra shows status "failed" due to non-zero exit status
> --------------------------------------------------------------------
>                 Key: CASSANDRA-13436
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message