Re: [ClusterLabs] Pacemaker not invoking monitor after $interval
> -Ursprüngliche Nachricht- > Von: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com] > Gesendet: Freitag, 20. Mai 2016 13:52 > An: Felix Zachlod (Lists) <fz.li...@onesty-tech.de> > Cc: users@clusterlabs.org > Betreff: Re: [ClusterLabs] Pacemaker not invoking monitor after > $interval > > Le Fri, 20 May 2016 11:33:39 +, > "Felix Zachlod (Lists)" <fz.li...@onesty-tech.de> a écrit : > > > Hello! > > > > I am currently working on a cluster setup which includes several > > resources with "monitor interval=XXs" set. As far as I understand > > this should run the monitor action on the resource agent every XX > > seconds. But it seems it doesn't. > > How do you know it doesn't? Are you looking at crm_mon? log files? I created a debug output from my RA. Furthermore I had a blackbox dump. But it now turned out, that for my resource I had to change meta-data to advertise monitor action twice (one for slave, one for master) and setup op monitor role=x interval=y instead of op monitor interval=x Since that I changed it at least for this resource monitor is working as desired. At least for now. Not sure why a Master/Slave resource has to have distinct monitor actions advertised for both roles but it seems related to that. Still don't see any monitor invocations in the log but seems there is still something wrong with the log level. Thanks anyway! regards, Felix ___ Users mailing list: Users@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
Re: [ClusterLabs] Pacemaker not invoking monitor after $interval
Le Fri, 20 May 2016 11:33:39 +, "Felix Zachlod (Lists)"a écrit : > Hello! > > I am currently working on a cluster setup which includes several resources > with "monitor interval=XXs" set. As far as I understand this should run the > monitor action on the resource agent every XX seconds. But it seems it > doesn't. How do you know it doesn't? Are you looking at crm_mon? log files? If you are looking at crm_mon, the output will not be updated unless some changes are applied to the CIB or a transition is in progress. > Actually monitor is only invoked in special condition, e.g. cleanup, > start and so on, but never for a running (or stopped) resource. So it won't > detect any resource failures, unless a manual action takes place. It won't > update master preference either when set in the monitor action. > > Are there any special conditions under which the monitor will not be > executed? Could you provide us with your Pacemaker setup? > (Cluster IS managed though) Resources can be unmanaged individually as well. Regards, -- Jehan-Guillaume de Rorthais Dalibo ___ Users mailing list: Users@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