[Pacemaker] Preventing resource from becoming inactive

Torsten Bronger bronger at physik.rwth-aachen.de
Tue Aug 10 01:56:47 EDT 2010


Sometimes Pacemaker just switches off my Lighttpd.  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?

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="" broadcast="" \
	   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" \
primitive pingd ocf:pacemaker:pingd \
       params host_list="" 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


Torsten Bronger, aquisgrana, europa vetus
                   Jabber ID: torsten.bronger at jabber.rwth-aachen.de
                                  or http://bronger-jmp.appspot.com

More information about the Pacemaker mailing list