Quantcast
Channel: DataStax Support Forums » Recent Topics
Viewing all articles
Browse latest Browse all 387

smandava on "ops-center agent is not able to communicate with opscenterd"

$
0
0

ops-center agent and opscenterd processes are running.
I am running my cassandra cluster on EC2 and this is a fresh install.
my address.yaml file:
-----------------------------
stomp_interface: "10.50.215.87"
use_ssl: 0
agent_rpc_interface: ip-10-191-54-230.ec2.internal
local_interface: ec2-50-16-32-26.compute-1.amazonaws.com
local_address: ec2-50-16-32-26.compute-1.amazonaws.com
agent_rpc_broadcast_address: ec2-50-16-32-26.compute-1.amazonaws.com

opscenter logs :
---------------------
2013-07-25 00:05:37+0000 [] WARN: Unable to find a matching cluster for node with IP ec2-50-16-32-26.compute-1.amazonaws.com; the message was {u'down-nodes': [], u'os-load': 0.23999999999999999}. This usually indicates that an OpsCenter agent is still running on an old node that was decommissioned or is part of a cluster that OpsCenter is no longer monitoring.
2013-07-25 00:05:37+0000 [] WARN: Unable to find a matching cluster for node with IP ec2-50-16-32-26.compute-1.amazonaws.com; the message was {u'agent_rpc_broadcast_address': u'ec2-50-16-32-26.compute-1.amazonaws.com', u'arch': u'amd64', u'hostname': u'ip-10-191-54-230', u'sub_os': u'.', u'os_version': u'1', u'ec2': {u'instance-type': u'm1.xlarge', u'placement': u'us-east-1a', u'ami-id': u'ami-812958e8', u'instance-id': u'i-e1cca583'}, u'memory': 15015, u'os': u'linux', u'procs': 4}. This usually indicates that an OpsCenter agent is still running on an old node that was decommissioned or is part of a cluster that OpsCenter is no longer monitoring.


Viewing all articles
Browse latest Browse all 387

Trending Articles