Hi Alex
Thank you. However, I tried this and it did not work; the resource
thrashes between monitor & start on the same node in perpetuity.
Which version do you use?
crmadmin -version
I am guessing this has to do with the score assigned the respective
nodes. I am not assigning a default score, just setting a preferred
node. My cib.xml is more or less converted straight from an haresources
file using the haresources2cib.py script:
<constraints>
<rsc_location id="rsc_location_group_1" rsc="group_1">
<rule id="prefered_location_group_1" score="100">
<expression attribute="#uname"
id="prefered_location_group_1_expr" operation="eq" value="ipc-1"/>
</rule>
</rsc_location>
</constraints>
That should leave the other node with a score of 0, which should be good
enough to run the resource.
However, it that resource is part of a group (as I suppose from your rsc
id), depending on your version, you might hit a bug there.
If you're just starting out with heartbeat and pacemaker, why not go
ahead and install 1.0?
Read http://clusterlabs.org/mw/Install - that should get you started.
I am not sure what default score that assigns the secondary node, nor
how to check it.
ptest -Ls (maybe LVs) should display some values for you.
You can also use my script showscores.sh that may display it a little
more clearly.
It never hurts to attach your entire config, maybe something else is
causing this.
cibadmin -Ql > my.xml
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
