cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Halliday (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6399) debian init script removes PID despite the return status
Date Fri, 22 Nov 2013 22:46:36 GMT

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

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

Also, on debian, there's no /var/run/cassandra directory created.  So that means the PID file
doesn't get created

{noformat}
ubuntu@domU-12-31-39-02-85-9C:~$ ps aux|grep cassandra
ubuntu@domU-12-31-39-02-85-9C:~$ sudo service cassandra start
xss =  -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42
-Xms1862M -Xmx1862M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
ubuntu@domU-12-31-39-02-85-9C:~$ sudo service cassandra status
xss =  -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42
-Xms1862M -Xmx1862M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k
 * Cassandra is not running
ubuntu@domU-12-31-39-02-85-9C:~$ 
{noformat}

> 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)

Mime
View raw message