[ClusterLabs] Connection to the CPG API failed: Library error (2)

Jan Friesse jfriesse at redhat.com
Mon Feb 1 13:19:14 UTC 2016 

Karthikeyan Ramasamy napsal(a):
> Hi Honza,
>    A team is already working on moving to the latest linux.  However, we delivered a feature with RHEL6.5, which has run into this issue.  Any tip would be very helpful for us!

It's highly probably caused by corosync, but it's really hard to say, 
what patch can help solve problem you hit (we did rebase in RHEL 6.6). 
So no real hint. Just upgrade to something supported.

Regards,
   Honza

>
> Thanks,
> Karthik.
>
> -----Original Message-----
> From: Jan Friesse [mailto:jfriesse at redhat.com]
> Sent: 01 பிப்ரவரி 2016 13:43
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: Re: [ClusterLabs] Connection to the CPG API failed: Library error (2)
>
> Karthikeyan Ramasamy napsal(a):
>> Sorry missed important information.
>>
>> We are using RHEL6.5 and Pacemaker 1.1.10-14.
>
> 6.5 EUS is over (ended November 30, 2015), so it's good idea to update.
>
> Regards,
>     Honza
>
>
>>
>> Thanks,
>> Karthik.
>>
>> -----Original Message-----
>> From: Karthikeyan Ramasamy [mailto:karthikeyan.ramasamy at ericsson.com]
>> Sent: 01 பிப்ரவரி 2016 13:21
>> To: Cluster Labs - All topics related to open-source clustering
>> welcomed
>> Subject: [ClusterLabs] Connection to the CPG API failed: Library error
>> (2)
>>
>> Hello Pacemaker Users,
>>     We are having a problem with cman failing, when the host server is
>> under load and processing traffic.  Following information is available
>> in the logs,
>>
>>
>> Jan 30 06:53:13 [2041] vmc0135      attrd:    error: pcmk_cpg_dispatch:         Connection to the CPG API failed: Library error (2)
>> Jan 30 06:53:13 [2043] vmc0135       crmd:    error: pcmk_cpg_dispatch:         Connection to the CPG API failed: Library error (2)
>> Jan 30 06:53:13 [2043] vmc0135       crmd:    error: crmd_cs_destroy:   connection terminated
>> Jan 30 06:53:13 [2041] vmc0135      attrd:     crit: attrd_cs_destroy:  Lost connection to Corosync service!
>> Jan 30 06:53:13 [2043] vmc0135       crmd:     info: qb_ipcs_us_withdraw:       withdrawing server sockets
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_cs_flush:      Sent 0 CPG messages  (1 remaining, last=129): Library error (2)
>> Jan 30 06:53:13 [2038] vmc0135        cib:    error: pcmk_cpg_dispatch:         Connection to the CPG API failed: Library error (2)
>> Jan 30 06:53:13 [2038] vmc0135        cib:    error: cib_cs_destroy:    Corosync connection lost!  Exiting.
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: terminate_cib:     cib_cs_destroy: Exiting fast...
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_client_destroy:        Destroying 0 events
>> Jan 30 06:53:13 [2041] vmc0135      attrd:   notice: main:      Exiting...
>> Jan 30 06:53:13 [2041] vmc0135      attrd:   notice: main:      Disconnecting client 0x611c30, pid=2043...
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: qb_ipcs_us_withdraw:       withdrawing server sockets
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_client_destroy:        Destroying 0 events
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:    error: pcmk_cpg_dispatch:         Connection to the CPG API failed: Library error (2)
>> Jan 30 06:53:13 [2043] vmc0135       crmd:     info: tengine_stonith_connection_destroy:        Fencing daemon disconnected
>> Jan 30 06:53:13 [2043] vmc0135       crmd:   notice: crmd_exit:         Forcing immediate exit: Link has been severed (67)
>> Jan 30 06:53:13 [2043] vmc0135       crmd:     info: crm_xml_cleanup:   Cleaning up memory from libxml2
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:    error: stonith_peer_cs_destroy:   Corosync connection terminated
>> Jan 30 06:53:13 [2041] vmc0135      attrd:    error: attrd_cib_connection_destroy:      Connection to the CIB terminated...
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:    error: cfg_connection_destroy:    Connection destroyed
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: stonith_shutdown:  Terminating with  1 clients
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:   notice: pcmk_shutdown_worker:      Shuting down Pacemaker
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:   notice: stop_child:        Stopping crmd: Sent -15 to process 2043
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:    error: pcmk_cpg_dispatch:         Connection to the CPG API failed: Library error (2)
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:    error: mcp_cpg_destroy:   Connection destroyed
>> Jan 30 06:53:13 [2021] vmc0135 pacemakerd:     info: crm_xml_cleanup:   Cleaning up memory from libxml2
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: cib_connection_destroy:    Connection to the CIB closed.
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: crm_client_destroy:        Destroying 0 events
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_client_destroy:        Destroying 0 events
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: qb_ipcs_us_withdraw:       withdrawing server sockets
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: main:      Done
>> Jan 30 06:53:13 [2039] vmc0135 stonith-ng:     info: crm_xml_cleanup:   Cleaning up memory from libxml2
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: qb_ipcs_us_withdraw:       withdrawing server sockets
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_client_destroy:        Destroying 0 events
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: qb_ipcs_us_withdraw:       withdrawing server sockets
>> Jan 30 06:53:13 [2038] vmc0135        cib:     info: crm_xml_cleanup:   Cleaning up memory from libxml2
>>
>>
>> We are trying to figure out when is this happening.  In the meantime, guidance from expert users would be very helpful for us.  Please let me know if you have already seen this issue and the probable causes.
>>
>> Thanks,
>> Karthik.
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>

More information about the Users mailing list