Bug 735287 - corosync crashes sometimes on takeover
Summary: corosync crashes sometimes on takeover
Status: CLOSED DUPLICATE of bug 671575
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync
Version: 6.1
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Steven Dake
QA Contact: Cluster QE
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-02 07:32 UTC by Robert
Modified: 2016-04-26 13:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-02 17:04:22 UTC

Attachments (Terms of Use)
output of corosync-fplay (523.20 KB, text/plain)
2011-09-02 07:32 UTC, Robert
no flags Details
one of the crash dumps (matches the corosync-fplay) (39 bytes, text/plain)
2011-09-02 08:03 UTC, Robert
no flags Details

Description Robert 2011-09-02 07:32:51 UTC
Created attachment 521159 [details]
output of corosync-fplay

Description of problem:

I'm testing a cluster setup with rhel 6.1 and I've a problem which stops me from deploying that cluster with rhel in production. Sometimes when I reboot a node with active services the corosync on the node which should to the take over crashes. It can work for some reboots and than suddenly I run into the problem. The 2 nodes are running as Vmware instances on different hosts, across 2 data centers (> 10 km distance).

Version-Release number of selected component (if applicable):


How reproducible:

reboot many times and sometimes it happens.

Actual results:

crash of corosync and 100% cpu for pacemaker

Expected results:

the Cluster should swith correctly

Additional info:

see attachments

Comment 2 Robert 2011-09-02 08:03:37 UTC
Created attachment 521165 [details]
one of the crash dumps (matches the corosync-fplay)

Comment 3 Steven Dake 2011-09-02 17:04:22 UTC

*** This bug has been marked as a duplicate of bug 671575 ***

Comment 4 Steven Dake 2011-09-02 17:06:53 UTC

Generally I believe your deployment would need an architecture review before being processed by sales.  Also, bugs should come in from support not directly from customers.

Best wishes

Note You need to log in before you can comment on or make changes to this bug.