On Tue, Jan 18, 2011 at 1:46 AM, Thomas Guthmann <tguthm...@iseek.com.au> wrote: > Hey, > >>> This may be dumb or obvious but it took me a long time to understand why my >>> pingd with >>> dampen never got updated! So I think that this may be useful for everybody >>> to share. >>> In short: >>> >>> " You MUST define a monitor interval HIGHER than the the dampen delay. " >> Which version was this? >> I seem to recall fixing something similar to this (its a bug in attrd) >> but 1.0.10 should be ok. > > It was 1.0.8 and 1.0.9. > > BTW, what would the best way to do : > " if 3 pings fail with an interval of 30 seconds between each > then > set pingd to 0. > else > keep pingd to 1 > " > > My main goal is to migrate _nothing_ if an external IP (usually > gateway) has a temporary hiccup. I am doing this right now but I > am open for comments. > > primitive pingd ocf:pacemaker:ping \ > params host_list="EXT.ERN.AL.IP" attempts="3" timeout="2" debug="true" > options="-i30" \ > op monitor interval="120" timeout="130" \ > op start interval="0" timeout="90" \ > op stop interval="0" timeout="90" > > Note that sometimes I have strange pacemaker timeout errors. > What does exactly represent "timeout" in op monitor ?
It means how long the operation is allowed to take. Looks about right. Any errors? _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
