<div dir="ltr">From the log it seems like during peer handshake the N/W went down and hence the handshake was never completed.<div><br></div><div>I'd request you to try this workaround:</div><div><br></div><div>open /var/lib/glusterd/peers/<peer file> on all the nodes, update the state value to 3 and restart all the glusterd instances.</div><div><br></div><div>~Atin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 7, 2016 at 3:01 AM, Alexandre Lombard <span dir="ltr"><<a href="mailto:aldebran@gmail.com" target="_blank">aldebran@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
I want to use Gluster but I’m facing a problem. I don’t know if it is the right place to ask for this kind of questions but I did not find other places dedicated to community support of Gluster users.<br>
<br>
I’m trying to connect two peers but I’m having a lot of difficulties.<br>
<br>
I have two servers. On the first server I have a volume, and I would like to add the second server as a brick of my volume.<br>
To do so, I followed this tutorial: <a href="http://www.gluster.org/community/documentation/index.php/Gluster_3.1:_Expanding_Volumes" rel="noreferrer" target="_blank">http://www.gluster.org/community/documentation/index.php/Gluster_3.1:_Expanding_Volumes</a><br>
<br>
I ran “gluster peer probe HOSTNAME” on the first server. After a long time, the command returned with Error : Request timed out.<br>
On the first server, I ran “gluster peer status”, it gave me this:<br>
<br>
Number of Peers: 1<br>
<br>
Hostname: myhostname<br>
Uuid: uuid<br>
State: Probe Sent to Peer (Connected)<br>
<br>
On the second server, I ran the same command, it game me this:<br>
<br>
Number of Peers: 1<br>
<br>
Hostname: otherhostname<br>
Uuid: otheruuid<br>
State: Connected to Peer (Connected)<br>
<br>
When trying to use the add-brick command, I got this:<br>
<br>
volume add-brick: failed: Host myhostname is not in 'Peer in Cluster' state.<br>
<br>
Therefore I cannot add a new brick and I don’t know why.<br>
<br>
The last lines of /var/log/glusterfs/etc-glusterfs-glusterd.vol.log on my first server are :<br>
<br>
[2016-06-06 20:49:57.342545] I [MSGID: 106487] [glusterd-handler.c:1178:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req myhostname 24007<br>
[2016-06-06 20:49:57.345347] I [MSGID: 106129] [glusterd-handler.c:3600:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: myhostname (24007)<br>
[2016-06-06 20:49:57.409989] I [rpc-clnt.c:984:rpc_clnt_connection_init] 0-management: setting frame-timeout to 600<br>
[2016-06-06 20:49:57.411353] W [socket.c:869:__socket_keepalive] 0-socket: failed to set TCP_USER_TIMEOUT -1000 on socket 17, Invalid argument<br>
[2016-06-06 20:49:57.411406] E [socket.c:2965:socket_connect] 0-management: Failed to set keep-alive: Invalid argument<br>
[2016-06-06 20:49:57.411750] I [MSGID: 106498] [glusterd-handler.c:3528:glusterd_friend_add] 0-management: connect returned 0<br>
[2016-06-06 20:49:57.564970] I [MSGID: 106511] [glusterd-rpc-ops.c:256:__glusterd_probe_cbk] 0-management: Received probe resp from uuid: ae9ea7b1-1386-46c2-939c-b958a342360a, host: myhostname<br>
[2016-06-06 20:49:57.565049] I [MSGID: 106511] [glusterd-rpc-ops.c:416:__glusterd_probe_cbk] 0-glusterd: Received resp to probe req<br>
[2016-06-06 20:49:57.632835] I [MSGID: 106163] [glusterd-handshake.c:1193:__glusterd_mgmt_hndsk_versions_ack] 0-management: using the op-version 30706<br>
[2016-06-06 20:59:58.152510] E [rpc-clnt.c:201:call_bail] 0-management: bailing out frame type(Peer mgmt) op(--(2)) xid = 0x6 sent = 2016-06-06 20:49:57.565540. timeout = 600 for <a href="http://46.105.100.74:24007" rel="noreferrer" target="_blank">46.105.100.74:24007</a><br>
[2016-06-06 20:59:58.152691] I [socket.c:3382:socket_submit_reply] 0-socket.management: not connected (priv->connected = -1)<br>
[2016-06-06 20:59:58.152721] E [rpcsvc.c:1314:rpcsvc_submit_generic] 0-rpc-service: failed to submit message (XID: 0x1, Program: GlusterD svc cli, ProgVers: 2, Proc: 1) to rpc-transport (socket.management)<br>
[2016-06-06 20:59:58.152768] E [MSGID: 106430] [glusterd-utils.c:400:glusterd_submit_reply] 0-glusterd: Reply submission failed<br>
[2016-06-06 21:06:44.226143] I [MSGID: 106487] [glusterd-handler.c:1411:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req<br>
<br>
I really don’t know what is the problem.<br>
It seems to me that the first server is sending the probe to the second server, and then the second server should be sending a kind of ACK to the first one, but this ACK is never received. I don’t understand why, and I don't know where I should start looking.<br>
<br>
Thanks and regards <br>
<br>
---<br>
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/antivirus</a><br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div><br></div>