Gluster add node failed to report error No route to host what to do
This article mainly introduces the gluster add node failure report No route to host how to do, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.
This problem occurs in both glusterfs 3.4.7 and gluster3.6.4.
The server 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 Received CLI probe req node61 47 Received CLI probe req node61 06.818281] I [glusterd-handler.c:1031:__glusterd_handle_cli_probe] Received CLI probe req node61 24007
I [glusterd-handler.c:3198:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: node61 (24007)
[2015-08-25 02 setting frame-timeout to 47V 06.831101] I [rpc-clnt.c:969:rpc_clnt_connection_init] 0-management:
[2015-08-25 002 connect returned 47V 06.834441] I [glusterd-handler.c:3131:glusterd_friend_add] 0-management: connect returned 0
[2015-08-25 02 connection to 47 failed 06.834631] E [socket.c:2276:socket_connect_finish] 0-management: connection to 192.168.111.81 failed (No route to host)
[2015-08-25 02 size=588 max=0 total=0 47 mem-pool.c:545:mem_pool_destroy 06.834823] 0-management: size=588 max=0 total=0
[2015-08-25 02 size=124 max=0 total=0 47 mem-pool.c:545:mem_pool_destroy 06.834836] I [mem-pool.c:545:mem_pool_destroy] size=124 max=0 total=0
In fact, the root cause is the problem of authority, so the error report of gluster is outrageous.
Solution:
Turn off the firewall or open the port permissions related to gluster.
Thank you for reading this article carefully. I hope the article "what to do about gluster adding node failure report No route to host" shared by the editor will be helpful to everyone. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!
