Mailing List Archive: Linux-HA: Users

pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat

Index | Next | Previous | View Threaded

tom at tiri

Feb 13, 2012, 12:26 PM

Post #1 of 9 (1268 views)
Permalink

pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat

Hello list,

In my current pacemaker/corosync installation in a 2 node cluster I get
following error:

# cl_status listnodes

cl_status[3681]: 2012/02/13_21:18:57 ERROR: Cannot signon with heartbeat
cl_status[3681]: 2012/02/13_21:18:57 ERROR: REASON: hb_api_signon: Can't
initiate connection to heartbeat

But the Cluster is running:

# crm_mon -1f

============
Last updated: Mon Feb 13 21:20:15 2012
Stack: openais
Current DC: srvrz1 - partition WITHOUT quorum
Version: 1.0.5-ee19d8e83c2a5d45988f1cee36d334a631d84fc7
2 Nodes configured, 1023 expected votes
1 Resources configured.
============

Online: [ srvrz1 srvrz2 ]

Resource Group: gpinst1
vipinst1 (ocf::heartbeat:IPaddr2): Started srvrz1
fsinst1_base (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_db01 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_db02 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_db03 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_db04 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_log1 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_log2 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_dp01 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_dp02 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_cp01 (ocf::heartbeat:Filesystem): Started srvrz1
fsinst1_cp02 (ocf::heartbeat:Filesystem): Started srvrz1
dsminst1 (ocf::tiri:dsmserv): Started srvrz1

Migration summary:
* Node srvrz2:
* Node srvrz1:

I have

cluster-glue 1.0.3
pacemaker 1.0.7
corosync 1.2.0
heartbeat-3.0.2

Best regards,
Thomas
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

andrew at beekhof

Feb 13, 2012, 6:09 PM

Post #2 of 9 (1214 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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

>
> cl_status[3681]: 2012/02/13_21:18:57 ERROR: Cannot signon with heartbeat
> cl_status[3681]: 2012/02/13_21:18:57 ERROR: REASON: hb_api_signon: Can't
> initiate connection to heartbeat
>
> But the Cluster is running:
>
> # crm_mon -1f
>
> ============
> Last updated: Mon Feb 13 21:20:15 2012
> Stack: openais
> Current DC: srvrz1 - partition WITHOUT quorum
> Version: 1.0.5-ee19d8e83c2a5d45988f1cee36d334a631d84fc7
> 2 Nodes configured, 1023 expected votes
> 1 Resources configured.
> ============
>
> Online: [ srvrz1 srvrz2 ]
>
> Resource Group: gpinst1
> vipinst1 (ocf::heartbeat:IPaddr2): Started srvrz1
> fsinst1_base (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_db01 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_db02 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_db03 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_db04 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_log1 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_log2 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_dp01 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_dp02 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_cp01 (ocf::heartbeat:Filesystem): Started srvrz1
> fsinst1_cp02 (ocf::heartbeat:Filesystem): Started srvrz1
> dsminst1 (ocf::tiri:dsmserv): Started srvrz1
>
> Migration summary:
> * Node srvrz2:
> * Node srvrz1:
>
> I have
>
> cluster-glue 1.0.3
> pacemaker 1.0.7
> corosync 1.2.0
> heartbeat-3.0.2
>
> Best regards,
> Thomas
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

florian at hastexo

Feb 14, 2012, 10:50 PM

Post #3 of 9 (1203 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

On 02/14/12 03:09, Andrew Beekhof wrote:
> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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".

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

andrew at beekhof

Feb 15, 2012, 2:12 AM

Post #4 of 9 (1200 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

On Wed, Feb 15, 2012 at 5:50 PM, Florian Haas <florian [at] hastexo> wrote:
> On 02/14/12 03:09, Andrew Beekhof wrote:
>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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 [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

tom at tiri

Feb 15, 2012, 12:49 PM

Post #5 of 9 (1201 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

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-bounces [at] lists
[mailto:linux-ha-bounces [at] lists] 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 <florian [at] hastexo> wrote:
> On 02/14/12 03:09, Andrew Beekhof wrote:
>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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 [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

andrew at beekhof

Feb 16, 2012, 3:56 AM

Post #6 of 9 (1199 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

On Thu, Feb 16, 2012 at 7:49 AM, Thomas Baumann <tom [at] tiri> 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-bounces [at] lists
> [mailto:linux-ha-bounces [at] lists] 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 <florian [at] hastexo> wrote:
>> On 02/14/12 03:09, Andrew Beekhof wrote:
>>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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 [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

tom at tiri

Feb 17, 2012, 10:32 AM

Post #7 of 9 (1184 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

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...

Von meinem tiriPhone gesendet.

Am 16.02.2012 um 12:57 schrieb Andrew Beekhof <andrew [at] beekhof>:

> On Thu, Feb 16, 2012 at 7:49 AM, Thomas Baumann <tom [at] tiri> 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-bounces [at] lists
>> [mailto:linux-ha-bounces [at] lists] 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 <florian [at] hastexo> wrote:
>>> On 02/14/12 03:09, Andrew Beekhof wrote:
>>>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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 [at] lists
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA [at] lists
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

tserong at suse

Feb 19, 2012, 11:06 PM

Post #8 of 9 (1179 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

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<andrew [at] beekhof>:
>
>> On Thu, Feb 16, 2012 at 7:49 AM, Thomas Baumann<tom [at] tiri> 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-bounces [at] lists
>>> [mailto:linux-ha-bounces [at] lists] 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<florian [at] hastexo> wrote:
>>>> On 02/14/12 03:09, Andrew Beekhof wrote:
>>>>> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann<tom [at] tiri> 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 [at] lists
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>>> _______________________________________________
>>> Linux-HA mailing list
>>> Linux-HA [at] lists
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA [at] lists
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>

--
Tim Serong
Senior Clustering Engineer
SUSE
tserong [at] suse
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

lars.ellenberg at linbit

Feb 20, 2012, 2:23 PM

Post #9 of 9 (1155 views)
Permalink

Re: pacemaker/corosync - cl_status . REASON: hb_api_signon: Can't initiate connection to heartbeat [In reply to]

On Wed, Feb 15, 2012 at 09:49:27PM +0100, Thomas Baumann wrote:
> Thanks for your info.
> But which process might run this cl_status as I see these messages in
> syslog nearly all the time ?

the monitor action of the SBD fencing was known to do that.
(stonith external/sbd)
I think it was patched out in some later revision.

It should be sufficient to chmod -x cl_status,
or uninstall the heartbeat stack and tools.
You still need the libs, though.

>
> Best regards,
> Thomas.
>
> -----Ursprüngliche Nachricht-----
> Von: linux-ha-bounces [at] lists
> [mailto:linux-ha-bounces [at] lists] 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 <florian [at] hastexo> wrote:
> > On 02/14/12 03:09, Andrew Beekhof wrote:
> >> On Tue, Feb 14, 2012 at 7:26 AM, Thomas Baumann <tom [at] tiri> 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 [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

--
: 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.
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads