Are you actually trying to connect to the cluster and failing? I tried a test build and though I do get those error messages, running cqlsh works just fine for me.
Are you building on the Trusty image? if so Cassandra isn’t currently available on that image. You’d need to install it yourself. Precise has it though.
Yes we’ve always built on the trusty image. What changed?
We get the error:
ubuntu@box1165:/var/log/cassandra$ service cassandra start
ubuntu@box1165:/var/log/cassandra$ start-stop-daemon: unable to set gid to 124 (Operation not permitted)
“service cassandra start” is being generated by Circle because we list “cassandra” under machine\services.
When we stop and start cassandra (to sed replace parts of the config file) later we use sudo.
Moving to the precise image returns us to building, but Cassandra still throws errors when started by Circle (though it doesn’t keep the build from continuing since we additionally stop and restart Cassandra as noted above)
I just ran into this issue as well and it seems that the root user is not using Java 8 which is required to start Cassandra.
=> java -version
java version "1.8.0_40"
Java™ SE Runtime Environment (build 1.8.0_40-b26)
Java HotSpot™ 64-Bit Server VM (build 25.40-b25, mixed mode)
=> sudo java -version
java version "1.7.0_101"
OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-0ubuntu0.14.04.1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
I did some digging and found that the alternatives were not set up correctly. To fix it you can run
=> echo ‘3’ | sudo update-alternatives --config java
There are 3 choices for the alternative java (providing /usr/bin/java).