perfsonar-user - Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Michael Petry <>
- To: Dan Doyle <>
- Cc: perfsonar-user <>
- Subject: Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors
- Date: Wed, 16 Nov 2016 11:44:56 -0500
- Ironport-phdr: 9a23:Eep4/B/sX0D3HP9uRHKM819IXTAuvvDOBiVQ1KB20ewcTK2v8tzYMVDF4r011RmSDN6dsq4P2rOempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9ZDeZwtFiCCgbb59Ixm7qRjdvdQKjIV/Lao81gHHqWZSdeRMwmNoK1OTnxLi6cq14ZVu7Sdete8/+sBZSan1cLg2QrJeDDQ9LmA6/9brugXZTQuO/XQTTGMbmQdVDgff7RH6WpDxsjbmtud4xSKXM9H6QawyVD+/9KpgVgPmhzkbOD446GHXi9J/jKRHoBK6uhdzx5fYbJyJOPZie6/Qe84RS2hcUcZLTyFOAI28YYsBAeQCIOhWsZXyqkAUoheiHwShHv/jxiNKi3LwwKY00/4hEQbD3AE4GNwOsWjbrNXvO6gMVeC+0bPGwivfb/NM2Tb29Y/Fcgg/rvGQR7JxcdHcyVQqFwzeklqcs5LqMC6I1ukUtWWQ8uRuVeWqi2E9qgFxpCCix8k2iobTnoIV0k7L+jhjwIYoI924TlR0bsWgEJROrS2aLZZ2QsU6T2F0uCY60KMJtoSmcyQQ0pQn2hjfZ+SbfIeS+RLjT/yeITFli3J/Yr2znRCy/la8yuHkS8W4zlRHojBZntXWqnwBzQHf586aQfV+5keswSiD2gHP5uxGJE00m6nWJIU9zrM1mZcfrVjPEjLzlUrqkKOZbUAp9+225+npf7nroIKXOZVuhQHkKKsun9SyAeQmPQgKWGiW4eG826fi/U39WblKj+E2nrXAvJHVO8gWqLO1DxVa0oYk7Ba/ADOm38oCkXYbK1JFfQqLj4nvO17QPPD1FemzjlWwnDppwv3GML7sDY7RInXGn7rtYapx51NZxQUv0dxQ/JdZB7QfLP/9R0P9rNnYAQU4MwywzebnEtJ91oYGVGKXHKCZLLnSsF+T6+IyJumDf5MatCzjJPc4+v7ilWU5lkMFfam1wZsXb2i1Hux4LEWDb3rsmdABEWEQsQokVeDqlUaCXiBJZ3upW6I85yo7CJ69DYvdXIytgbqB3DulEZ1MYGBJFEyMHWnye4qaRvgMdXHaHsg0vjUCHZSmWossnUWivQv2zKtjI8Lb/ioSvJbl09Mz5vCVmB0vo29aFcOYhkSMRGF9k2dAfzIqxrE39VRw1k2S+bV9ifceGNBOsaAaGjwmPILRmrQpQ+v5XRjMK5LQEA6r
Only one process running when I looked, but this was straight off the ISO behavior. That was my concern. There may be a synchronization issue hidden in the startup scripts/configs.
The cassandra log shows:
/usr/sbin/cassandra: line 155: /var/run/cassandra/cassandra.pid: No such file or directory
and there is no /var/run/cassandra
Looks like something in the setup on the ISO needs tweaking.
Mike
On Wed, Nov 16, 2016 at 11:16 AM, Dan Doyle <> wrote:
Hi Mike,Do you already have an instance of cassandra running? I have seen similar cases where you "start" cassandra on a machine where it's still running, particularly where the pidfile gets out of sync and so the init scripts think things are okay.You may want to look at something like `ps aux | grep cassandra` and kill any existing processes that may be running, that start again via the init script.On Nov 16, 2016, at 11:11 AM, Michael Petry <> wrote:cassandra leaves a fatal error in its logs. Is this expected behavior?/var/log/cassandra/cassandra.log Btw: I've tried using theINFO 11:00:15,857 Cassandra version: 2.0.17INFO 11:00:15,857 Thrift API version: 19.39.0INFO 11:00:15,861 CQL supported versions: 2.0.0,3.1.7 (default: 3.1.7)INFO 11:00:15,874 Loading persisted ring stateINFO 11:00:15,890 Starting up server gossipINFO 11:00:15,893 Enqueuing flush of Memtable-local@1959711969(375/3750 serialized/live bytes, 13 ops) INFO 11:00:15,904 Writing Memtable-local@1959711969(375/3750 serialized/live bytes, 13 ops) INFO 11:00:15,931 Completed flushing /var/lib/cassandra/data/system/local/system-local-jb- 24-Data.db (313 bytes) for commitlog position ReplayPosition(segmentId= 1479312014388, position=179710) INFO 11:00:15,932 Loading settings from file:/etc/cassandra/default.conf/cassandra.yaml ERROR 11:00:16,101 Fatal configuration errororg.apache.cassandra.exceptions. ConfigurationException: 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 at org.apache.cassandra.net.MessagingService. getServerSockets( MessagingService.java:492) at org.apache.cassandra.net.MessagingService.listen( MessagingService.java:438) at org.apache.cassandra.service.StorageService.prepareToJoin( StorageService.java:692) at org.apache.cassandra.service.StorageService.initServer( StorageService.java:622) at org.apache.cassandra.service.StorageService.initServer( StorageService.java:514) at org.apache.cassandra.service.CassandraDaemon.setup( CassandraDaemon.java:424) at org.apache.cassandra.service.CassandraDaemon.activate( CassandraDaemon.java:554) at org.apache.cassandra.service.CassandraDaemon.main( CassandraDaemon.java:643) 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 servicesFatal configuration error; unable to start server. See log for stacktrace.INFO 11:00:16,121 Announcing shutdownERROR 11:00:16,122 Exception in thread Thread[StorageServiceShutdownHook,5, main] java.lang.IllegalArgumentException: Invalid token for Murmur3Partitioner. Got true but expected a long value (unsigned 8 bytes integer). at org.apache.cassandra.dht.Murmur3Partitioner$1. fromString(Murmur3Partitioner. java:190) at org.apache.cassandra.service.StorageService.getTokensFor( StorageService.java:1470) at org.apache.cassandra.service.StorageService. handleStateNormal( StorageService.java:1532) at org.apache.cassandra.service.StorageService.onChange( StorageService.java:1354) at org.apache.cassandra.gms.Gossiper. doOnChangeNotifications( Gossiper.java:1171) at org.apache.cassandra.gms.Gossiper. addLocalApplicationStateIntern al(Gossiper.java:1401) at org.apache.cassandra.gms.Gossiper. addLocalApplicationStates( Gossiper.java:1416) at org.apache.cassandra.gms.Gossiper. addLocalApplicationState( Gossiper.java:1406) at org.apache.cassandra.gms.Gossiper.stop(Gossiper.java: 1432) at org.apache.cassandra.service.StorageService$1.runMayThrow( StorageService.java:583) at org.apache.cassandra.utils.WrappedRunnable.run( WrappedRunnable.java:28) at java.lang.Thread.run(Thread.java:745) [petry@oit-82-33 cassandra]$Mike
- [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Michael Petry, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Dan Doyle, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Michael Petry, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Andrew Lake, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Michael Petry, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Valentin Vidic, 11/17/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Michael Petry, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Andrew Lake, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Michael Petry, 11/16/2016
- Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors, Dan Doyle, 11/16/2016
Archive powered by MHonArc 2.6.19.