According to the homepage: auto_failback does not have any effect on a Release 2 CRM-style cluster (one configured with crm on). For CRM-style clusters, this has been replaced with the default_resource_stickiness attribute in the CIB.
so if "crm on" ---> auto_failback = ignored the values you have to look in are: resource_stickiness resource_failure_stickiness if you use heartbeat version 1 (no CIB) configuration set auto_failback no On Tuesday 28 August 2007, Michael Dengler wrote: > GRRRRRR..... > > OK...i have *auto_failback *set to no. > > and > > do a "service network stop" on the primary node....fine > > the standby comes up and starts all the resources...fine > > then i do a "service network start" on the primary node.... > > heartbeat FAILS BACK! why? > > I'm very confused...Please help.... > > Mike > > On 8/10/07, Andrew Beekhof <[EMAIL PROTECTED]> wrote: > > On 8/10/07, Mark Eisenblaetter <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > you must cofigure autofailback no in your ha.cf. > > > > > > so the sytem will stop to failback on the preferred node. > > > > the crm/cib.xml equivalent is default_resource_stickiness > > _______________________________________________ > > 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 -- 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| [EMAIL PROTECTED] _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
