Mailing List Archive

On 2014-01-09T22:38:17, erkin kabataÅŸ <ekbts7@gmail.com> wrote:

> 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.

2.1.2? Seriously, upgrade. You're running code from 2007.

> 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.

The answer is probably in the logs. Probably some network failure
somewhere that causes split-brain, and because you don't have
fencing/STONITH configured, resources get activated multiple times.

Honestly, 2.1.2 is so long ago that we can't even remember all the bugs
it had ;-)


Regards,
Lars

--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________
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

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

Hi,

Thanks for the replies. Unfortunately we do not have an option to upgrade
heartbeat, at least short term. I have seen the problem (3 active
resource(service IP) at the same time) again about 2014/01/15_02:40 and
added the logs.
There are many errors in the logs like:

- Message hist queue is filling up (200 messages in queue)
- Irretrievably lost packet: node geo2.netas.com seq 485
- Cannot rexmit pkt 395 for geo2.netas.com: seqno too low

Also when I remove the following parts from cib.xml

<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair id="no_quorum_policy" name="no-quorum-policy"
value="ignore"/>
</attributes>
</cluster_property_set>
</crm_config>

Resource does not start (service IP) at any node.
Also I have added to ha.cf file these lines from an advice.

ucast eth0 IP1
ucast eth0 IP2
ucast eth0 IP3

Also I will enable stonith, but not figured out how, any advice?

Thanks and Regards,
Erkin Kabatas

ha-debug_node1
<http://linux-ha.996297.n3.nabble.com/file/n15471/ha-debug_node1>
ha-debug_node2
<http://linux-ha.996297.n3.nabble.com/file/n15471/ha-debug_node2>
ha-debug_node3
<http://linux-ha.996297.n3.nabble.com/file/n15471/ha-debug_node3>



--
View this message in context: http://linux-ha.996297.n3.nabble.com/3-active-nodes-in-3-node-configuration-tp15446p15471.html
Sent from the Linux-HA mailing list archive at Nabble.com.
_______________________________________________
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