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?



db1a =

db1b =



db1a:~# nodeprobe -host ring

Error connecting to remote JMX agent!

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

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

db1b:~# nodeprobe -host info


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.