使用OpsCenter启动AWS EC2群集时出现问题

时间:2016-01-28 23:03:52

标签: cassandra datastax

我希望在AWS上使用Datastax Enterprise集群。

我首先创建了一个带有OpsCenter的第一个节点。我使用以下Amazon EC2映像来启动此节点:

image-1439607361.manifest.xml (ami-e715a08c)

节点启动后,我进入并配置了OpsCenter基础知识。我将/etc/default/dse配置为:

EXTRA_CLASSPATH="/usr/share/java/mx4j-tools.jar"
HADOOP_ENABLED=0
CFS_REPLICATION_FACTOR=3
SOLR_ENABLED=0
SPARK_ENABLED=0
CFS_ENABLED=0

/etc/dse/cassandra/cassandra.yaml中,我使用172.11.11.11内部ip地址作为种子,监听地址,广播地址,rpc地址和广播rpc地址。

我将小报保留为com.datastax.bdp.snitch.DseSimpleSnitch

我将/etc/dse/cassandra/cassandra-env.sh指向$JAVA_HOME/jre/lib/management/jmxremote.password并修正了对它的权限。

我设置了一个JMX用户和密码。

我停止了服务datastax-agent,dse和opscenterd并重新启动它们。

nodetool status显示节点为up。

然后,我去了8888号港口的opscenter网址。

我选择了“管理现有群集”。输入种子节点。输入凭据,OpsCenter仪表板显示并挂起。回到节点上,我在/var/log/opscenter/opscenterd.log

中得到了以下内容
2016-01-28 22:28:57+0000 [cluster3]  INFO: Done loading persisted scheduled job descriptions
2016-01-28 22:28:57+0000 [cluster3]  INFO: Agent for ip 172.11.11.11 is version '5.2.4'
2016-01-28 22:28:57+0000 [cluster3] ERROR: Agent for 172.11.11.11 was unable to complete operation (http://172.11.11.11:61621/load-stomp-conf?): No cassandra connections available
2016-01-28 22:28:57+0000 [cluster3]  INFO: Automatic agent setup failed for (unknown ip): No cassandra connections available (172.11.11.11)
2016-01-28 22:28:57+0000 []  INFO: Starting to update agents' configuration
2016-01-28 22:28:57+0000 [cluster3]  INFO: OpsCenter starting up.
2016-01-28 22:28:57+0000 [] DEBUG: Persisting config file /etc/opscenter/clusters/cluster3.conf
2016-01-28 22:28:57+0000 []  INFO: Finished starting new cluster services for cluster3
2016-01-28 22:29:05+0000 [] DEBUG: Average opscenterd CPU usage: 1.61%, memory usage: 53 MB
2016-01-28 22:29:05+0000 [cluster3] DEBUG: keyspace type all are {'all': [u'system', u'system_traces', u'dse_system', u'system_auth', u'dse_auth', u'OpsCenter', u'cfs'], 'system_with_auth': [u'system', u'system_traces', u'dse_system', u'system_auth', u'dse_auth', u'dse_security']}
2016-01-28 22:29:05+0000 [] DEBUG: Keyspace collecting status for: [u'dse_perf']
2016-01-28 22:29:05+0000 [cluster3] DEBUG: [control connection] Refreshing node list and token map
2016-01-28 22:29:05+0000 [cluster3] DEBUG: [control connection] Finished fetching ring info
2016-01-28 22:29:05+0000 [cluster3] DEBUG: [control connection] Rebuilding token map due to topology changes
2016-01-28 22:29:26+0000 [cluster3] DEBUG: [control connection] Refreshing node list and token map
2016-01-28 22:29:26+0000 [] DEBUG: Error during pending deferred: [Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'address'
/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py:1141:unwindGenerator
/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py:1020:_inlineCallbacks
/usr/lib/python2.7/dist-packages/opscenterd/Cluster.py:1354:collectNodeList
/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py:1141:unwindGenerator
--- <exception caught here> ---
/usr/share/opscenter/lib/py-debian/2.7/amd64/twisted/internet/defer.py:1020:_inlineCallbacks
/usr/lib/python2.7/dist-packages/opscenterd/CassandraService.py:326:getTokenList
]
2016-01-28 22:29:26+0000 [cluster3] ERROR: There was an error while collecting the node list: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/opscenterd/Cluster.py", line 1042, in updateNodeList
AttributeError: 'NoneType' object has no attribute 'address'

我在/var/log/opscenter/repair_service/cluster3.log中获得了以下内容:

2016-01-28 22:53:56+0000 [cluster3] ERROR: The state of the following nodes could not be determined, most likely due to agents on those nodes not being properly connected: [<Node 172.11.11.11='1304142645335128783'>]

知道出了什么问题吗?

0 个答案:

没有答案
相关问题