[Pacemaker] Preventing resource from becoming inactive

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


David Mohr writes:

> On Tue, 10 Aug 2010 07:56:47 +0200, Torsten Bronger
> <bronger at physik.rwth-aachen.de> wrote:
>> 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?
> [...]
>> location lighty-on-connected-node lighty_group \
>>        rule $id="lighty-on-connected-node-rule" -inf: not_defined \
>>        pingd or pingd lte 0
> The last location rule says that lighty_group should never run on
> a node that doesn't have connectivity. So if the ping node goes
> down, then lighty_group will be shut down everywhere.

Yes but it should bring Lighty up again as soon as connectivity is
restored.  Well, it doesn't.  But it should.  Besides, -100 instead
of -inf didn't help.

> I'm not certain on how to improve this situation, since I'm having
> trouble with a similar configuration. In principle you should be
> assigning a positive score to nodes that can ping, so that you
> don't assign negative scores. As far as I know only negative
> scores can cause pacemaker to shut down a resource.

Interesting.  So I just have to negate the condition?


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