On 14 Jan 2014, at 5:13 am, Brian J. Murrell (brian) <br...@interlinx.bc.ca> wrote:
> Hi, > > I found a situation using pacemaker 1.1.10 on RHEL6.5 where the output > of "crm_resource -L" is not trust-able, shortly after a node is booted. > > Here is the output from crm_resource -L on one of the nodes in a two > node cluster (the one that was not rebooted): > > st-fencing (stonith:fence_foo): Started > res1 (ocf::foo:Target): Started > res2 (ocf::foo:Target): Started > > Here is the output from the same command on the other node in the two > node cluster right after it was rebooted: > > st-fencing (stonith:fence_foo): Stopped > res1 (ocf::foo:Target): Stopped > res2 (ocf::foo:Target): Stopped > > These were collected at the same time (within the same second) on the > two nodes. > > Clearly the rebooted node is not telling the truth. Perhaps the truth > for it is "I don't know", which would be fair enough but that's not what > pacemaker is asserting there. > > So, how do I know (i.e. programmatically -- what command can I issue to > know) if and when crm_resource can be trusted to be truthful? The local cib hasn't caught up yet by the looks of it. You could compare 'cibadmin -Ql' with 'cibadmin -Q' > > b. > > > > > _______________________________________________ > 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
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
