Yes I used the gui which configured the constraints automatically.I have tried again without the constraints but still no joy.As Andrew advised i will secure a more recent build and try again.
Thanks a lot. Peter Idah > > But for some reason the resources do not fail over when I switch off a > node. > I used crm_verify -L -V to check the config and I have no errors. > However an attempt to simulate a failure returns with a warning in the > logs > - > > WARN: native_color: Resource Fs cannot run anywhere > pengine[5868]: 2009/01/27_12:17:06 WARN: native_color: Resource JVIP > cannot > run anywhere When you shutdown 001, the resources have nowhere left to run due to your configuration: <rsc_location id="cli-standby-ISGROUP" rsc="ISGROUP"> <rule id="prefered_cli-standby-ISGROUP" score="-INFINITY"> <expression attribute="#uname" id="6200ffd0-126c-4fa5-993f-a24627ce15a8" operation="eq" value="cll-jcaps-002"/> </rule> </rsc_location> This forbids ISGROUP to run on 002. And that's the only node left. Judging by the id "cli-standby-ISGROUP", you propably used crm_resource -M or the gui before to migrate ISGROUP. Both will have told you that they were going to create this constraint and that - if you ever wanted the resource on that particular node ever again - you'd have to revert the migration by crm_resource -U or some function in the gui (not familiar with that). So do that and ISGROUP should start on 002. Regards Dominik _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems -- View this message in context: http://www.nabble.com/Linux-HA-configuration-on-SLES-10.2-problem-tp21725780p21728148.html Sent from the Linux-HA mailing list archive at Nabble.com. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
