尝试将cassandra作为服务启动时,它不会启动

尝试将cassandra作为服务启动时,它不会启动,cassandra,server,redhat,nosql,Cassandra,Server,Redhat,Nosql,我使用yum manager在RHEL6系统中安装了cassandra。还根据datastax指南配置了yaml文件。但当我尝试作为服务启动时,它会在日志文件中提供以下信息。但是cassandra服务器不会启动 INFO [STREAM-INIT-/10.76.10.82:59899] 2015-10-20 01:07:33,523 StreamResultFuture.java:116 - [Stream #da0ad600-76f0-11e5-8d1d-1f91bf0f84ef, ID#0

我使用yum manager在RHEL6系统中安装了cassandra。还根据datastax指南配置了yaml文件。但当我尝试作为服务启动时,它会在日志文件中提供以下信息。但是cassandra服务器不会启动

INFO  [STREAM-INIT-/10.76.10.82:59899] 2015-10-20 01:07:33,523 StreamResultFuture.java:116 - [Stream #da0ad600-76f0-11e5-8d1d-1f91bf0f84ef, ID#0] Received streaming plan for Bootstrap
INFO  [STREAM-INIT-/10.76.10.82:59900] 2015-10-20 01:07:33,546 StreamResultFuture.java:116 - [Stream #da0ad600-76f0-11e5-8d1d-1f91bf0f84ef, ID#0] Received streaming plan for Bootstrap
INFO  [STREAM-IN-/10.76.10.82] 2015-10-20 01:07:33,651 StreamResultFuture.java:180 - [Stream #da0ad600-76f0-11e5-8d1d-1f91bf0f84ef] Session with /10.76.10.82 is complete
INFO  [STREAM-IN-/10.76.10.82] 2015-10-20 01:07:33,652 StreamResultFuture.java:212 - [Stream #da0ad600-76f0-11e5-8d1d-1f91bf0f84ef] All sessions completed
INFO  [StorageServiceShutdownHook] 2015-10-20 01:28:50,930 ThriftServer.java:142 - Stop listening to thrift clients
INFO  [StorageServiceShutdownHook] 2015-10-20 01:28:50,978 Server.java:214 - Stop listening for CQL clients
INFO  [StorageServiceShutdownHook] 2015-10-20 01:28:50,980 Gossiper.java:1442 - Announcing shutdown
INFO  [StorageServiceShutdownHook] 2015-10-20 01:28:50,983 StorageService.java:1698 - Node /10.76.10.78 state jump to normal
INFO  [StorageServiceShutdownHook] 2015-10-20 01:28:53,014 MessagingService.java:735 - Waiting for messaging service to quiesce
INFO  [ACCEPT-/10.76.10.78] 2015-10-20 01:28:53,016 MessagingService.java:1011 - MessagingService has terminated the accept() thread

您能否将日志级别更改为DEBUG/TRACE并查看MessagingService被终止的原因?这是一个单节点安装吗?你可以分享一些信息,比如YAML配置,也可以检查它是否因为内存限制而被杀死。这是一个安装在云环境中的五节点集群。所有机器都在redhat linux 6上运行。我还检查了是否存在内存限制。您可以将日志级别更改为DEBUG/TRACE,并查看MessagingService被终止的原因吗?这是一个单节点安装吗?你可以分享一些信息,比如YAML配置,也可以检查它是否因为内存限制而被杀死。这是一个安装在云环境中的五节点集群。所有的机器都在redhat linux 6上运行。我还检查了是否有内存限制