On 07/18/2013 12:43 PM, Rahul51 S wrote: > > I am trying to "peer probe" a node, connected by a switch on the local > area network, but the command is failing with the return code 146. > > /root> gluster peer probe 172.24.132.1 > /root> echo $? > 146 > > The gluster peer status on both the nodes give different outputs. > > The below output is from the node from which the command is given > > /root> gluster peer status > Number of Peers: 1 > > Hostname: 172.24.132.1 > Port: 24007 > Uuid: 00000000-0000-0000-0000-000000000000 > State: Establishing Connection (Connected) > > And the below one is on the other node > /root> gluster peer status > Number of Peers: 1 > > Hostname: 172.24.132.0 > Port: 24007 > Uuid: 00000000-0000-0000-0000-000000000000 > State: Connected to Peer (Connected) > > After this, the state halts here and does not progresses to "Connection > Established" on both the nodes. > Could you please let me know if there is any file in the glusteFS code > where all the return codes are defined. > Could you please shed some light on where I am going wrong in this case Have you tried identifying if there's any firewall configuration on your nodes that might block access to port 24007? You can also take a look at glusterd logs to determine if exchanges are happening between the glusterd processes on your nodes. -Vijay