[Pacemaker] Multistate Resources is not promoted automatically

Andrew Beekhof andrew at beekhof.net
Thu Nov 11 10:46:42 UTC 2010


On Thu, Nov 11, 2010 at 11:38 AM, Simon Jansen
<simon.jansen1 at googlemail.com> wrote:
> Hi Andrew,
>
> thank you for your answer.
>
>> Does the ocf:heartbeat:Rsyslog script call crm_master?
>> It needs to to tell pacemaker which instance to promote.
>
> Yes it does. But I forgot to call crm_master with the option -D in the stop
> action. I think that this was the error. After correcting this issue the ra
> starts as expected.
>
>> Two questions though...
>> 1) Why use master/slave for rsyslog?
>
> In the master role the rsyslog daemon should function as central log server
> and write the entries received on UDP port 514 into a MySQL database.
> On the passive node the rsyslog service should be started with the standard
> config.

Interesting

> Do you think there is a better solution to solve this requirement?

No, I'd just never heard rsyslog being used in this way.

>>
>> 2) Is this an upstream RA? If not, you shouldn't be using the
>> ocf:heartbeat namespace.
>
> Ok thank you for the advice. Should I use the pacemaker class instead or
> should I define a custom namespace?

Custom.

>
> --
>
> Regards,
>
> Simon Jansen
>
>
> ---------------------------
> Simon Jansen
> 64291 Darmstadt
>
>
> _______________________________________________
> 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