Clean install, but no processes

[LeeFox]

I've installed the ANXS.cassandra playbook along with dependencies and run it against several stock ubuntu VM's on AWS. I get the same result each time.

The playbook runs cleanly with no errors (22 OK tasks, 16 changed), but there is no cassandra process to be found running. I do see the following at the end of of /var/log/cassandra:
===
INFO [StorageServiceShutdownHook] 2014-10-16 15:47:57,311 ThriftServer.java:142 - Stop listening to thrift clients
INFO [StorageServiceShutdownHook] 2014-10-16 15:47:57,334 Server.java:192 - Stop listening for CQL clients
INFO [StorageServiceShutdownHook] 2014-10-16 15:47:57,334 Gossiper.java:1279 - Announcing shutdown
INFO [StorageServiceShutdownHook] 2014-10-16 15:47:59,335 MessagingService.java:705 - Waiting for messaging service to quiesce
INFO [ACCEPT-localhost/127.0.0.1] 2014-10-16 15:47:59,335 MessagingService.java:951 - MessagingService has terminated the accept() thread
===
So, it seems like cassandra starts, but then shuts down. I don't see any exceptions or errors in the log otherwise.

Manually starting cassandra results in this message displayed to console:

===
Error opening zip file or JAR manifest missing : /usr/share/cassandra/lib/jamm-0.2.5.jar
Error occurred during initialization of VM
agent library failed to init: instrument
===
The only change I've made to the playbook was editing defaults/main.yml to change the name of the cluster from "Test Cluster" to my cluster name.

I'm invoking the ANXS.cassandra playbook with this:

---

• hosts: nogroup
  sudo: yes
  roles:
  • ANXS.cassandra

So, everything seems simple enough, but I can't get a cassandra instance running.

[lcacciagioni]

Guys it seems that cassandra looks for jamm-0.2.5.jar, but jamm-0.2.6.jar is installed. I have used a fast fix (This is not how ideally I want to fix this kind of things).

root@cassandra-test-node-1:~# ln -s /usr/share/cassandra/lib/jamm-0.2.6.jar /usr/share/cassandra/lib/jamm-0.2.5.jar

Maybe this will help you guys to fix this.BTW, I have done this in a playbook to replicate this behaviour in all nodes.-

[charlesa101]

I think the jamm version should be made a var, hardcoded to jamm-0.2.5 in the template
but the value keeps changing with new cassandra update release!

Line 170 -- fixed it for me
https://github.com/ANXS/cassandra/blob/99d7c4414a3064653d3015aafd7d51638bdfe7e6/templates/cassandra-env.sh.j2