Created attachment 1024542 [details] sosreport from rhs-client21 Description of problem: I am having RHEL7.1 based setup with glusterfs installed on them. The issue I face is that I get the peer probe failing Version-Release number of selected component (if applicable): glusterfs-3.7.0beta1-0.155.git72f80ae.el7.centos.x86_64 How reproducible: always Steps to Reproduce: 1. install the glusterfs build of the version as mentioned above 2. try gluster peer probe 3. Actual results: [root@rhs-client21 ~]# gluster peer probe 10.70.36.47 peer probe: failed: Probe returned with unknown errno 107 [2015-05-12 09:07:31.237797] I [glusterd-handler.c:1044:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 10.70.36.47 24007 [2015-05-12 09:07:31.536393] I [glusterd-handler.c:3316:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: 10.70.36.47 (24007) [2015-05-12 09:07:31.594583] I [rpc-clnt.c:972:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600 [2015-05-12 09:07:31.597512] W [socket.c:923:__socket_keepalive] 0-socket: failed to set TCP_USER_TIMEOUT -1000 on socket 12, Invalid argument [2015-05-12 09:07:31.597535] E [socket.c:3015:socket_connect] 0-management: Failed to set keep-alive: Invalid argument [2015-05-12 09:07:31.597728] I [glusterd-handler.c:3248:glusterd_friend_add] 0-management: connect returned 0 [2015-05-12 09:07:31.597974] E [socket.c:2332:socket_connect_finish] 0-management: connection to 10.70.36.47:24007 failed (No route to host) [2015-05-12 09:07:31.598010] I [MSGID: 106004] [glusterd-handler.c:4700:__glusterd_peer_rpc_notify] 0-management: Peer <10.70.36.47> (<00000000-0000-0000-0000-000000000000>), in state <Establishing Connection>, has disconnected from glusterd. [2015-05-12 09:07:31.598078] I [mem-pool.c:587:mem_pool_destroy] 0-management: size=588 max=0 total=0 [2015-05-12 09:07:31.598086] I [mem-pool.c:587:mem_pool_destroy] 0-management: size=124 max=0 total=0 Expected results: Peer probe should be successful Additional info:
I have just looked at the setup and in one of the node ( rhs-client23 ) had its iptables rules enabled and that seems to be the culprit. I have flushed all the iptables rules in that node and now the peer probe seems successful. Closing this bug as NOTABUG