[ https://issues.apache.org/jira/browse/CASSANDRA-6399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837076#comment-13837076 ]
Peter Halliday commented on CASSANDRA-6399: ------------------------------------------- I followed this: http://www.datastax.com/docs/1.1/install/install_deb, the following fails. The one after that works. {noformat} automaton@ip-10-32-35-198:~/cassandra$ sudo apt-get install cassandra=2.0.1 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: cassandra 0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded. Need to get 14.1 MB of archives. After this operation, 16.1 MB of additional disk space will be used. Get:1 http://debian.datastax.com/community/ stable/main cassandra all 2.0.1 [14.1 MB] Fetched 14.1 MB in 1s (8,983 kB/s) Selecting previously unselected package cassandra. (Reading database ... 49953 files and directories currently installed.) Unpacking cassandra (from .../cassandra_2.0.1_all.deb) ... Processing triggers for ureadahead ... Setting up cassandra (2.0.1) ... Installing new version of config file /etc/cassandra/cassandra.yaml ... Installing new version of config file /etc/cassandra/cassandra-env.sh ... Installing new version of config file /etc/init.d/cassandra ... vm.max_map_count = 1048575 xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k Processing triggers for python-support ... automaton@ip-10-32-35-198:~/cassandra$ 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 * could not access pidfile for Cassandra {noformat} Then when did the same with 2.0.2, it does start correctly. {noformat} automaton@ip-10-32-35-198:~$ sudo apt-get install cassandra=2.0.2 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: cassandra 0 upgraded, 1 newly installed, 0 to remove and 93 not upgraded. Need to get 0 B/14.2 MB of archives. After this operation, 16.1 MB of additional disk space will be used. Selecting previously unselected package cassandra. (Reading database ... 49953 files and directories currently installed.) Unpacking cassandra (from .../cassandra_2.0.2_all.deb) ... Processing triggers for ureadahead ... Setting up cassandra (2.0.2) ... Installing new version of config file /etc/cassandra/cassandra.yaml ... Installing new version of config file /etc/cassandra/cassandra-env.sh ... Installing new version of config file /etc/init.d/cassandra ... vm.max_map_count = 1048575 xss = -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1862M -Xmx1862M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss256k Processing triggers for python-support ... automaton@ip-10-32-35-198:~$ 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 running {noformat} I tried updating the definition file to add 2.0.2 to the drop down box for installation, but that may not have been enough. > 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)