http://www.datastax.com/support-forums/topic/opscenter-agent-jmx-connection-issue Software, Support, and Training for Apache Cassandra en-US Thu, 23 May 2013 15:03:13 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/opscenter-agent-jmx-connection-issue#post-1351 Mon, 12 Mar 2012 16:06:32 +0000 Anonymous 1351@http://www.datastax.com/support-forums/ <p>indeed that has worked for me:<br /> JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=&lt;hostname&gt;" </p> http://www.datastax.com/support-forums/topic/opscenter-agent-jmx-connection-issue#post-1345 Fri, 09 Mar 2012 10:40:04 +0000 Anonymous 1345@http://www.datastax.com/support-forums/ <p>Hi Nick</p> <p>Thanks for your help.</p> <p>The issue was to do with the way vserver manages the lo interface and 127.0.0.1 .</p> <p>I added the lo interface explicitly to the vserver and all works now.</p> <p>Dan </p> http://www.datastax.com/support-forums/topic/opscenter-agent-jmx-connection-issue#post-1326 Wed, 07 Mar 2012 16:39:07 +0000 nickmbailey 1326@http://www.datastax.com/support-forums/ <p>JMX is actually a two connection protocol. Cassandra will first bind JMX to port 7199 on all interfaces of the machine. When clients connect to this port it will then have them reconnect on a configurable hostname and random port.</p> <p>Unless you have firewall rules that are specifically blocking local traffic to 127.0.0.1 on port 7199, then I believe it is the second connection that is failing. The port for the second connection is a random port &gt; 1024, so you may also have firewall rules that are preventing this connection.</p> <p>The interface used by this second connection is controlled by the jvm argument: '-Djava.rmi.server.hostname=&lt;hostname&gt;'</p> <p>You can add this argument to your cassandra-env.sh conf file to set this interface to something that the agents can communicate with (and has appropriate firewall rules allowing all ports &gt; 1024).</p> <p>JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=&lt;hostname&gt;" </p> http://www.datastax.com/support-forums/topic/opscenter-agent-jmx-connection-issue#post-1286 Mon, 05 Mar 2012 08:51:21 +0000 Anonymous 1286@http://www.datastax.com/support-forums/ <p>I have installed 2 community instances if dsc-cassandra-1.0.7 each in their own vserver. Both cassandra's communicate to each other and are working fine. I followed one of the datastax tutorials.</p> <p>I installed the opscenter on one of the vservers and as far as I can tell it works properly.</p> <p>I then installed opscenter-agent on each. However, when I run these they both try to connect to JMX on 127.0.0.1:7199 and fail since cassandra JMX port is on the server IP and not 127.0.0.1</p> <p>Opscenter reports both nodes as down.</p> <p>I am assuming this is opscenter-agent connecting to cassandra?</p> <p>The error is</p> <p> INFO [pool-4-thread-1] 2012-03-05 08:47:39,362 New JMX connection (127.0.0.1:7199)<br /> ERROR [pool-4-thread-1] 2012-03-05 08:47:39,364 Error connecting via JMX: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:<br /> java.net.ConnectException: Connection refused]</p> <p>I have tried many things to try and force cassandra to have JMX bound to 127.0.0.1 and I have tried to force opscenter-agent to connect to the right IP.</p> <p>My address,yaml looks like this<br /> -------<br /> stomp_interface: "xxx.xxx.xx.77"<br /> local_interface: "xxx.xxx.xx.77"<br /> -------</p> <p>Anyone got any ideas with this?</p> <p>Dan </p>