On 02/18/2012 05:32 AM, Thomas Baumann wrote: > But which could these be? It seems SuSE specific? Should I post a rpm -ql ? > How can it be debugged - there are lots of recurring messages...
If those errors are in syslog, what's the name of the process generating them? That might help a bit. Anyway, regardless of that, you said you had installed: > cluster-glue 1.0.3 > pacemaker 1.0.7 > corosync 1.2.0 > heartbeat-3.0.2 If you're running a pacemaker cluster on corosync, you neither need nor want heartbeat installed. I'd suggest removing heartbeat and seeing if those messages go away. Regards, Tim > > Von meinem tiriPhone gesendet. > > > Am 16.02.2012 um 12:57 schrieb Andrew Beekhof<and...@beekhof.net>: > >> On Thu, Feb 16, 2012 at 7:49 AM, Thomas Baumann<t...@tiri.li> wrote: >>> Thanks for your info. >>> But which process might run this cl_status as I see these messages in >>> syslog nearly all the time ? >> >> I just assumed you were running it. >> Some sort of external monitoring script perhaps? >> >>> >>> Best regards, >>> Thomas. >>> >>> -----Ursprüngliche Nachricht----- >>> Von: linux-ha-boun...@lists.linux-ha.org >>> [mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Andrew Beekhof >>> Gesendet: Mittwoch, 15. Februar 2012 11:13 >>> An: General Linux-HA mailing list >>> Betreff: Re: [Linux-HA] pacemaker/corosync - cl_status . REASON: >>> hb_api_signon: Can't initiate connection to heartbeat >>> >>> On Wed, Feb 15, 2012 at 5:50 PM, Florian Haas<flor...@hastexo.com> wrote: >>>> On 02/14/12 03:09, Andrew Beekhof wrote: >>>>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann<t...@tiri.li> wrote: >>>>>> Hello list, >>>>>> >>>>>> In my current pacemaker/corosync installation in a 2 node cluster I >>>>>> get following error: >>>>>> >>>>>> # cl_status listnodes >>>>> >>>>> This is a heartbeat command, you're running corosync Try crm_node -p >>>> >>>> Or to get the straight-up Corosync view, "corosync-objctl | grep >>>> member". >>> >>> Unless you're using corosync 2.0 in which case its: >>> >>> corosync-cmapctl | grep member >>> _______________________________________________ >>> Linux-HA mailing list >>> Linux-HA@lists.linux-ha.org >>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>> See also: http://linux-ha.org/ReportingProblems >>> _______________________________________________ >>> Linux-HA mailing list >>> Linux-HA@lists.linux-ha.org >>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>> See also: http://linux-ha.org/ReportingProblems >> _______________________________________________ >> Linux-HA mailing list >> Linux-HA@lists.linux-ha.org >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > > -- Tim Serong Senior Clustering Engineer SUSE tser...@suse.com _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
