[ClusterLabs] Antw: CRM location specification and errors

[Ulrich Windl]

Hi!

I guess the cluster is running monitor operations on the forbidden node to make sure no resources run there: Meaning: If you had started those resources on the forbidden node, the cluster would stop them. To find out it runs the monitors.

Regards,
Ulrich

>>> Matthew Vernon <mcv21 at cam.ac.uk> schrieb am 25.06.2015 um 18:07 in Nachricht
<558C2747.7040207 at cam.ac.uk>:
> Hi,
> 
> I have a 3-node cluster, with 2 nodes of type "xenhost", and one node of
> type "quorum". I have a location defined that should stop my resource
> from being run on the "quorum" node, and yet crm_mon always shows
> something like:
> 
> Failed actions:
>     written_monitor_0 on on 'not installed' (5): call=68,
> status=complete, last-rc-change='Thu Jun 25 16:58:38 2015', queued=0ms,
> exec=22ms
>     written_monitor_0 on on 'not installed' (5): call=68,
> status=complete, last-rc-change='Thu Jun 25 16:58:38 2015', queued=0ms,
> exec=22ms
> 
> ...and if I do crm resource cleanup written, the only effect is that the
> timestamp updates.
> 
> Why, if I have specified that my resource "written" is only to be run on
> "xenhost" nodes is the cluster trying to monitor it on the quorum node?
> Better, how can I stop it doing so (or, if that's impossible, suppress
> the errors)?
> 
> Relevant bits of config:
> node 739821491: on \
>         attributes type=quorum standby=off
> node 739821492: ophon \
>         attributes type=xenhost maintenance=off standby=off
> node 739821493: opus \
>         attributes type=xenhost maintenance=off standby=off
> primitive written Xen \
> [config snipped, can include if you like]
> location xenhosts written \
>         rule -inf: type ne xenhost
> 
> Thanks,
> 
> Matthew
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org 
> http://clusterlabs.org/mailman/listinfo/users 
> 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org