[Gluster-users] Setup gluster 3.1.2 ok but probe fails

Gerry Reno greno at verizon.net
Tue Jan 18 17:24:40 UTC 2011

On 01/18/2011 12:07 PM, Anand Avati wrote:
> Can you connect to port 24007 (with telnet) of the other node from
> one? It still looks like a hostname resolution issue as the log
> message says
> "[glusterd-handler.c:397:glusterd_friend_find] glusterd: Unable
> to find hostname: 10.XXX.58.95"
> and 
> "[2011-01-18 04:14:16.78380] E
> [socket.c:1661:socket_connect_finish] management: connection to
>  failed (Connection timed out)".
> It should have said "connection to SOMETHING failed". Are you using
> external or internal names to connect to each other? Try internal
> hostname (instead of IP) if you still haven't.
> Avati

>From primary to secondary:

    # telnet 10.XXX.58.95 24007
    Trying 10.XXX.58.95...
    telnet: Unable to connect to remote host: Connection timed out

This doesn't make sense though because the 2 servers are both in the
same security group which means that they should be able to connect on
internal IP or internal hostname with each other on any port.  Have you
tried 3.1.2 on ec2 yet? 

More information about the Gluster-users mailing list