On Mon, Apr 23, 2012 at 8:16 PM, Lars Marowsky-Bree <[email protected]> wrote: > On 2012-04-21T10:15:23, Arnold Krille <[email protected]> wrote: > >> But I still get error-messages ($OCF_ERR_NOT_INSTALLED) when the cluster >> tries >> to monitor the resources on the third node. I don't want that. I want the >> cluster to either not even run monitor (for these resources) on the third >> node >> or to ignore monitor-errors from these resources on the third node. >> How to achieve this? Do I have to add anti-location rules for all the >> resources in that group individually? > > No. The cluster will always run the probes to find out if the service is > active there by accident.
Or still running there after a crash. Or after someone ran "crm resource cleanup". > You cannot disable this safely. > > > > Regards, > Lars > > -- > Architect Storage/HA > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, > HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > > _______________________________________________ > Pacemaker mailing list: [email protected] > 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: [email protected] 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
