perfSONAR User Q&A and Other Discussion

[Szymon Trocha <>]

W dniu 20.09.2017 o 17:31, eddie legbed pisze:

Hi Szymon,

thanks for that. So I got round that and did a yum update to receive 4.0.1. On restart, the web GUI shows "Error loading test listing: Internal Server Error

esmond log says the following error

[ERROR] /usr/lib/esmond/esmond/api/perfsonar/api_v2.py: Unable to connect to cassandra. Please verify cassandra is running.

cassandra log shows as follows

190  localhost/127.0.0.1:7000 is in use by another process.  Change listen_address:storage_port in cassandra.yaml to values that do not conflict with other services

   191  Fatal configuration error; unable to start server.  See log for stacktrace.

   192   INFO 15:19:59,498 Announcing shutdown

   193  ERROR 15:19:59,499 Exception in thread Thread[StorageServiceShutdownHook,5,main]

   194  java.lang.IllegalArgumentException: Invalid token for Murmur3Partitioner. Got true but expected a long value (unsigned 8 bytes integer).

   195          at org.apache.cassandra.dht.Murmur3Partitioner$1.fromString(Murmur3Partitioner.java:190)

Any help in resolving this would be highly appreciated.

Does it help if you verify there are no cassandra processes, and start again?
service cassandra start

What is the result of

sudo service cassandra status 

If you look to /var/run/cassandra, does it exist with content?

-- 
Szymon Trocha

Poznań Supercomputing & Networking Center
Tel. +48 618582022 ::: http://noc.pcss.pl