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

Lars Ellenberg lars.ellenberg at linbit.com
Fri Apr 8 09:48:59 EDT 2011

On Fri, Apr 08, 2011 at 09:13:45AM +0200, Andrew Beekhof wrote:
> On Thu, Apr 7, 2011 at 11:48 PM, Colin Hines <colinhines at gmail.com> wrote:
> > 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
> > heartbeat
> > Apr  7 17:44:41 cvt-db-005 cl_status: [5901]: ERROR: REASON: hb_api_signon:
> > Can't initiate connection  to heartbeat
> Someone/something is running cl_status.
> Find out who/what and stop them - it has no place in a corosync based cluster.

That could be the status action of the SBD stonith plugin,
between commits
http://hg.linux-ha.org/glue/rev/faada7f3d069	(Apr 2010)
http://hg.linux-ha.org/glue/rev/1448deafdf79	(May 2010)

if so, upgrade your "cluster glue".

> > I can send my configs, but they're pretty vanilla, has anyone seen anything
> > like this before.   I did have a heartbeat installation on this host before
> > I followed the CFSv2 document, but heartbeat is stopped and I've verified
> > that cl_status doesn't output those errors if I stop corosync.
> > c

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.

More information about the Pacemaker mailing list