On Mon, Feb 15, 2010 at 8:46 PM, Shahan Khan <contact@shahan.me> wrote:

I tried Brandon's suggestion, but am still getting the same error on the "remote" server.

Any other suggestions? Is it possible that its a bug?

Thanks,

Shahan

db1a = 192.168.1.13

db1b = 192.168.1.14

=================

 

db1a:~# nodeprobe -host 192.168.1.14 ring

Error connecting to remote JMX agent!

java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is: 


For some reason, db1a indicates that 192.168.1.14 resolves to 127.0.0.1...what does your /etc/hosts look like on this machine?
 

db1b:~# nodeprobe -host 192.168.1.14 info

Token(bytes[eaaca3c3bd3caba3e14ee0f85d5cda8a])

Load             : 4 KB

Generation No    : 1266260277

Uptime (seconds) : 9933

Heap Memory (MB) : 54.83 / 1016.13


 So the problem with db1b before was indeed incorrect host resolution for db1a.

-Brandon