[Pacemaker] adding third node, how to stop it trying to run monitor resources

[Andreas Kurz]

On 05/26/2011 08:16 PM, Jelle de Jong wrote:
> Hello everybody,
> 
> I am trying to add a third quorum node, however while the third node
> being in standy it keeps trying and trying to start a VirtualDomain
> monitor the third node cant run kvm or other resources (small Debian
> Linux device)
> 
> # the output of crm_mon showing my issue
> http://paste.debian.net/118081/
> 
> #my config
> http://paste.debian.net/118080/
> 
> Is there a simple way to change my config to tell it to never ever try
> to run anything on my third node ebony except checking quorum. (to
> detect network failures and prevent other nodes from starting the kvm
> guests when coming back online from a network issues)

There is no need (and no easy way) to disable these probes ... maybe the
output of crm_mon is not really nice but in fact only informational ...
so simply get used to the output for your quorum node ;-)

Regards,
Andreas

> 
> Thanks in advance,
> 
> Kind regards,
> 
> Jelle de Jong
> 
> _______________________________________________
> 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
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 286 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110526/58779817/attachment-0004.sig>