Duplicate nodes in HA cluster, no quorum
This document (3215608) is provided subject to the disclaimer at the end of this document.
You will also see the duplicate nodes in hb_gui. In addition, the ha.cf file must be the same on all nodes, with the exception of the bcast parameter. If the node list is different, this will lead to even more extra nodes. If you have nodes han1 and han1.example.foo.com, then heartbeat will start one of the nodes, but the other will never start. This leads to a no quorum in the cluster. By default, you can only add resources to the cluster if you have quorum (two or more running nodes for example). So, this duplicate node condition prevents you from adding resources to the cluster.
On ALL nodes
1. Stop heartbeat (rcheartbeat stop)
2. Delete the host cache (rm /var/lib/heartbeat/hostcache)
3. Delete the deleted host cache (rm /var/lib/heartbeat/delhostcache)
On ONE node:
1. Change /etc/ha.d/ha.cf to reference each node only once, without a fully qualified domain name; and do not use autojoin any. Make sure you include all nodes, including the current node on which you are editing the ha.cf file. For example,
2. Run /usr/lib/heartbeat/ha_propagate or /usr/lib64/heartbeat/ha_propagate
On ALL nodes:
1. Restart heartbeat (rcheartbeat start)
2. Check for duplicate nodes (cl_status listnodes)
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3215608
- Creation Date: 29-Aug-2006
- Modified Date:23-Feb-2021
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com