On Tue, 25 Jun 2013 11:37:15 -0400 (EDT) Jake Smith <jsm...@argotec.com> wrote:
> You probably already know but you're going to get failed "not > installed" from test4 always unless you install the same packages > there. > > Do you have logs from test4-node[1|2] that are generating the not > installed for o2cb? The log below is just from test4 if I'm not > mistaken which we expect doesn't have o2cb installed. Hi Jake, the log is from test4-node2, the machine was renamed and in the logs it still shows up as test4. It has o2cb installed. I can use the Drive fine on this machine when I start o2cb and ocfs2 by hand and mount the drive. > A quick search for "ERROR: Wrong stack o2cb" indicates you may want > to verify o2cb isn't starting on boot? But that's just a guess > without the logs from the affected nodes. I've executed "update-rc.d o2cb disable" and "update-rc.d ocfs2 disable". The services are stopped and pacemaker/corosync should handle everything. o2cb is still enabled in /etc/default/o2cb but the init-Script isn't executed on boot. Best regards Denis Witt _______________________________________________ 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
