[Pacemaker] Preventing resource from becoming inactive
Dejan Muhamedagic
dejanmm at fastmail.fm
Tue Aug 10 10:45:51 UTC 2010
Hi,
On Tue, Aug 10, 2010 at 07:56:47AM +0200, Torsten Bronger wrote:
> Hallöchen!
>
> Sometimes Pacemaker just switches off my Lighttpd.
How do you mean "just switches off"?
> It becomes
> inactive and is never reanimated. Only restarting the Heartbeat
> service helps. How can I tell Pacemaker to retry to restart
> lighttpd without ever giving up?
As soon as the migration-threshold is reached, the resource
cannot be started again on that node until the failcount is
cleared. Is that what you're seeing?
Thanks,
Dejan
> Since I use Lighty as a load balancer, it is tied with my public
> IP. I suspect that pingd is non-working in the exact instance
> Lighty is set to "inactive".
>
> primitive Public-IP ocf:heartbeat:IPaddr2 \
> params ip="134.94.252.127" broadcast="134.94.253.255" \
> nic="eht0" cidr_netmask="23" \
> op monitor interval="60s" timeout="10s" \
> meta migration-threshold="10"
> primitive lighty lsb:lighttpd \
> op monitor interval="60s" timeout="30s" on-fail="restart" \
> op start interval="0" timeout="60s" \
> meta migration-threshold="3" failure-timeout="30s" \
> target-role="Started"
> primitive pingd ocf:pacemaker:pingd \
> params host_list="134.94.111.186" multiplier="100" \
> op monitor interval="15s" timeout="20s"
> group lighty_group Public-IP lighty
> clone pingclone pingd meta globally-unique="false"
> location lighty-on-connected-node lighty_group \
> rule $id="lighty-on-connected-node-rule" -inf: not_defined pingd or pingd lte 0
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger, aquisgrana, europa vetus
> Jabber ID: torsten.bronger at jabber.rwth-aachen.de
> or http://bronger-jmp.appspot.com
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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
More information about the Pacemaker
mailing list