首页 文章

cassandra.service在几秒钟后退出,nodetool给出'Connection refused'错误

提问于
浏览
1

我在digitalocean上有一个4GB的RAM ubuntu服务器我正在使用cassandra 3.9

完成设置过程后详细here

cqlsh,nodetool status都返回此消息:

nodetool:无法连接到'127.0.0.1:7199' - ConnectException:'连接被拒绝(连接被拒绝)' .

我已经阅读了几个类似的问题,他们都建议4GB最小ram大小,我有,但仍然得到相同的错误>> Nodetool status connection refused

有人建议将listen_address和rpc_address设置为cassandra.yaml中指定ip的digitalocean,也尝试过,但问题仍然存在

一些建议查看调试日志和系统日志,很多[INFO]和[DEBUG]行,但我有一些[WARN]行,它们不会终止执行,它终止于[ERROR]行

Warnings

...
WARN  [main] 2018-03-13 12:06:52,359 DatabaseDescriptor.java:563 - Small commitlog volume detected at /var/lib/cassandra/commitlog; setting commitlog_total_space_in_mb to 6158.  You can override this in cassandra.yaml
WARN  [main] 2018-03-13 12:06:52,361 DatabaseDescriptor.java:590 - Small cdc volume detected at /var/lib/cassandra/cdc_raw; setting cdc_total_space_in_mb to 3079. You can override this in cassandra.yaml
WARN  [main] 2018-03-13 12:06:52,365 DatabaseDescriptor.java:643 - Only 22.102GiB free across all data volumes. Consider adding more capacity to your cluster or removing obsolete snapshots
...

WARN  [main] 2018-03-13 12:06:52,530 StartupChecks.java:123 - jemalloc shared library could not be preloaded to speed up memory allocations
WARN  [main] 2018-03-13 12:06:52,530 StartupChecks.java:156 - JMX is not enabled to receive remote connections. Please see cassandra-env.sh for more info.
INFO  [main] 2018-03-13 12:06:52,533 SigarLibrary.java:44 - Initializing SIGAR library
WARN  [main] 2018-03-13 12:06:52,554 SigarLibrary.java:174 - Cassandra server running in degraded mode. Is swap disabled? : true,  Address space adequate? : true,  nofile limit adequate? : true, nproc limit adequate? : false

Error

...
ERROR [main] 2018-03-13 12:06:55,808 CassandraDaemon.java:747 - Exception encountered during startup
java.lang.AbstractMethodError: org.apache.cassandra.utils.JMXServerUtils$Exporter.exportObject(Ljava/rmi/Remote;ILjava/rmi/server/RMIClientSocketFactory;Ljava/rmi/ser$
        at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:150) ~[na:1.8.0_161]
        at javax.management.remote.rmi.RMIJRMPServerImpl.export(RMIJRMPServerImpl.java:135) ~[na:1.8.0_161]
        at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:405) ~[na:1.8.0_161]
        at org.apache.cassandra.utils.JMXServerUtils.createJMXServer(JMXServerUtils.java:106) ~[apache-cassandra-3.9.jar:3.9]
        at org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:145) [apache-cassandra-3.9.jar:3.9]
        at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:219) [apache-cassandra-3.9.jar:3.9]
        at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:601) [apache-cassandra-3.9.jar:3.9]
        at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:730) [apache-cassandra-3.9.jar:3.9]

不知道如何处理该错误消息

我怀疑你们很多人都遇到过这个问题,有些人解决了这个问题,请详细说明我们其他人(以及未来的人)如何对其进行排序

我正在考虑尝试更早版本的cassandra,也许这个问题特定于版本3.9而不是早期版本

1 回答

  • 2

    这是一个已知问题(CASSANDRA-14173) . 要么将Java降级到Java 8 build 152,要么升级Cassandra .

相关问题