CentOS: OpsCenter does not see other node’s agent

agentcassandracentosopscenter

I'm new with Apache Cassandra. I am trying to install a little sample cluster using two CentOS server. I followed the documentation (Tarball installation) and the nodes are up. However, when I go to OpsCenter, the nodes cannot see each other's agent (there is always "1 of 2 agents connected"..I tried to fix, but nothing change).

I tried both to disable and enable SSL, I tried to set the incoming_interface in opscenter.conf, I tried almost everything the network suggested to me, but the problem persisted.

Is there someone that could help me, please?

Best Answer

I don't know much about your configuration, but experienced a similar use case myself, where the opscenter only had data from the local datastax agent.

My initial setup was: 3 cassandra nodes, all 3 running opscenter and datastax-agent, with the agent configured for the local node. It seems that this was wrong, as the agents needed to be configured with (one?) opscenter address. I decided to only run the agents in all 3 nodes, but opscenter only in one of them, and configured all 3 agents to point to that node (agent/bin/setup ... this updates conf/address.yaml). This fixed my problem. I still don't know how to setup opsCenter to more than one host, but that's a different problem.

Related Solutions

DataStax OpsCenter agent fails to start when Cassandra requires authentication

Nicolas check out this documentation. With cassandra set to use internal authentication, the cassandra username and password are set in the cluster configuration file for opscenter on the opscenterd server. The file is named .conf

[cassandra] username
The thrift username to Cassandra if thrift authentication is enabled.
[cassandra] password
The thrift password to Cassandra if thrift authentication is enabled.

If that is set properly and your agents still can't connect then you might also check that the various ip addresses set in your address.yaml are correct for your installation.

Specifically, can the cassandra node reach the opscenterd server via the public internface? Verify that the local_interface ip address matches the ip for the node as seen in the nodetool status output. Verify that the opscenterd server can reach the agent on the node using the agent rpc broadcast address ip.

OpsCenter 5.1 add existing cluster

I did a fresh opscenter 5.1 install on a new aws instance and opscenter was able to connect to agents fine. However we still saw the error in the agent logs complaining about unable to connect to cassandra. This seems to be the issue with the dse version we have and looks like it got fixed with later versions

We then tried using Dse version 4.0.4 with opscenter 5.1 and were able successfully take backs ups from the opscenter. Since the backups involve communication between agents and cassandra I think the issue is not there in later dse versions.

Best Answer

Related Solutions

DataStax OpsCenter agent fails to start when Cassandra requires authentication

OpsCenter 5.1 add existing cluster

Related Topic