On Thu, 2018-08-23 at 08:08 +0200, Ulrich Windl wrote: > Hi! > > Many years ago I wrote a parser that could format the CIB XML in a > flexible way. Today I used it again to print some statistics for > "exec-time". Thereby I discovered one operation that has a valid > "exec-time", a valid "last-rc-change", but no "last-run". > All other operations had "last-run". Can someone explain how this can > happen? The operation in question is "monitor", so it should be run > frequently (specified as "op monitor interval=600 timeout=30").
Recurring actions never get last-run, because the crmd doesn't initiate each run of a recurring action. > I see no failed actions regarding the resource. > > The original XML part for the operation looks like this: > <lrm_rsc_op id="prm_cron-cleanup_monitor_600000" > operation_key="prm_cron-cleanup_monitor_600000" operation="monitor" > crm-debug-origin="build_active_RAs" crm_feature_set="3.0.10" > transition-key="92:3:0:6c6eff09-0d57-4844-9c3c-bc300c095bb6" > transition-magic="0:0;92:3:0:6c6eff09-0d57-4844-9c3c-bc300c095bb6" > on_node="h06" call-id="151" rc-code="0" op-status="0" > interval="600000" last-rc-change="1513367408" exec-time="13" queue- > time="0" op-digest="2351b51e5316689a0eb89e8061445728"/> > > The node is not completely up-to-date, and it's using pacemaker- > 1.1.12-18.1... > > Regards, > Ulrich > > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > https://lists.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 -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Users mailing list: Users@clusterlabs.org https://lists.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