[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-ha
Subject:    Re: [Linux-HA] Cloned resources starting on forbidden nodes
From:       Max Hofer <max.hofer () apus ! co ! at>
Date:       2006-10-30 12:42:30
Message-ID: 200610301342.31094.max.hofer () apus ! co ! at
[Download RAW message or body]

"No", it is the Debian package form Ultramonkey side with 2 patches provided 
from the project side (resource agent "pingd" patch, and a patch which prevents
ping nodes to show up as cluster nodes).

But as i already explained it was a mistake in the cib.xml. I used #id unstead of 
#uname. I tested it out and it works fine now.

kind regards,
Max

On Monday 30 October 2006 10:41, Andrew Beekhof wrote:
> Is this a vanilla 2.0.7 build?
> 
> On 10/30/06, Max Hofer <max.hofer@apus.co.at> wrote:
> > I have a cluster with 4 nodes: management1, management2, routing1, routing2.
> > 
> > I created a cloned resource called "isdn_cards" (the primitive is "isdn_card")
> > which should only run on "management[12]" and never on routing[12].
> > 
> > The constraint in the cib.xml looks like:
> > 
> > <rsc_location id="isdn_location" rsc="isdn_cards">
> > <!-- make sure they run only on management servers -->
> > <rule id="isdn_not_on_routing_servers" score="-INFINITY" boolean_op="or">
> > <expression attribute="#id" operation="eq" value="routing1"/>
> > <expression attribute="#id" operation="eq" value="routing2"/>
> > </rule>
> > <rule id="isdn_on_mgmt_servers" score="INFINITY" boolean_op="or">
> > <expression attribute="#id" operation="eq" value="management1"/>
> > <expression attribute="#id" operation="eq" value="management2"/>
> > </rule>
> > </rsc_location>
> > 
> > At the first it seemed to work pretty fine until i shut down all 4 nodes
> > simultaneously and i restarted them at the same time.
> > 
> > Then the PE moves "isdn_card:1" to routing1 and i have no clue why.
> > 
> > Excerpt from the ha-log:
> > 
> > pengine[21020]: 2006/10/28_10:27:38 notice: NoRoleChange:native.c Leave  resource \
> > pingd-child:3  (routing1) pengine[21020]: 2006/10/28_10:27:38 notice: \
> > NoRoleChange:native.c Move  resource isdn_card:0    (management1 -> routing1) \
> > pengine[21020]: 2006/10/28_10:27:38 notice: Recurring:native.c routing1     \
> > isdn_card:0_monitor_10000 pengine[21020]: 2006/10/28_10:27:38 notice: \
> > NoRoleChange:native.c Leave resource isdn_card:1    (management2) pengine[21020]: \
> > 2006/10/28_10:27:38 notice: NoRoleChange:native.c Leave resource clusterIp_1    \
> > (routing1) 
> > The RA for the ISDN cards (pt-isdn) is "buggy" in the sense that stop does not
> > work on a node where the software for the ISDN card is not installed and thus
> > the resource remains in failed state (will be fixed soon - i just never thought a
> > start/stop would occur on routingX because of my constraints) ---
> > appart from that --- Why is the pengine moving the isdn_card:0 to routing1?
> > 
> > Sadly I never was able to figure out how ptest works *manual needed by someone
> > who knows how to work with it*
> > 
> > Attched the cib.xml and the ha-log
> > --
> > Max Hofer
> > APUS Software G.m.b.H.
> > A-8074 Raaba, Bahnhofstraße 1/1
> > T| +43 316 401629 11
> > F| +43 316 401629 9
> > W| www.apus.co.at
> > E| max.hofer@apus.co.at
> > 
> > 
> > _______________________________________________
> > 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
> > 
> > 
> > 
> _______________________________________________
> 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
> 

-- 
Max Hofer
APUS Software G.m.b.H.
A-8074 Raaba, Bahnhofstraße 1/1
T| +43 316 401629 11
F| +43 316 401629 9
W| www.apus.co.at
E| max.hofer@apus.co.at
_______________________________________________
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


[prev in list] [next in list] [prev in thread] [next in thread]