[Linux-cluster] RHEL 3: no quorum for 3rd node

Karl Podesta kpodesta at redbrick.dcu.ie
Mon May 19 11:25:39 UTC 2008

On Thu, May 15, 2008 at 05:06:16PM -0400, Lon Hohberger wrote:
> > cluquorumd[8049]: <warning> Dropping connect from (node3-IP): Unauthorized
> > 
> > Seems like the other two nodes are rejecting the third's advances
> > towards joining quorum. Is there anything I can do about this? 
> > Would appreciate any pointers, I couldn't find an answer in the archives
> > (I notice the question was asked before too). The three nodes are listed
> > as "Active" in clustat on all nodes, but the third obviously just can't
> > join the quorum, despite reboot of the third node. 
> The md5sum of /etc/cluster.xml is the same for all nodes, right?
> -- Lon

Indeed the sums/files are the same for all nodes... 

However it turns out the issue was resolved by rebooting the existing
two production nodes! I'm not sure if just restarting clumanager/cluquorumd
on the existing nodes would have made the difference, but when I wasn't
having any luck getting the third node into the quorum, we scheduled a 
reboot of the existing two nodes, then when all 3 nodes came back up they
had all joined quorum successfully, and services could be listed/migrated
on all of the nodes. Fixed. 

I know there are probably few people using RHEL 3 cluster anymore, but 
I found this useful to know; that I need to schedule downtime in future
if requested to add a 3rd node to a live 2-node cluster...

Thanks a lot for the help as per usual, the list is excellent reading!


Karl Podesta
Systems Engineer, Securelinx Ltd., Ireland

More information about the Linux-cluster mailing list