<div>Joe - Scott had sent me a private email and I provided the work around, for some (unknown) reason all the nodes ended up having two uuids for a particular peer which caused it. I've asked for the log files to further debug.</div><div><br><div class="gmail_quote"><div>On Fri, 17 Feb 2017 at 21:58, Joe Julian <<a href="mailto:joe@julianfamily.org">joe@julianfamily.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="gmail_msg">Does your repaired server have the correct uuid /var/lib/glusterd/<a href="http://glusterd.info" class="gmail_msg" target="_blank">glusterd.info</a>?<br class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"></div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg">On February 16, 2017 9:49:56 PM PST, Scott Hazelhurst <<a href="mailto:Scott.Hazelhurst@wits.ac.za" class="gmail_msg" target="_blank">Scott.Hazelhurst@wits.ac.za</a>> wrote:</div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><pre class="m_6417423859401864534k9mail gmail_msg"><br class="gmail_msg">Dear all<br class="gmail_msg"><br class="gmail_msg">Last week I posted a query about a problem I had with a machine that had failed but the underlying hard disk with the gluster brick was good. I’ve made some progress in restoring. I now have the problem with my new restored machine where it becomes its own peer, which then breaks everything.<br class="gmail_msg"><br class="gmail_msg">1. Gluster daemons are off on all peers, content of /var/lib/glusterd/peers looks good.<br class="gmail_msg">2. I start the gluster daemons on all peers. All looks good.<br class="gmail_msg">3. For about 2 minutes, there’s no obvious problem — if I do a gluster peer status on any machine it looks good, if I do a gluster volume status A01 on any machine it looks good.<br class="gmail_msg">4. Then at some point, the /var/lib/glusterd/peers file of the new, restored machine gets an entry for itself and things start breaking. A typical error message is the understandable <br class="gmail_msg"><br class="gmail_msg">: Unable to get lock for uuid: 4fb930f7-554e-462a-9204-4592591feeb8, lock held by: 4fb930f7-554e-462a-9204-4592591feeb8 <br class="gmail_msg"><br class="gmail_msg">5. This is repeatable — if I stop daemons, remove the offending entry in /var/lib/glusterd/peer, and restart, the same behavior occurs — all good for a minute or two and then something magically puts something in /var/lib/glusterd/peers<br class="gmail_msg"><br class="gmail_msg">In a previous step in restoring my machine, I had a different error of mismatching cksums and what I did then may be the cause of the problem. In searching the list archives I found someone with a similar cksum problem, and the proposed solution was to copy the /var/lib/glusterd/vols/ from another of the peers to the new machine. This may not be the issue but this is the only thing I think I did that was unconventional.<br class="gmail_msg"><br class="gmail_msg">I am running version 3.7.5-19 on Scientific Linux 6.8<br class="gmail_msg"><br class="gmail_msg">If anyone can suggest a way forward I would be grateful<br class="gmail_msg"><br class="gmail_msg">Many thanks<br class="gmail_msg"><br class="gmail_msg">Scott<br class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <br class="gmail_msg"><tr><br class="gmail_msg"><td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td><br class="gmail_msg"></tr><br class="gmail_msg"></table<br class="gmail_msg"><hr class="gmail_msg"><br class="gmail_msg"></pre></blockquote></div></div><div class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><pre class="m_6417423859401864534k9mail gmail_msg">Gluster-users mailing list<br class="gmail_msg"><a href="mailto:Gluster-users@gluster.org" class="gmail_msg" target="_blank">Gluster-users@gluster.org</a><br class="gmail_msg"><a href="http://lists.gluster.org/mailman/listinfo/gluster-users" class="gmail_msg" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a></pre></blockquote></div></div><div class="gmail_msg"><br class="gmail_msg">
-- <br class="gmail_msg">
Sent from my Android device with K-9 Mail. Please excuse my brevity.</div>_______________________________________________<br class="gmail_msg">
Gluster-users mailing list<br class="gmail_msg">
<a href="mailto:Gluster-users@gluster.org" class="gmail_msg" target="_blank">Gluster-users@gluster.org</a><br class="gmail_msg">
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">- Atin (atinm)</div>