unable to peer probe in glusterfs : Transport endpoint is not connected

cloud learner picture cloud learner · Nov 18, 2015 · Viewed 16k times · Source

We are implementing a 3-node openstack cloud using glusterfs for storage solution. 3 nodes : controller compute and network are peers in gluster. We need to add another compute node as a peer in gluster but it is showing the following error :

[root@newcompute2 ~]# gluster peer probe 192.168.10.3
peer probe: failed: Probe returned with Transport endpoint is not connected

where 192.168.10.3 is the IP of controller node. Logs are also showing the same error. Please suggest what may be the reason for this and the required solution.

Answer

maheshp1987 picture maheshp1987 · Oct 27, 2017

This indicate that their is no port open for proper communication Node1 and Node2 host.

For that you need to fire these commands on servers

1) firewall-cmd --zone=public --add-port=24007-24008/tcp --permanent

2) firewall-cmd --zone=public --add-port=24009/tcp --permanent

3) firewall-cmd --zone=public --add-service=nfs --add-service=samba --add-service=samba-client --permanent

4) firewall-cmd --zone=public --add-port=111/tcp --add-port=139/tcp --add-port=445/tcp --add-port=965/tcp --add-port=2049/tcp --add-port=38465-38469/tcp --add-port=631/tcp --add-port=111/udp --add-port=963/udp --add-port=49152-49251/tcp --permanent

5) firewall-cmd --reload

Then try again command => gluster peer probe x.y.z.n (IP)
peer probe: success.

Please check and revert if any other query.