issues recovering machine in gluster

[Arif Ali <mail@xxxxxxxxxxxxxx>]

Hi all,

Hopefully, someone can help

We have a 6 node gluster setup, and have successfully got the gluster system up and running, and had no issues with the initial install.

For other reasons, we had to re-provision the nodes, and therefore we had to go through some recovery steps to get the node back into the system. The documentation I used was [1].

The key thing is that everything in the documentation worked without a problem. The replication of gluster works, and can easily monitor that through the heal commands.

Unfortunately, we are not able to run "gluster volume status", which hangs for a moment, and in the end we get "Error : Request timed out ". Most of the log files are clean, except for /var/log/glusterfs/etc-glusterfs-glusterd.vol.log. See below for some of the contents

[2016-06-13 12:57:01.054458] W [socket.c:870:__socket_keepalive] 0-socket: failed to set TCP_USER_TIMEOUT -1000 on socket 45, Invalid argument
[2016-06-13 12:57:01.054492] E [socket.c:2966:socket_connect] 0-management: Failed to set keep-alive: Invalid argument
[2016-06-13 12:57:01.059023] W [socket.c:870:__socket_keepalive] 0-socket: failed to set TCP_USER_TIMEOUT -1000 on socket 45, Invalid argument
[2016-06-13 12:57:01.059042] E [socket.c:2966:socket_connect] 0-management: Failed to set keep-alive: Invalid argument

Any assistance on this would be much appreciated.

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/sect-Replacing_Hosts.html#Replacing_a_Host_Machine_with_the_Same_Hostname

--

Arif Ali

IRC: arif-ali at freenode

LinkedIn: http://uk.linkedin.com/in/arifali

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users