Hiii,
I also faced a similar situation
The real problem was with DRBD. It was in split brain condition and it was
the reason for the ping/pingd resource's improper functioning...
Check whether your DRBD is also in split brain by using
# cat /proc/drbd
and
# drbdadm
On Wed, Apr 21, 2010 at 9:41 AM, Stefan Kelemen wrote:
> So i madde a complete hb_report (attachment) over ten minutes in that i made
> a deconnect of the ethernet without failover and a reconnect.
Could you reproduce with "debug 1" in ha.cf please?
There's not enough detail in the lrmd logs to
e-rule" pingd: defined pingd
> colocation col_apache_after_drbd inf: group_t3 ms_drbd_service:Master
> order ord_apache_after_drbd inf: ms_drbd_service:promote group_t3:start
> property $id="cib-bootstrap-options" \
> dc-version="1.0.8-2c98138c2f070fcb6ddeab1084154cffbf4
cluster-infrastructure="Heartbeat" \
no-quorum-policy="ignore" \
default-resource-stickiness="100" \
last-lrm-refresh="1271410912" \
startup-fencing="false" \
stonith-enabled="false" \
default
Datum: Thu, 15 Apr 2010 12:56:01 +0200
>> Von: "Stefan Kelemen"
>> An: The Pacemaker cluster resource manager
>> Betreff: Re: [Pacemaker] Failover after fail on Ethernet Fails
>
>> Hm.. OK i tested this there is no changes, no Failover when i cut the
>> Ethe
Am Donnerstag, 15. April 2010 14:49:10 schrieb Stefan Kelemen:
> I found the Issue.
> As location i used the key resource ms_drbd_service. Why does i cant use
> group or a Part of the group as key resource.
>
> location loc_Cluster_IP_on_pingd ms_drbd_service \
> rule $id="loc_Cluster_IP_on
t
property $id="cib-bootstrap-options" \
dc-version="1.0.8-2c98138c2f070fcb6ddeab1084154cffbf44ba75" \
cluster-infrastructure="Heartbeat" \
no-quorum-policy="ignore" \
default-resource-stickiness="100" \
las
ommunications
# udpport691
bcast eth1
# autojoin any
# Thresholds (in seconds)
keepalive 1
warntime 6
deadtime 10
initdead 15
crm on
Original-Nachricht
> Datum: Wed, 7 Apr 2010 15:35:56 +0200
> Von: Andrew Beekhof
> An: The Pacemaker cluster resource manager
> Betreff: Re: [Pacemaker] Failover after fail on Ethernet Fails
> On Wed, Apr 7, 2010 at 3:26 PM, Stefan Kelemen
> wrote:
> >
On Wed, Apr 7, 2010 at 3:26 PM, Stefan Kelemen wrote:
> Hello,
> My Two Node Cluster
> Debain 5/Pacemaker/Heartbeat aktual Madkiss and Backport Packets, Kernel
> 2.6.30
> makes Failover fine, but when i disconnect the Ethernet Connection then show
> me the other Server "hey the other Node is gon
Hello,
My Two Node Cluster
Debain 5/Pacemaker/Heartbeat aktual Madkiss and Backport Packets, Kernel 2.6.30
makes Failover fine, but when i disconnect the Ethernet Connection then show me
the other Server "hey the other Node is gone" but hes do no migration of the
Resources.
11 matches
Mail list logo
