Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 13 Dec 2011 12:59:30 +0000 (UTC)
From: "Zenek Kraweznik (Updated) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <52089809.5574.1323781170767.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1120247831.5507.1323779730559.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-3621) nodetool is trying to contact old
 ip address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zenek Kraweznik updated CASSANDRA-3621:
---------------------------------------

    Summary: nodetool is trying to contact old ip address  (was: nodetool is trying to contact old ip addres)
    
> nodetool is trying to contact old ip address
> --------------------------------------------
>
>                 Key: CASSANDRA-3621
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3621
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.8.8
>         Environment: java 1.6.26, linux
>            Reporter: Zenek Kraweznik
>
> My cassandra used to have adresses in 10.0.1.0/24 adresses, I moved it to 10.0.2.0/24 network (for security resons).
> I want to test new cassandra before upgrading production instances. I've made snapshot and moved it to test servers (except system/LocationInfo* files).
> Changes in configuration: ip adresses (seeds, listen address etc), cluster name. Test server are in 10.0.1.0/24 network.
> In logs I see that test nodes are seeing each other, but when i try to show ring I get this error:
> casstest1:/# nodetool -h 10.0.1.211 ring
> Error connection to remote JMX agent!
> java.rmi.ConnectIOException: Exception creating connection to: 10.1.0.201; nested exception is:
>         java.net.NoRouteToHostException: No route to host
>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:614)
>         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
>         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
>         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
>         at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
>         at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2329)
>         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:279)
>         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
>         at org.apache.cassandra.tools.NodeProbe.connect(NodeProbe.java:140)
>         at org.apache.cassandra.tools.NodeProbe.<init>(NodeProbe.java:110)
>         at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:582)
> Caused by: java.net.NoRouteToHostException: No route to host
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:529)
>         at java.net.Socket.connect(Socket.java:478)
>         at java.net.Socket.<init>(Socket.java:375)
>         at java.net.Socket.<init>(Socket.java:189)
>         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
>         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
>         ... 10 more
> casstest1:/#
> Old production adresses in 10.0.1.0/24 were: 10.0.1.201, 10.0.1.202, 10.0.1.203
> New adresses for tests: 10.0.1.211, 10.0.1.212, 10.0.1.213

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira