|
A conversation with myself, but JoeJulian was kind enough to point out that it was the info file and not the vol file that wasn’t matched. Confirmed that new servers have two extra lines: op-version=2 client-op-version=2 Which of course would cause a mismatch. I’ll take down everything tonight and see if that corrects it as it does correct it on some test servers. From: gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx]
On Behalf Of Brandon Mackie Replace “bricks” with “servers” as IRC just informed me my vocab was crossed. Anyway, I wanted to add that following
http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected I can get one brick to see it as not rejected (the brick that I peer on step 4 but the rest still see it as rejected. From:
gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx]
On Behalf Of Brandon Mackie Good afternoon folks, Not sure if this is an occurrence of
https://bugzilla.redhat.com/show_bug.cgi?id=1072720 but cannot add new bricks to my existing cluster running under Ubuntu 12. New bricks are completely blank. Peer probed new from a trusted member. Both sides say “Peer Rejected (Connected)” but does not migrate the peer to the other bricks. If I then clear out the newly created /var/lib/glusterd on the new brick and then restart the server then
it migrates to all bricks but all say rejected (connected) instead of just one. Confirmed not firewall as I can open a tcp port in both directions. A quick snap of the log on the new brick: I’ve heard this means the vol file doesn’t match but this is a brand new clean server and therefore no vol file. |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
