On Fri, Sep 18, 2009 at 12:52 PM, Enno Gröper <[email protected]> wrote: > Hi, > I'm using pacemaker with heartbeat to run a 2 node dhcp server cluster > with shared disk using drbd for the lease file. > After upgrading from using heartbeat 2.1.3 (lenny packages) alone (I > purged the old install and removed rest of the old files by hand) I have > some strange problems. > When stopping the monitored dhcp service using "/etc/init.d/dhcp3-server > stop" pacemaker recognises this as expected, but instead of simply > trying to restart the resource on the same node it leaves it stopped > (the other node is in standby mode). > To achieve what I want (and what I think was default behaviour using > heartbeat 2.1.3) I set migration_threshold to 1. > However failcount is set to INFINITY instead of being increased by 1 so > this doesn't matter. > I thougt failcount is only set to INFINITY if failures occur on starting > a resource?
With migration-threshold = 1, _any_ failure will force the resource to another node. Including monitor failures. > Did I understand anything wrong? > > btw: I'm using this repo: > deb http://people.debian.org/~madkiss/ha lenny main > > What is the difference to the following repo? I'm using heartbeat and > not openais. > deb http://people.debian.org/~madkiss/ha-corosync lenny main For people using heartbeat, the differences are a slightly more recent version of Pacemaker and a new package division (the resource agents and core libraries were split into sub projects). _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
