[Gluster-users] issues recovering machine in gluster

[Arif Ali]

Hi Atin,

I have sent the tar file of logs in a PM

The version of gluster, that we have been using is

# rpm -qa | grep gluster
glusterfs-api-3.7.11-1.el7.x86_64
glusterfs-geo-replication-3.7.11-1.el7.x86_64
glusterfs-libs-3.7.11-1.el7.x86_64
glusterfs-client-xlators-3.7.11-1.el7.x86_64
glusterfs-fuse-3.7.11-1.el7.x86_64
glusterfs-server-3.7.11-1.el7.x86_64
glusterfs-3.7.11-1.el7.x86_64
glusterfs-cli-3.7.11-1.el7.x86_64

--
Arif Ali

IRC: arif-ali at freenode
LinkedIn: http://uk.linkedin.com/in/arifali

On 13 June 2016 at 15:46, Atin Mukherjee <amukherj at redhat.com> wrote:

> Please send us the glusterd log file along with cmd_history.log from all
> the 6 nodes. The logs you mentioned in the thread are not relevant to
> debug the issue. Which gluster version are you using?
>
> ~Atin
>
> On 06/13/2016 06:49 PM, Arif Ali wrote:
> > 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 at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-users
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160613/cbee8790/attachment.html>