perfSONAR User Q&A and Other Discussion

[eddie legbed <>]

cassandra service is started

service cassandra status

â— cassandra.service - SYSV: Starts and stops Cassandra

   Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled)

   Active: active (exited) since Fri 2017-09-22 15:55:59 UTC; 4s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 2592 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited, status=1/FAILURE)

  Process: 2703 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, status=0/SUCCESS

 /var/run/cassandra has a .pid file

-rw-r--r--  1 cassandra cassandra    4 Sep 22 14:47 cassandra.pid

I stopped/disabled perfsonar-lsregistrationdaemon.service but it seems pS is still looking for a Ls

2017/09/22 16:01:32 (3377) DEBUG> Host.pm:469 perfSONAR_PS::Utils::Host::discover_primary_address - No primary address found

2017/09/22 16:01:32 (3377) DEBUG> Host.pm:476 perfSONAR_PS::Utils::Host::discover_primary_address - No primary ipv4 address found

2017/09/22 16:01:32 (3377) DEBUG> Host.pm:483 perfSONAR_PS::Utils::Host::discover_primary_address - No primary ipv6 address found

2017/09/22 16:01:32 (3377) DEBUG> Utils.pm:119 perfSONAR_PS::Client::Utils::send_http_request - Sending HTTP GET to http://ps1.es.net:8096/lookup/activehosts.json

2017/09/22 16:01:32 (3377) ERROR> LookupService.pm:110 perfSONAR_PS::Utils::LookupService::discover_lookup_services - Problem retrieving http://ps1.es.net:8096/lookup/activehosts.json: 500 Can't connect to 198.128.151.11:8096 (Connection refused)

2017/09/22 16:01:32 (3377) ERROR> LookupService.pm:158 perfSONAR_PS::Utils::LookupService::is_host_registered - Unable to determine ls_url

2017/09/22 16:01:32 (3377) ERROR> Host.pm:297 perfSONAR_PS::NPToolkit::DataService::Host::get_details - Unable to find host record in LS using hostname XXxxXX

2017/09/22 16:01:32 (3378) DEBUG> Host.pm:436 perfSONAR_PS::NPToolkit::DataService::Host::get_services - Checking esmond

2017/09/22 16:01:33 (3378) DEBUG> Host.pm:436 perfSONAR_PS::NPToolkit::DataService::Host::get_services - Checking lsregistration

On Fri, Sep 22, 2017 at 3:33 PM, Szymon Trocha <> wrote:

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