This problem occurs with Glusterfs 3.4.7 and gluster3.6.4.
The server side executes the Add Peer command to report the following error:
Probe returned with unknown errno 107
The corresponding log error message is as follows:
[2015-08-25 02:47:06.818281] I [glusterd-handler.c:1031:__glusterd_handle_cli_probe] 0-glusterd:received CLI Probe req node61 24007
[2015-08-25 02:47:06.818633] I [Glusterd-handler.c:3198:glusterd_probe_begin] 0-glusterd:unable to find PeerInfo For Host:node61 (24007)
[2015-08-25 02:47:06.831101] I [Rpc-clnt.c:969:rpc_clnt_connection_init] 0-management:setting frame-timeout to -
[2015-08-25 02:47:06.834441] I [Glusterd-handler.c:3131:glusterd_friend_add] 0-management:connect returned 0
[2015-08-25 02:47:06.834631] E [Socket.c:2276:socket_connect_finish] 0-management:connection to 192.168.111.81:24007 failed (No route to host)
[2015-08-25 02:47:06.834823] I [Mem-pool.c:545:mem_pool_destroy] 0-management:size=588 max=0 total=0
[2015-08-25 02:47:06.834836] I [Mem-pool.c:545:mem_pool_destroy] 0-management:size=124 max=0 total=0
There are some descriptions on the web that fail to provide a solution:
http://serverfault.com/questions/690894/glusterfs-centos-7-wont-start#
http://funwithlinux.net/2013/02/glusterfs-tips-and-tricks-centos/
http://blog.csdn.net/hanphy/article/details/8901604
In fact, root cause is the authority problem, gluster error is more outrageous.
Solution:
Turn off firewall or open Gluster related port permissions.
This article is from the "Members Doukua" blog, make sure to keep this source http://dangzhiqiang.blog.51cto.com/7961271/1688180
Gluster Add node failure error: No route to host