[
https://issues.apache.org/jira/browse/CASSANDRA-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148034#comment-13148034
]
Joaquin Casares commented on CASSANDRA-3477:
--------------------------------------------
This is what I see when I run a restart. I was asking if we could have
something similar for this stop command? Fairy sprinkles if you will, but if
the code is already going to be touched, why not?
{CODE}
root@jcasares-Ubuntu-11:~# sudo /etc/init.d/cassandra restart
* Restarting Cassandra cassandra
...fail!
{CODE}
In /var/log/cassandra.bak/output.log:
{CODE}
INFO 12:07:31,271 Listening for thrift clients...
INFO 12:07:32,525 Cassandra shutting down...
INFO 12:07:32,526 Stop listening to thrift clients
Shutdown or reload already scheduled
Shutdown or reload already scheduled
Shutdown or reload already scheduled
...
{CODE}
> 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
