Nodetool cannot ring localhost

(3 posts) (3 voices)

• Started 8 months ago by Transcendence
• Latest reply from thobbs
• This topic is not resolved

Tags:

No tags yet.

1. 

   Transcendence
   Member

   I configured a single node cluster and tried to use nodetool but I get this exception:

   bin/nodetool ring -h localhost
   Error connection to remote JMX agent!
   java.rmi.ConnectIOException: Exception creating connection to: 10.10.155.250; nested exception is:
           java.net.NoRouteToHostException: No route to host
           at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:632)
           at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
           at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
           at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:128)
           at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
           at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2370)
           at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:296)
           at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
           at org.apache.cassandra.tools.NodeProbe.connect(NodeProbe.java:141)
           at org.apache.cassandra.tools.NodeProbe.<init>(NodeProbe.java:111)
           at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:623)
   Caused by: java.net.NoRouteToHostException: No route to host
           at java.net.PlainSocketImpl.socketConnect(Native Method)
           at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:337)
           at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:198)
           at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)
           at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
           at java.net.Socket.connect(Socket.java:579)
           at java.net.Socket.connect(Socket.java:528)
           at java.net.Socket.<init>(Socket.java:425)
           at java.net.Socket.<init>(Socket.java:208)
           at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
           at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:146)
           at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
           ... 10 more

   Posted 8 months ago #
2. 

   song
   Member

   This usually means that the host is not started. Sometimes if your environment doesn't allow the root user or cassandra service account start the service, the instance is not started. Try starting it manually in the bin or grep the process to find it running to make sure and then run the nodetool perhaps? I am just asking.

   Posted 8 months ago #
3. 

   thobbs
   Administrator

   With the JMX protocol (which nodetool uses), after the client initially connects, the server asks it to reconnect on a randomly chosen port at a particular address. In your case, the address is 10.10.155.250 rather than localhost, and I'm guess your firewalls aren't open to incoming traffic on all ports >= 1024.

   One solution is to edit cassandra-env.sh and set this line close to the bottom:

   JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=127.0.0.1"

   However, you won't be able to use nodetool against that node from a remote host. Your other option if you don't want to open your firewall is something like this: http://simplygenius.com/2010/08/jconsole-via-socks-ssh-tunnel.html

   Posted 8 months ago #

RSS feed for this topic

Reply

You must log in to post.