[Gluster-users] Machine becomes its own peer

[Scott Hazelhurst]

Dear Atin, Joe

Many thanks for your responses. 

Atin correctly diagnosed the problem — the /var/lib/glusterd/peers directories on all the nodes had a duplicate entry for one of the nodes. Fixing was just a matter of stopping all the gluster daemons, deleting the incorrect entry for the node, and restarting. All is now good.

The problem occurred when I had reintroduced a brick : the machine had died, and when I brought up a new machine with the same name & IP address with the old (but good disk) in it, I  must have introduced some inconsistency on one of the machines which then propagated to the others.

Again, many thanks for the prompt response — it was very helpful in resolving the issue easily.

Regards

Scott



<table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> 
<tr>
<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>
</tr>
</table