Roland G. McIntosh wrote: > I've got 3 resources in a group, and I'd like to configure stickiness > values such that if there are more than 3 failures in the group all > resources go to the failover node. I've read > http://www.linux-ha.org/v2/faq/forced_failover many times, but do not > quite understand from that how to configure my cluster stickiness > values, or why crm_failcount does not increment :( > > To keep things simple, I'd like to rely on inherited default stickiness > values as much as possible. > > I'm running Heartbeat 2.1.3 on RHEL4 from RPMs that I got here: > http://mirror.centos.org/centos/4/extras/x86_64/RPMS/ > > Here's an example of crm_failcount not incrementing: > > # crm_failcount -G -U slinkmaster -r slink_db > name=fail-count-slink_db value=0 > # /etc/init.d/postgresql stop > # crm_failcount -G -U slinkmaster -r slink_db > name=fail-count-slink_db value=1 > # /etc/init.d/postgresql stop > # crm_failcount -G -U slinkmaster -r slink_db > name=fail-count-slink_db value=1 > > Can anyone help? Config files attached. If I get this working I would > love to contribute to the wiki to supply the problem solution for the "A > worked example involving a Group" section. > Hi Roland,
Unfortunatly crm_failcount is broken in 2.1.3. Search this list. It's fixed but not yet available as RPM's. So you could compile it yourself in the meanwhile. See a recent thread from Serge here as well. Would you like to ad your voice on the request list for RHEL4 rpm's from the buildservice? :) regards, Johan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
