On 02/14/2014 08:32 PM, Michael Shuler wrote:
On 02/14/2014 08:27 PM, Michael Shuler wrote:
On 02/14/2014 08:10 PM, Michael Shuler wrote:
mshuler@debian:~$ sudo supervisorctl status
cassandra_server:cassandra FATAL Exited too quickly
(process log may have details)
I imagine the problems all stem from the fact that the initializing
script, in my case, /opt/cassandra/bin/cassandra, is executed and it's
done starting c* (Exited too quickly), and the process that actually
needs to be supervised is the java process (thus the ignorance that it
is running, and the fact that killing it is not recognized).
Yup.
https://lists.supervisord.org/pipermail/supervisor-users/2012-December/001207.html
(Self reply again..)
with cassandra -f, which is not being backgrounded in the exec line of
the script, my conf works:
mshuler@debian:~$ sudo supervisorctl status
cassandra_server:cassandra RUNNING pid 2784, uptime 0:00:23
mshuler@debian:~$ pkill java
mshuler@debian:~$ ps axu|grep java
mshuler 2988 0.0 0.0 7828 876 pts/0 S+ 20:45 0:00 grep java
mshuler@debian:~$ ps axu|grep java
mshuler 2989 18.1 16.4 1056412 168492 ? Sl 20:45 0:04 java
-ea -javaagent:/opt/cassandra/bin/../lib/jamm-0.2.5.jar
-XX:+UseThreadPriorities <...>
and in the supervisor log:
2014-02-14 20:42:23,067 INFO daemonizing the supervisord process
2014-02-14 20:42:23,067 INFO supervisord started with pid 2777
2014-02-14 20:42:24,072 INFO spawned: 'cassandra' with pid 2784
2014-02-14 20:42:39,302 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 15 seconds (startsecs)
2014-02-14 20:45:57,131 INFO exited: cassandra (exit status 143; not
expected)
2014-02-14 20:45:58,134 INFO spawned: 'cassandra' with pid 2989
2014-02-14 20:46:13,241 INFO success: cassandra entered RUNNING state,
process has stayed up for > than 15 seconds (startsecs)
--
Michael
