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: Andrew Lake <>
- Cc: Dan Doyle <>, perfsonar-user <>
- Subject: Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors
- Date: Wed, 16 Nov 2016 12:34:56 -0500
- Ironport-phdr: 9a23:A24SBhehTZHRp23wP//+QN8JlGMj4u6mDksu8pMizoh2WeGdxcW8ZR7h7PlgxGXEQZ/co6odzbGH6Oa5BSdZuc/JmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYdFRrlKAV6OPn+FJLMgMSrzeCy/IDYbxlViDanb75/KBu7oR/MusQZjoduN7o9xgbUqXZUZupawn9lK0iOlBjm/Mew+5Bj8yVUu/0/8sNLTLv3caclQ7FGFToqK2866tHluhnFVguP+2ATUn4KnRpSAgjK9w/1U5HsuSbnrOV92S2aPcrrTbAoXDmp8qlmRAP0hCoBKjU063/chNBug61HoRKhvx1/zJDSYIGJL/p1Y6fRccoHSWZdQspdUipMCZ6+YYQSFeoMJeRXr4f9qVUArhWwGBeiC//0xzBSmnP7x7c33/g9HQzE2gErAtIAsG7TrNXwLKocVuG1w7XIzTrZcfxW3Sr25pLWfRA9u/GNXa97fM3JyUYxCwPFlFWRpJf4PzOQzesCr3KX4PR9WuKykmMqrRx6rDaoxscpkIbJh4QVx0jK9CVj2ok1PcW4R1Bmbt6+DZtQsSeaOJFtTcMmXW5kojw6yqAAuZKjYScF1ponyATCa/yDb4iE+A7sVOGJLTdkhHJlYqywiAyv/kS60O38S8+03E5QoSpdiNbDqnAN2ALJ5siAUPt98V+t1iqV2ADI8eFLO0Y0mrfBK5E72LIwkIQcsVjbEiPrhkn7jrWaelk+9uS08ejrf7PrrYKfOY9skgzyLKUjltC9DOk9PAgDXHOU9fi52bDs4UH1XKlFg/gqnaXFsJ3XIMEWqrCnDwBO1Iso9gyxAC280NsCmHkKNFJFdwyDj4juI1zOJer3Dfa7g1i1jjdrxOzKMqTuA5nTMHTMi63tfbl6605bxwozyc5Q64hIBbEGJfL/Qk7xtNrGAR8lKwG43efqBMl/244bV2KCAbSWPL/XvFKH+u4jP/WDaYoJtzrhK/Uo4vvjgWEnlVAGZaWp2IEYaHG8HvRoOUWZZn/sj88ZEWgUogo+VuzrhUafUT5WfHm9Q7gw6S8mB4K7FYvDXJyigKSd3CenGZ1bfnhGBU6WEXfmbIWEXPEMZziIIsN4jzwETqauS5U62BGqtQ/60KZnLvHK9iECtJLj0sR16PPJlRE06zN0E9qR33uTQG5pg2NbDwMxiYl5rVZw1R+n2Kt1y6hRE9BCz/5SFAE3KciP4fZ9DoXXWwnBd9qNAG6rXs+3SWUpQ84r0vcTZkx2Xdiuk0aQjGKRH7YJmunTV9QP+aXG0i20fp4lxg==
over at https://issues.apache.org/jira/browse/CASSANDRA-10920
the quick fix is to add the following the cassandrea init.d file
start) # Cassandra startup echo -n "Starting Cassandra: " + pid_dir=`dirname $pid_file` + [ -d $pid_dir ] || install -m 755 -o $CASSANDRA_OWNR -d $pid_dir su $CASSANDRA_OWNR -c "$CASSANDRA_PROG -p $pid_file" > $log_file 2>&1
On Wed, Nov 16, 2016 at 11:57 AM, Andrew Lake <> wrote:
Hi,It’s a known bug in the cassandra RPM on CentOS 7. Cassandra creates /var/run/cassandra on install, but that directory is cleaned-out on reboot by the OS. Really the cassandra init script should be creating that directory, not the RPM. We don't actually control that RPM, but we might have to roll our own or tweak some boot scripts if they don’t fix that.Thanks,Andy
On November 16, 2016 at 11:45:59 AM, Michael Petry () wrote:
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.
Dan Doyle
GlobalNOC Software Developer
1-812-856-3892
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=14793 12014388, 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(M essagingService.java:492) at org.apache.cassandra.net.MessagingService.listen(MessagingSe rvice.java:438) at org.apache.cassandra.service.StorageService.prepareToJoin(St orageService.java:692) at org.apache.cassandra.service.StorageService.initServer(Stora geService.java:622) at org.apache.cassandra.service.StorageService.initServer(Stora geService.java:514) at org.apache.cassandra.service.CassandraDaemon.setup(Cassandra Daemon.java:424) at org.apache.cassandra.service.CassandraDaemon.activate(Cassan draDaemon.java:554) at org.apache.cassandra.service.CassandraDaemon.main(CassandraD aemon.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(Sto rageService.java:1470) at org.apache.cassandra.service.StorageService.handleStateNorma l(StorageService.java:1532) at org.apache.cassandra.service.StorageService.onChange(Storage Service.java:1354) at org.apache.cassandra.gms.Gossiper.doOnChangeNotifications(Go ssiper.java:1171) at org.apache.cassandra.gms.Gossiper.addLocalApplicationStateIn ternal(Gossiper.java:1401) at org.apache.cassandra.gms.Gossiper.addLocalApplicationStates( Gossiper.java:1416) at org.apache.cassandra.gms.Gossiper.addLocalApplicationState(G ossiper.java:1406) at org.apache.cassandra.gms.Gossiper.stop(Gossiper.java:1432) at org.apache.cassandra.service.StorageService$1.runMayThrow(St orageService.java:583) at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnab le.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.