Any ideas as to the cause of this error when OpsCenter starts?
Error loading cluster: No Cassandra connections available
(4 posts) (4 voices)- Started 1 year ago by TheSaint
- Latest reply from thobbs
- This topic is resolved
-
blueplastic
MemberHello Saint,
Which version of OpsCenter and Cassandra are you running?
What does the OpsCenter log show? It's located at /var/log/opscenter/opscenterd.log
Copying and Pasting the relevant parts of the log file would help us troubleshoot.
Did you use the DataStax Brisk AMI to launch the cluster or install OpsCenter yourself in a cluster?
Are all the correct ports open? OpsCenter intra-node monitoring ports are anything over 1024. So TCP ports 1024 - 65535 should be open for traffic originating from within the cluster. The OpsCenter website port is 8888, but that's not where the problem appears to be.
- Sameer
Posted 1 year ago # -
I am having the same issue after replacing a node in the cluser.
In the log I see2012-11-13 12:50:48+0000 [] Error fetching metric data:
Traceback (most recent call last):
Failure: opscenterd.CassandraService.NoCassandraConnection: No Cassandra connections available2012-11-13 12:50:48+0000 [] Error fetching metric data:
Traceback (most recent call last):
Failure: opscenterd.CassandraService.NoCassandraConnection: No Cassandra connections availablePosted 6 months ago # -
thobbs
AdministratorTamar,
That log message indicates that opscenterd (the main daemon) cannot connect to your nodes over Thrift. First, make sure OpsCenter has an update set of node IP addresses by looking at the "Edit Cluster" page of OpsCenter. Second, make sure you don't have any firewalls preventing outside access to port 9160; you can test this by attempting to connect to nodes from the machine opscenterd is running on using cassandra-cli.
(P.S. In the future, please start a new thread for new issues.)
Posted 6 months ago #
Reply
You must log in to post.