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 733049 - corosync crashed during shutdown
Summary: corosync crashed during shutdown
Keywords:
Status: CLOSED DUPLICATE of bug 732698
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-24 15:10 UTC by Jaroslav Kortus
Modified: 2011-08-25 07:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-25 07:22:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
abrt produced crash dump (2.32 MB, application/x-gzip)
2011-08-24 15:11 UTC, Jaroslav Kortus 		no flags Details
corosync-blackbox output after the crash (166.90 KB, application/x-gzip)
2011-08-24 15:12 UTC, Jaroslav Kortus 		no flags Details
View All

Description Jaroslav Kortus 2011-08-24 15:10:48 UTC 
Description of problem:
Corosync crash was detected during cluster-wide shutdown 
Redundant ring feature was in use.

Version-Release number of selected component (if applicable):
corosync-1.4.1-1.el6.x86_64

How reproducible:
quite rarely

Steps to Reproduce:
1. config redundant ring cluster
2. issue service cman stop cluster-wide (via cssh for example)
3.
  
Actual results:
all nodes shut down, one crashed

Expected results:
no crash

Additional info:

Core was generated by `corosync -f'.
Program terminated with signal 6, Aborted.
#0  0x0000003acc232a45 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install cman-3.0.12.1-14.el6.x86_64 glibc-2.12-1.25.el6.x86_64 libgcc-4.4.5-6.el6.x86_64 libibverbs-1.1.4-2.el6.x86_64 librdmacm-1.0.10-2.el6.x86_64 libxml2-2.7.6-1.el6.x86_64 nspr-4.8.7-1.el6.x86_64 nss-3.12.9-9.el6.x86_64 nss-util-3.12.9-1.el6.x86_64 openais-1.1.1-7.el6.x86_64 zlib-1.2.3-25.el6.x86_64
(gdb) bt full
#0  0x0000003acc232a45 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x0000003acc234225 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x0000003acc22b9d5 in __assert_fail () from /lib64/libc.so.6
No symbol table info available.
#3  0x0000003155213aa1 in orf_token_rtr (instance=0x7f71169e7010, orf_token=0x7ffff0a0b5b0, fcc_allowed=0x7ffff0a0afcc) at totemsrp.c:2528

It happened after redundant ring testing, when all nodes rejoined and normal traffic was restored (both rings functional).

Having cpgbench traffic might help reproducing the issue, for me it was like 2/10.
Comment 1 Jaroslav Kortus 2011-08-24 15:11:31 UTC 
Created attachment 519659 [details]
abrt produced crash dump
Comment 2 Jaroslav Kortus 2011-08-24 15:12:08 UTC 
Created attachment 519660 [details]
corosync-blackbox output after the crash
Comment 4 Steven Dake 2011-08-24 18:24:10 UTC 
Jaroslav,

Is this a redundant ring only bug?  (Does this happen on single ring setups in your lab environment?)

Thanks
-steve
Comment 5 Jan Friesse 2011-08-25 07:22:56 UTC 

*** This bug has been marked as a duplicate of bug 732698 ***
Note You need to log in before you can comment on or make changes to this bug.