I was seeing an obscure error message about an unconnected socket with peer 127.0.0.1.
[2013-08-16 00:36:56.765755] W
[socket.c:1494:__socket_proto_state_machine] 0-socket.management:
reading from socket failed. Error (Transport endpoint is not
connected), peer (127.0.0.1:1022)
It turns out the problem I was having was due to NAT. I was trying to create gluster servers that were behind a NAT device and use the public IP to resolve the names. This is just not going to work properly for the local machine.
What I had was something like the following on each node.
A hosts file containing
192.168.0.11 gluster1
192.168.0.12 gluster2
192.168.0.13 gluster3
192.168.0.14 gluster4
The fix was to remove the trusted peers first
sudo gluster peer detach gluster2
sudo gluster peer detach gluster3
sudo gluster peer detach gluster4
Then change the hosts file on each machine to be
# Gluster1
127.0.0.1 gluster1
192.168.0.12 gluster2
192.168.0.13 gluster3
192.168.0.14 gluster4
# Gluster2
192.168.0.11 gluster1
127.0.0.1 gluster2
192.168.0.13 gluster3
192.168.0.14 gluster4
etc
Then peer probe, and finally create the volume which was then successful.
I doubt that using IP addresses (the public ones) will work in this case. It should work if you use the private addresses behind your NAT. In my case, each server was behind a NAT in the AWS cloud.
As of late 2016, this is a known issue. It appears that a fix was attempted but it has not been released, which means it is buggy. You may have to continue to manually mount it for a while.
You can follow this bug here:
https://github.com/rancher/rancher/issues/4348
Best Answer
In case the problem is with the firewall, you should be able to open the firewall ports with the following command:
You might want to test first if disabling the firewall works, and then tune the firewall rules and services for your environment.