Thanks for your info. But which process might run this cl_status as I see these messages in syslog nearly all the time ?
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
