Re: Nodeprobe Not Working Properly

2010-02-16 Thread Brandon Williams
On Tue, Feb 16, 2010 at 11:08 AM, Shahan Khan wrote: > I can ping to the other server using db1a instead of the host name. > > By 'host name' I assume you mean IP address. > 192.168.1.13db1a > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff

Re: Nodeprobe Not Working Properly

2010-02-16 Thread Shahan Khan
I can ping to the other server using db1a instead of the host name.192.168.1.13 db1a::1 localhost ip6-localhost ip6-loopbackfe00::0 ip6-localnetff00::0 ip6-mcastprefixff02::1 ip6-allnodesff02::2 ip6-allroutersff02::3 ip6-allhosts# Auto-generated hostname. Please do not remove this comment.127.0.0

Re: Nodeprobe Not Working Properly

2010-02-15 Thread Brandon Williams
On Mon, Feb 15, 2010 at 8:46 PM, Shahan Khan 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 > > =

Re: Nodeprobe Not Working Properly

2010-02-15 Thread Shahan Khan
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 re

Re: Nodeprobe Not Working Properly

2010-02-15 Thread Brandon Williams
On Mon, Feb 15, 2010 at 1:13 PM, Shahan Khan wrote: > db1b:~# nodeprobe -host db1a ring > > Error connecting to remote JMX agent! > > java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested > exception is: > This seems to indicate that db1a resolves as 127.0.0.1 on db1b, when it