Cassandra opscenter 5.0.1代理连接失败

opscenter代理无法连接到opscenter

opscenter的agent.log显示如下错误。（将IP替换为XX）

代理配置。

$cat-datastax-agent-5.0.1/conf/address.yaml

stomp_interface: <X.X.X.X>
use_ssl: 0

看起来还可以

但是opscenter代理告诉我一个错误。。一次又一次

 INFO [StompConnection receiver] 2014-11-28 12:05:46,826 Reconnecting in 60s.
ERROR [StompConnection receiver] 2014-11-28 12:06:46,830 failed connecting to <X.X.X.X>:61620:java.net.UnknownHostException: <X.X.X.X>

INFO[StompConnection receiver]2014-11-28 12:05:46826 60秒内重新连接。
错误[StompConnection receiver]2014-11-28 12:06:46830无法连接到：61620:java.net.UnknownHostException:

是加法

我正在CentOS 6.5版（最终版）上运行cassandra 2.1.2（3副本） 和内核：2.6.32-431.23.3.el6.x86_64

---

有人能帮我吗？

所以我在OpsCenter诊断输出中有一条稍微不同的消息： 调用CreateClusterConfController时处理错误：无法连接到群集

但是，我也在运行Cassandra 2.1.2和OpsCenter 5.0.1，在Cassandra.yaml中看到这一点之前，我无法连接到现有集群

listen_address
# You _must_ change this if you want multiple nodes to be able to communicate!
# Leaving it blank leaves it up to InetAddress.getLocalHost(). This
# will always do the Right Thing _if_ the node is properly configured
# (hostname, name resolution, etc), and the Right Thing is to use the
# address associated with the hostname (it might not be).

这似乎包括OpsCenter。所以我把它注释掉了。我还注释掉了rpc_地址，并让它自动配置自己

---

请验证这些设置，重新启动cassandra，然后尝试通过OpsCenter再次连接。

当操作系统无法将主机名解析为给定IP时，通常会引发UnknownHostException。address.yaml中的表单应为

stomp\u接口：1.2.3.4

。如果已在配置中包含

，则应删除它们并重新启动代理。

$netstat -an | grep 61620
tcp        0      0 0.0.0.0:61620               0.0.0.0:*                   LISTEN

$ telnet X.X.X.X 61620
Trying X.X.X.X...
Connected to X.X.X.X.
Escape character is '^]'.

 INFO [StompConnection receiver] 2014-11-28 12:05:46,826 Reconnecting in 60s.
ERROR [StompConnection receiver] 2014-11-28 12:06:46,830 failed connecting to <X.X.X.X>:61620:java.net.UnknownHostException: <X.X.X.X>

listen_address
# You _must_ change this if you want multiple nodes to be able to communicate!
# Leaving it blank leaves it up to InetAddress.getLocalHost(). This
# will always do the Right Thing _if_ the node is properly configured
# (hostname, name resolution, etc), and the Right Thing is to use the
# address associated with the hostname (it might not be).