Hi Raoul [EMAIL PROTECTED] wrote on 21.12.2007 10:35:13: > differences i spot at my system: > > > <nvpair id="default-resource-stickiness" name="default-resource- > stickiness" value="0"/> > > <nvpair id="stop-orphan-resources" name="stop-orphan- > resources" value="false"/> > > <nvpair id="transition-idle-timeout" name="transition-idle- > timeout" value="60"/> > > mybe the default-resource-stickiness set to INFINITY causes the problem?
If I understand it right the default-resource-stickiness is used to let the resource running on the redundance if a failure has happened on the master which is solved now. So the resource is still on the redundance until it is moved back to the master by hand. That is what I want and so I think this setting is correct. But correct me if I'm wrong! A change of stop-orphan-resources to false makes no difference in the behaviour: The resource is switched to the redundance. But why? There is no failure, the resource is running on the master as it should do. Why is it switching to the redundance if this machine comes up? Yves Schumann Softwareentwicklungsingenieur Security Solutions Division ______________________________ Ascom (Schweiz) AG Eichtal, CH-8634 Hombrechtikon Phone: +41 55 254 66 84 [EMAIL PROTECTED] http://www.ascom.com _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
