On 03/22/2016 01:14 PM, Joshua J. Kugler wrote: > On Sunday, March 20, 2016 14:44:18 Atin Mukherjee wrote: >> What does gluster peer status output say? > >>From the node that failed: > > [root@vmserver-b ~]# gluster peer status > Number of Peers: 1 > > Hostname: 192.168.122.10 > Uuid: d8e1d7a0-077a-4a50-93f6-d3922e3b96b9 > State: Accepted peer request (Connected) This is the problem, peer handshaking hasn't finished yet. To get to know the reason I'd need to get the glusterd log file from 192.168.122.10. As a workaround can you do the following? 1. From node 1 open /var/lib/glusterd/peers/<uuid file>, modify state=3 2. Repeat step 1 for node 2 as well if state is different 3. restart both the glusterd instances. ~Atin > >> Also send the glusterd log of the node where the commands have failed. > > The two logs are attached. The peer status says connected. The log file says > "FAILED : Host 192.168.122.10 is not in 'Peer in Cluster' state" I'm > confused. :) > > Thanks for your help on this! > > j > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
