Node unreachable even though the nodes are pingable

Mark Phillips mark at basho.com
Mon Feb 11 18:45:09 EST 2013


Hi Shrikar,

I suspect you've gotten to the bottom of this (as we haven't heard
from you in a few days), but upon re-reading this I noticed the
following:

>
>
The following nodes are unreachable: ['riak at 192.168.8.134',
                                      'riak at 192.168.8.135']

electic at riak-6:/var/lib/riak/leveldb$ ping 92.168.8.134
PING 92.168.8.134 (92.168.8.134) 56(84) bytes of data.
^C
--- 92.168.8.134 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
>

It looks like you're trying to ping "92.168.8.134", which is different
from the "192.168.8.134" address above.

That may not solve the issue, but it might not be a bad place to start.

Hope that helps. Let us know if you're still chasing this.

Mark




On Mon, Feb 4, 2013 at 4:20 PM, Shrikar archak <shrikar84 at gmail.com> wrote:
> Hi All,
> We have a 6 node riak cluster running on riak 1.2.1
> I am often seeing this issue where the nodes become unreachable
> when I run the riak-admin command
>
> electic at riak-6:/var/lib/riak/leveldb$ riak-admin ring-status
> Attempting to restart script through sudo -H -u riak
> ================================== Claimant
> ===================================
> Claimant:  'riak at 192.168.8.132'
> Status:     up
> Ring Ready: true
>
> ============================== Ownership Handoff
> ==============================
> No pending changes.
>
> ============================== Unreachable Nodes
> ==============================
> The following nodes are unreachable: ['riak at 192.168.8.134',
>                                       'riak at 192.168.8.135']
>
> electic at riak-6:/var/lib/riak/leveldb$ ping 92.168.8.134
> PING 92.168.8.134 (92.168.8.134) 56(84) bytes of data.
> ^C
> --- 92.168.8.134 ping statistics ---
> 1 packets transmitted, 0 received, 100% packet loss, time 0ms
>
> electic at riak-6:/var/lib/riak/leveldb$ ping 192.168.8.134
> PING 192.168.8.134 (192.168.8.134) 56(84) bytes of data.
> 64 bytes from 192.168.8.134: icmp_req=1 ttl=64 time=0.062 ms
> 64 bytes from 192.168.8.134: icmp_req=2 ttl=64 time=0.057 ms
>
> electic at riak-6:/var/lib/riak/leveldb$ ping 192.168.8.135
> PING 192.168.8.135 (192.168.8.135) 56(84) bytes of data.
> 64 bytes from 192.168.8.135: icmp_req=1 ttl=64 time=0.065 ms
> 64 bytes from 192.168.8.135: icmp_req=2 ttl=64 time=0.057 ms
>
> Has anyone faced similar problems like these?
>
> During this time the latency increases to 1 second or more than that.
>
> Please let me know if there is a way to get around this problem.
>
> Thanks,
> Shrikar
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>




More information about the riak-users mailing list