[
https://issues.apache.org/jira/browse/CASSANDRA-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148011#comment-13148011
]
paul cannon commented on CASSANDRA-3477:
----------------------------------------
A return value of 2 from the initscript stop routine means that jsvc failed to
stop the daemon.
(So "the stop command seems to have completed successfully" is inaccurate; a
nonzero return value is the correct way for an initscript to indicate failure.
If you want to see messages about progress/success/failure from initscripts,
you should set {{VERBOSE=yes}} in {{/etc/default/rcS}}.)
At any rate, it looks like the bit to debug is jsvc. Can you try stopping the
daemon with:
{noformat}
sudo /usr/bin/jsvc -stop -verbose -home /usr/lib/jvm/java-6-sun/jre/bin/../ \
-pidfile /var/run/cassandra.pid org.apache.cassandra.thrift.CassandraDaemon
{noformat}
..then see what exit code it gives, and see whether cassandra actually stops.
> sudo /etc/init.d/cassandra stop and restart don't work on Debian 6
> ------------------------------------------------------------------
>
> Key: CASSANDRA-3477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3477
> Project: Cassandra
> Issue Type: Bug
> Components: Packaging
> Reporter: Joaquin Casares
> Assignee: paul cannon
> Priority: Minor
> Fix For: 1.0.3
>
>
> The restart command keeps failing and never passes.
> The stop command seems to have completed successfully, but the processes is
> still listed when I run 'ps auwx | grep cass'.
> Using the Debian6 images on Rackspace. 2 nodes are definitely showing the
> same behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
