On 13 Nov 2013, at 12:06 am, Robert H. <pacema...@elconas.de> wrote:
> Hello, > > for PaceMaker 1.1.8 (CentOS Version) the thread > http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg18048.html was > solved with adding cluster-recheck-interval="5m", causing the LRM Its the policy engine btw. Not the lrmd. > to be executed every 5 minutes and detecting externally managed resources as > started (in this case an externally managed percona cluster). cluster-recheck-interval shouldn't have anything to do with it. its completely handled by: op monitor enabled="true" timeout="20s" interval="11s" role="Stopped" So the questions to ask: 1. is that recurring operation being executed? 2. is it reporting accurate results? (For 1., this happens without the involvement of cluster-recheck-interval, the lrmd will re-run the command every 'interval' seconds). > > Now the same cluster was updated to 1.1.10 (new upstream) and it seems that > the problem is back again. It seems that cluster-recheck-interval="5m" does > not cause the LRM to be executed again after 5 minutes, detecting, that > external - unmanaged ressources are started again. CIB is unmodified. > > Has something changed in the upstream release ? Not intentionally. > Any hints ? Have a read of the section "But wait there’s still more" of http://blog.clusterlabs.org/blog/2013/pacemaker-logging/ and see if you can get the information from the lrmd process to answer questions 1 and 2 above.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Pacemaker mailing list: Pacemaker@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://bugs.clusterlabs.org
