You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Peter Halliday (JIRA)" <ji...@apache.org> on 2013/12/03 00:24:36 UTC

[jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status

    [ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837066#comment-13837066 ] 

Peter Halliday commented on CASSANDRA-6399:
-------------------------------------------

This actually seems to work with 2.0.2.

> debian init script removes PID despite the return status
> --------------------------------------------------------
>
>                 Key: CASSANDRA-6399
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6399
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Peter Halliday
>
> If there's an error in running service cassandra stop it can return a non-successful code, but the do_stop() removes the PID file anyway.  This shows then via service cassandra status, that Cassandra is stopped, even though it's still running in the process list.



--
This message was sent by Atlassian JIRA
(v6.1#6144)