On 09/26/2013 12:45 AM, Nux! wrote: > On 25.09.2013 18:24, Vijay Bellur wrote: >> On 09/25/2013 08:50 PM, Nux! wrote: >>> On 25.09.2013 15:42, Nux! wrote: >>>> Hello, >>>> >>>> I'm currently using 4 servers with various types of volumes on them, >>>> today I noticed 2 of them report the other 2 as "peer rejected" and >>>> viceversa. >>>> Where do I even begin to debug this? I don't see anything meaningful >>>> in the logs. >>>> Any pointers? >> >> "Peer rejected" is seen if there is a volume configuration mismatch >> between peers. Can you check if there is a mismatch in volume >> configuration between the two sets of peers? > > I have checked the volumes "info" files following Krishnan's advice and > they seem to have the same data, though oddly not exactly in the same > place, e.g. some have auth.allow above rpc.auth-allow and it's > counterpart info files from other servers have it the other way around, > but the values are identical. Aren't these files supposed to be 100% the > same? The ordering need not be the same. Can you please verify if there's a difference in the content of this file on all peers: /var/lib/glusterd/vols/<volname>/cksum Thanks, Vijay > > Other than this, the volume files on all servers have port=0 for the > bricks that are on the "rejected" peers. > > So it's hard to say which is the "right" set of servers and on which I > should execute the instructions from > http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected > > > I'm afraid not to make this even a bigger disaster. > > Suggestions? >
