This bug seems relevant: https://bugzilla.redhat.com/show_bug.cgi?id=1011694but it has had its permissions changed in bugzilla. Still available on google cache. Any work arounds? Thanks! Joel On Thu, Nov 14, 2013 at 9:55 AM, Joel Young <jdy at cryregarder.com> wrote: > I am trying to add a new peer to my gluster 3.4.1 cluster. > > The peer probe reports success however when doing gluster peer status, it > report "Peer Rejected": > > [root at ir2 glusterfs]# gluster peer probe ir4 > peer probe: success > [root at ir2 glusterfs]# gluster peer status > Number of Peers: 4 > > Hostname: ir1 > Uuid: 9d9e1585-fd42-4473-ab01-8b44deb8ba6f > State: Peer in Cluster (Connected) > > Hostname: ir0 > Uuid: fbe1f8be-22ef-4b93-adef-1a9e2180d2f6 > State: Peer in Cluster (Connected) > > Hostname: ir3 > Uuid: ab641379-96ec-4e81-9123-297415793c65 > State: Peer in Cluster (Connected) > > Hostname: ir4 > Port: 24007 > Uuid: e98ba4ff-d669-4b75-9abb-0eef20b3fb4a > State: Peer Rejected (Connected) > > I've read a bunch of threads on similar reports and they don't seem > relevant. Yes, the DNS seems to be correct for forward and reverse > lookups. Yes, r4 is clean. Yes, the same thing happens from the other > nodes in the cluster. Yes, the firewall settings all appear to be correct. > > Attached is an excerpt from the probing machine (ir2) and from the full > log from the probed machine (ir4). > > Thanks in advance for any help and suggestions. > > Joel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131118/9dddd830/attachment.html>
