There's something wrong with your logging setup... I see a lot of:
Sep 4 15:57:00 [EMAIL PROTECTED] pengine: [7845]: ERROR: cl_log: 57 messages
were dropped
Sep 4 15:57:00 [EMAIL PROTECTED] pengine: [7845]: ERROR: cl_log: 61 messages
were dropped
Sep 4 15:57:00 [EMAIL PROTECTED] pengine: [7845]: ERROR: cl_log: 54 messages
were dropped
which makes the hb_report archive not so useful.
This is likely your problem though:
<rsc_location id="loc_for_ibp3" rsc="ibp3">
<rule score="INFINITY" id="loc_for_ibp3_rule_for_ibp3">
^^^^^^^^^^
You're saying it MUST (score=infinity) run on ibp3 and it MUST
(stickiness=infinity) stay where it is.
You can't have both be true :-)
On Thu, Sep 4, 2008 at 21:12, Itay Donenhirsch <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> default-resource-stickiness is INFINITY
> failure stickiness is -INFINITY
>
> I bring down host ibp3 and the resources migrate to ibp-standby
>
> When I bring ibp3 back up the resources come back to ibp3, although that I
> need no auto auto failback.
>
> What is the reason?
>
> Thanks
> Itay
>
> p.s.: Attached is the hb_report tarball
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
