[Pacemaker] Always Run Clone Resource

[Andrew Beekhof]

On Sat, Mar 24, 2012 at 5:50 AM, Andrew Martin <amartin at xes-inc.com> wrote:
> Hi Andrew,
>
> It did not send me a message that it was being stopped. Is there something
> wrong with my MailTo configuration?

Possbily.

I just confirmed that the RA tries to send a mail on stop:

MailToStop () {
	Subject="`SubjectLine $subject` Migrating resource away at `date` from $us"

	MailProgram "$Subject" $1
	ha_pseudo_resource MailTo_${OCF_RESOURCE_INSTANCE} stop
}


>
> Thanks,
>
> Andrew
>
> ________________________________
> From: "Andrew Beekhof" <andrew at beekhof.net>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, March 21, 2012 9:25:55 PM
> Subject: Re: [Pacemaker] Always Run Clone Resource
>
>
> Shouldnt it have sent you a message that it was being stopped?
>
> On Thu, Mar 22, 2012 at 4:51 AM, Andrew Martin <amartin at xes-inc.com> wrote:
>> Hello,
>>
>> I have a pacemaker/heartbeat cluster that uses several DRBD primitives.
>> The
>> cluster resources are all colocated and ordered to start after the
>> DRBD primitives. I have configured an ocf:heartbeat:MailTo primitive and
>> clone for notifying me of any changes in the cluster state:
>> primitive p_notify ocf:heartbeat:MailTo \
>>         params email="myaddr at example.com" \
>>         params subject="Alert Pacemaker Change" \
>>         op start interval="0" timeout="10" \
>>         op stop interval="0" timeout="10" \
>>         op monitor interval="10" timeout="10"
>> ...
>> clone cl_notify p_notify
>>
>> This MailTo primitive and clone are NOT part of the colocation or order
>> rules for the rest of the resources. Last night all of the resources in
>> the
>> cluster stopped because of a syntax error in the DRBD config. This also
>> stopped the MailTo resources, and thus I was not notified of the error
>> state
>> in the cluster. How can I configure the MailTo resources to be running
>> always, regardless of the state of the rest of the resources in the
>> cluster?
>>
>> Thanks,
>>
>> Andrew
>>
>> _______________________________________________
>> 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://bugs.clusterlabs.org
>>
>
> _______________________________________________
> 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://bugs.clusterlabs.org
>
>
> _______________________________________________
> 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://bugs.clusterlabs.org
>