Hi all, I hope to release the first release candidate for Pacemaker 2.1.2 next week.
One of the most noticeable changes will be in failed action displays in crm_mon. (This change will *not* show up if Pacemaker is built with the --enable-compat-2.0 option.) An example from one of our regression tests, using the familiar display: * ClusterIP:0_monitor_30000 on fc16-builder 'not running' (7): call=11, status='complete', last-rc-change='Wed Feb 22 11:04:34 2012', queued=0ms, exec=20ms As of 2.1.2, that display will still be available if crm_mon is given the --show-detail option, but by default it will now look like: * ClusterIP:0 30s-interval monitor on fc16-builder returned 'not running' at Wed Feb 22 11:04:34 2012 after 20ms Here's another before-and-after example: * rsc1_monitor_10000 on sles11-1 'not installed' (5): call=26, status='Not installed', last-rc-change='Thu Aug 8 20:20:39 2013', queued=0ms, exec=0ms * rsc1 10s-interval monitor on sles11-1 could not be executed (Not installed) at Thu Aug 8 20:20:39 2013 Combined with exit reasons now displayed for internal errors, this should hopefully make it easier to quickly see what's wrong (or at least a decent pointer in the right direction). -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/