[Gluster-users] Gluster 3.7.6 add new node state Peer Rejected (Connected)

[Mohammed Rafi K C]

On 02/25/2016 11:45 PM, Steve Dainard wrote:
> Hello,
>
> I upgraded from 3.6.6 to 3.7.6 a couple weeks ago. I just peered 2 new
> nodes to a 4 node cluster and gluster peer status is:
>
> # gluster peer status *<-- from node gluster01*
> Number of Peers: 5
>
> Hostname: 10.0.231.51
> Uuid: b01de59a-4428-486b-af49-cb486ab44a07
> State: Peer in Cluster (Connected)
>
> Hostname: 10.0.231.52
> Uuid: 75143760-52a3-4583-82bb-a9920b283dac
> State: Peer in Cluster (Connected)
>
> Hostname: 10.0.231.53
> Uuid: 2c0b8bb6-825a-4ddd-9958-d8b46e9a2411
> State: Peer in Cluster (Connected)
>
> Hostname: 10.0.231.54 *<-- new node gluster05*
> Uuid: 408d88d6-0448-41e8-94a3-bf9f98255d9c
> *State: Peer Rejected (Connected)*
>
> Hostname: 10.0.231.55 *<-- new node gluster06*
> Uuid: 9c155c8e-2cd1-4cfc-83af-47129b582fd3
> *State: Peer Rejected (Connected)*

Looks like your configuration files are mismatching, ie the checksum
calculation differs on this two node than the others,

Did you had any failed commit ?

Compare your /var/lib/glusterd/<volname>/info of the failed node against
good one, mostly you could see some difference.

can you paste the /var/lib/glusterd/<volname>/info ?

Regards
Rafi KC


> *
> *
> I followed the write-up
> here: http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected
> and the two new nodes peer'd properly but after a reboot of the two
> new nodes I'm seeing the same Peer Rejected (Connected) State.
>
> I've attached logs from an existing node, and the two new nodes.
>
> Thanks for any suggestions,
> Steve
>
>
>
>
> _______________________________________________
> 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/20160226/6c9318b8/attachment.html>