[Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks

[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 at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Brandon Mackie
Sent: April 21, 2014 12:40 PM
To: gluster-users at gluster.org
Subject: [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks

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:
http://pastie.org/9098095

I’ve heard this means the vol file doesn’t match but this is a brand new clean server and therefore no vol file.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140421/dd200e0e/attachment.html>