RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1141367 - cmirrord: cpg_dispatch failed: SA_AIS_ERR_LIBRARY
Summary: cmirrord: cpg_dispatch failed: SA_AIS_ERR_LIBRARY
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.6
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-12 19:26 UTC by Corey Marthaler
Modified: 2015-07-22 07:24 UTC (History)
12 users (show)

Fixed In Version: corosync-1.4.7-2.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-22 07:24:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch to fix (596 bytes, patch)
2014-12-09 13:35 UTC, Christine Caulfield 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1389 0 normal SHIPPED_LIVE corosync bug fix and enhancement update 2015-07-20 17:58:11 UTC

Description Corey Marthaler 2014-09-12 19:26:42 UTC 
Description of problem:
I've been seeing these failure messages while running cmirror configuration tests. They don't appear to cause any problems however, just worrisome to see in the logs.

./lvm_config -R $sts_cluster_resource_file -m 

Sep 12 14:08:37 grant-01 qarshd[4037]: Running cmdline: vgchange -ay mirror_6_5263
Sep 12 14:08:38 grant-01 lvm[4747]: Monitoring mirror device mirror_6_5263-mirror_6_52630 for events.
Sep 12 14:08:38 grant-01 lvm[4747]: mirror_6_5263-mirror_6_52630 is now in-sync.
Sep 12 14:08:39 grant-01 lvm[4747]: No longer monitoring mirror device mirror_6_5263-mirror_6_52630 for events.
Sep 12 14:08:39 grant-01 multipathd: dm-135: remove map (uevent)
Sep 12 14:08:39 grant-01 multipathd: dm-135: devmap not registered, can't remove
Sep 12 14:08:39 grant-01 cmirrord[18871]: cpg_dispatch failed: SA_AIS_ERR_LIBRARY
Sep 12 14:08:39 grant-01 multipathd: dm-135: remove map (uevent)
Sep 12 14:08:39 grant-01 multipathd: dm-135: devmap not registered, can't remove
Sep 12 14:08:39 grant-01 multipathd: dm-34: remove map (uevent)
Sep 12 14:08:39 grant-01 multipathd: dm-34: devmap not registered, can't remove
Sep 12 14:08:39 grant-01 multipathd: dm-34: remove map (uevent)


Version-Release number of selected component (if applicable):
2.6.32-502.el6.x86_64
lvm2-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
lvm2-libs-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
lvm2-cluster-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
udev-147-2.57.el6    BUILT: Thu Jul 24 08:48:47 CDT 2014
device-mapper-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-libs-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-event-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-event-libs-1.02.90-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
device-mapper-persistent-data-0.3.2-1.el6    BUILT: Fri Apr  4 08:43:06 CDT 2014
cmirror-2.02.111-2.el6    BUILT: Mon Sep  1 06:46:43 CDT 2014
Comment 2 Peter Rajnoha 2014-09-15 10:30:32 UTC 
This seems to be corosync internal error - there's also https://access.redhat.com/solutions/45952 for this issue - so this must have happened at least once before... As such, I'd probably reassign this to corosync component to debug this more.
Comment 4 Christine Caulfield 2014-12-09 13:35:45 UTC 
Created attachment 966250 [details]
Patch to fix

This is the old 'finalise being called in the dispatch' routine race. The solution I chose is to return CS_OK from coroipcc_dispatch_put() if the ipc_channel has been closed. It's been tested and works for me.

I'll post it to the mailing list for review.
Comment 6 Christine Caulfield 2014-12-15 16:18:12 UTC 
commit 83bf77e6f42c2a8b01b1d079e8dc792d9cc7d35d
Author: Christine Caulfield <ccaulfie>
Date:   Mon Dec 15 16:15:10 2014 +0000

    ipcc: Fix ERR_LIBRARY error if finalise called inside dispatch
Comment 7 Christine Caulfield 2015-02-27 16:30:12 UTC 
We're fixing a benign message in an obscure part of the code. I don't see the need to document this BZ
Comment 10 Corey Marthaler 2015-04-22 23:12:27 UTC 
Fixed verified in the latest rpm (corosync-1.4.7-2.el6.x86_64).

I was unable to reproduce these errors after hours of running the test listed in comment #0.
Comment 11 errata-xmlrpc 2015-07-22 07:24:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1389.html
Note You need to log in before you can comment on or make changes to this bug.