[Pacemaker] Setting the logfile option in corosync.conf to a directory not created causes corosync to fail to start with non-descriptive parse error...

2011-04-08 Thread Colin Hines
Just adding this as an FYI if anyone comes across it... Not creating the logfile directory that is listed in corosync.conf will create the following log errors and corosync will fail to start (this is with the latest rpm based builds from http://www.clusterlabs.org/rpm/epel-5/ Apr 8 12:34:24 cvt

Re: [Pacemaker] Following the clusters from scratch v2 document, and coming up with weird (erroneous?) errors...

2011-04-08 Thread Colin Hines
sages. I can break/fix the issue by installing and removing the heartbeat-3.0.3-2.3.el5.x86_64 package. c On Fri, Apr 8, 2011 at 9:48 AM, Lars Ellenberg wrote: > On Fri, Apr 08, 2011 at 09:13:45AM +0200, Andrew Beekhof wrote: > > On Thu, Apr 7, 2011 at 11:48 PM, Colin Hines > wrote

[Pacemaker] Following the clusters from scratch v2 document, and coming up with weird (erroneous?) errors...

2011-04-07 Thread Colin Hines
I've recently followed the clusters from scratch v2 document for RHEL and although my cluster works and fails over correctly using corosync, I have the following error message coming up in my logs consistently, twice a minute: Apr 7 17:44:41 cvt-db-005 cl_status: [5901]: ERROR: Cannot signon with