[
https://issues.apache.org/jira/browse/CASSANDRA-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285002#comment-13285002
]
Douglas Muth commented on CASSANDRA-4290:
-----------------------------------------
It was in fact hostname resolution, along with Ubuntu 10.10 not updating
/etc/hostname when I rebooted. Scary.
Here's a full explanation:
http://www.mail-archive.com/[email protected]/msg22706.html
-- Doug
> nodetool tries to connect to old IP address
> -------------------------------------------
>
> Key: CASSANDRA-4290
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4290
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 1.1.0
> Environment: Ubuntu 10.10 on an Amazon EC2 instance.
> Reporter: Douglas Muth
> Labels: newbie
>
> I'm running Cassandra on an EC2 instance. Prior to rebooting the machine the
> other day, nodetool worked without any issues.
> When I try to run nodetool now, it times out after about 10 seconds with an
> error like this:
> {quote}
> dmuth@devteam:~ $ nodetool --host localhost ring
> Error connection to remote JMX agent!
> java.rmi.ConnectException: Connection refused to host: *10.244.207.16*;
> nested exception is:
> java.net.ConnectException: Connection timed out
> {quote}
> Now here's the interesting thing: the IP address listed above that nodetool
> tried to connect to was the *previous* IP of our instance. Our current IP is
> entirely different:
> {quote}
> dmuth@devteam:~ $ ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 12:31:3d:14:6a:84
> inet addr:*10.84.117.110* Bcast:10.84.117.255 Mask:255.255.255.0
> {quote}
>
> I'm not using hostnames anywhere, but I did check /etc/hosts just in case,
> and didn't see anything there.
> Right now, I have a cassandra instance that I cannot manage through nodetool,
> which is a bit of a problem. Do you have any suggestions for anything else I
> can look at?
> Thanks,
> -- Doug
--
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
