Hallo, I'm testing heartbeat 2.1.3 (packaged by debian) and I see a strange behaviour of the failcount. According to <http://www.linux-ha.org/ScoreCalculation> the failcount is increased by 1 every time that my resource is failing. In my experience with heartbeat the fail count is increased by 1 only if the previous value was 0. My test was conducted in this way: I've configured a resource that is an instance of the IPaddr2, I've put the resource_stickiness=3 and the resource_failure_stickyness=-1 RA. The first time I've started the resource the CRM has choose a node (let's say node1) where to put the IP configured by IPaddr2. To test the failure behaviour I've delete (by hand) the IP from the interface configured by my resource and the monitor operation has detected the failure and restored the resource. I've checked that the score of IPaddr2 on the running node was 2 and the failcount was 1. Now, to test a second failure on the same node I deleted again the IP. Also this time the resource was restored and I expected that the score was 1 but the score was 2 and the value of the failcount was not incremented (failcount=1)! It's the normal behaviour of the failcount? There is any parameter on the configuration file or the cib.xml that I must configure to change this "binary" behaviour of the failcount?
Thanks in advance -- Michele Codutti Centro Servizi Informatici e Telematici (CSIT) Universita' degli Studi di Udine via Delle Scienze, 208 - 33100 UDINE tel +39 0432 558928 fax +39 0432 558911 e-mail: michele.codutti at uniud.it _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
