On 09/01/14 03:38 PM, erkin kabataş wrote:
Hi,
I am using heartbeat-2.1.2-2.i386.rpm, heartbeat-pils-2.1.2-2.i386.
rpm, heartbeat-stonith-2.1.2-2.i386.rpm packages on RHEL 5.5.
I have 3 nodes and I only use cluster IP as resource. When I start
heartbeat service on all nodes, node1 takes cluster IP. But, after about
2-3 days all 3 nodes got cluster IP, at the same time.
Also I want node priority as node1, node2, node3. Sometimes node2 has
cluster IP even heartbeat on node1 is running.
I also attached my configuration files. Am I doing something wrong in the
configurations?
I am stucked with this problem, any help would be appreciated.
Thanks!
3 things;
1. Heartbeat is long deprecated. If possible, use corosync + pacemaker.
2. You don't appear to have any fencing (aka stonith)
3. You've disabled quorum
Issues 2 and 3 are a recipe for split-brain, which is exactly what
you've experienced. At the very least, enable fencing. Strongly
recommend fencing, too.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
