Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors


Chronological Thread 
  • From: Dan Doyle <>
  • To: Michael Petry <>
  • Cc: perfsonar-user <>
  • Subject: Re: [perfsonar-user] perfSONAR 4.0 RC2 Cassandra logs have fatal errors
  • Date: Wed, 16 Nov 2016 11:16:24 -0500
  • Ironport-phdr: 9a23:7p12BxAD86F3W2lB4Y54UyQJP3N1i/DPJgcQr6AfoPdwSPX+o8bcNUDSrc9gkEXOFd2CrakV0KyP7+uwBCQp2tWoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7Ovr6GpLIj8Swyuu+54Dfbx9GiTe5b75+Ngi6oAreusQVgYZpN7o8xAbOrnZUYepd2HlmJUiUnxby58ew+IBs/iFNsP8/9MBOTLv3cb0gQbNXEDopPWY15Nb2tRbYVguA+mEcUmQNnRVWBQXO8Qz3UY3wsiv+sep9xTWaMMjrRr06RTiu86FmQwLzhSwZKzA27n3Yis1ojKJavh2hoQB/w5XJa42RLfZyY7/Rcc8fSWdHQ81fVTFOApmkYoQTAOUPIOZWoIvzqVUNoxuwGw6iCfjgyjNUg3/7x6063/g/HQzAwQcuH8gOsHPRrNjtOqkdS+a1x7TGwzXEb/JW3Sny45XPfx88u/6MWa9/cc3RyEkrCQzIlVqQqYjiPzyOzOsNt26b7+18Wu61im4ntht9rSayyccxk4TEgJ8exF7D9SV82ok1JNu4RVZ1YN6+CpRQrzmaOJVrTcM4XmFoviA6xacdtp6/YicG0o4nxwPZa/Cfb4iI4gjjW/iLLjhlnn5lYq+/hxCq/Ue80OL8TdK030xMriVYiNnDrGoB1xrN5cibUvdx41mt1DSV2wzP8O1IPVo4mbfdJpU8wbAwjoIevVnMEyLygkn6ka6be0U+9uS15enqba/qq56YOoNslw3zPaAjltaiDek5LgQCRXWX9OS42bH5/UD0RqhBgOcsnanDqp/aINwWpq6nDA9R1YYu8xO/AC2n0NQcgHULNVRFdwyJjoTzNFHOOvb4DfCjjFi2kTdr2urKMaP8DZXQNnTDkbHhcqhh60NE1QY+wtRS64hJBrwAIP//QFL9udLXAxMjMgG5x/7rCNBn2YMfXWKPDLWZMKTXsVKQ++0gOe2Ma5ISuDf9L/gq+eXjjXA9mV8aZqamx58XaHa/Hvt6OUmZYGfsjs0fHmgXowoyVPbqh0GaUT5Pe3ayWLox5iklB4K8A4fDXYetgLqb0yehB5FWe3tGBU6WEXrzc4WEWuwMaD6JIsN/iDAEVL6hS5M/2hG0sg/11aZnIvTO9iIGqJ3jyYs92+qGsBA59TV5C4yl3n2XXikghm4UXS4ewaV1qgpwxkrVgoZihPkNOdVVr99OQwM3fcrQxuh2DMH2VyrOetCDQVKgRd7gACx3Q94slYxdK31hEsmv20iQlxGhBKUYwvnSXMQ5

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 the 

INFO 11:00:15,857 Cassandra version: 2.0.17
 INFO 11:00:15,857 Thrift API version: 19.39.0
 INFO 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 state
 INFO 11:00:15,890 Starting up server gossip
 INFO 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 error
org.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 services
Fatal configuration error; unable to start server.  See log for stacktrace.
 INFO 11:00:16,121 Announcing shutdown
ERROR 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.addLocalApplicationStateInternal(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


Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page