cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shahan Khan <cont...@shahan.me>
Subject Re: Nodeprobe Not Working Properly
Date Tue, 16 Feb 2010 17:08:12 GMT


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.1 db1b.domain.com localhost db1b
localhost.localdomain================================================================================

db1b:~$
ping db1a PING db1a (192.168.1.13) 56(84) bytes of data. 64 bytes from
db1a (192.168.1.13): icmp_seq=1 ttl=64 time=0.252 ms 64 bytes from db1a
(192.168.1.13): icmp_seq=2 ttl=64 time=0.228 ms 64 bytes from db1a
(192.168.1.13): icmp_seq=3 ttl=64 time=0.233 ms --- db1a ping statistics
--- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt
min/avg/max/mdev = 0.228/0.237/0.252/0.020 ms 

The same issue happens in
reverse, when I switch db1a and db1b. 

Other possibly useful information:


db1b:~# sudo ifconfigeth0 Link encap:Ethernet HWaddr 00:18:51:07:64:ea 
inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr:
fe80::218:51ff:fe07:64ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST
MTU:1500 Metric:1 RX packets:938664 errors:0 dropped:0 overruns:0 frame:0
TX packets:649625 errors:0 dropped:0 overruns:0 carrier:0 collisions:0
txqueuelen:0  RX bytes:429396142 (409.5 MiB) TX bytes:133120553 (126.9
MiB)eth0:0 Link encap:Ethernet HWaddr 00:18:51:07:64:ea  inet
addr:xx.xx.xxx.xx Bcast:68.71.241.31 Mask:255.255.255.224 UP BROADCAST
RUNNING MULTICAST MTU:1500 Metric:1lo Link encap:Local Loopback  inet
addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK
RUNNING MTU:16436 Metric:1 RX packets:41715 errors:0 dropped:0 overruns:0
frame:0 TX packets:41715 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0  RX bytes:5095781 (4.8 MiB) TX bytes:5095781 (4.8
MiB)

db1b:~# lsof -i
COMMAND PID USER FD TYPE DEVICE SIZE NODE
NAME
portmap 171 daemon 4u IPv4 112286666 UDP *:sunrpc 
portmap 171 daemon
5u IPv4 112286667 TCP *:sunrpc (LISTEN)
master 343 root 12u IPv4 112287239
TCP db1b.domain.com:smtp (LISTEN)
jsvc 14672 root 24u IPv6 113014281 TCP
*:53586 (LISTEN)
jsvc 14672 root 26u IPv6 113014282 TCP *:http-alt
(LISTEN)
jsvc 14672 root 27u IPv6 113014285 TCP *:39979 (LISTEN)
jsvc 14672
root 30u IPv6 113014297 TCP 192.168.1.14:afs3-fileserver (LISTEN)
jsvc
14672 root 35u IPv6 113014299 UDP 192.168.1.14:afs3-callback 
jsvc 14672
root 44u IPv6 113014301 TCP 192.168.1.14:9160 (LISTEN)

Thank you,
Shahan


On Mon, 15 Feb 2010 20:52:02 -0600, Brandon Williams  wrote:  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 

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

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   

 

Links:
------
[1]
mailto:contact@shahan.me

Mime
View raw message