Hi, Andrew I made a version of Pacemaker latest. Then pacemaker came to fail in start.
I think that this came to be caused by the following changes. https://github.com/ClusterLabs/pacemaker/commit/4f88cb1049e898726472a91fff834dcccbd6f665 I confirm movement in the following versions now. OS: RHEL6.3 # pacemakerd -F Pacemaker 1.1.8 (Build: bd68c20) Supporting: agent-manpages ncurses libqb-logging libqb-ipc lha-fencing heartbeat corosync-native # corosync -v Corosync Cluster Engine, version '2.1.0.1-20c58' I collected crm_report of this time. Did how to use pacemaker change? Does my setting have a problem? Best Regards, Yuusuke -- ---------------------------------------- METRO SYSTEMS CO., LTD Yuusuke Iida Mail: iiday...@intellilink.co.jp ----------------------------------------
start_fail.tar.bz2
Description: Binary data
_______________________________________________ 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
