On Thu, Apr 7, 2011 at 11:48 PM, Colin Hines <colinhi...@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. > 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 > _______________________________________________ > 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > _______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker