Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 629431

Summary: [abrt] corosync-1.2.7-1.fc13: raise: Process /usr/sbin/corosync was killed by signal 6 (SIGABRT)
Product: [Retired] Corosync Cluster Engine Reporter: Madison Kelly <mkelly>
Component: unknownAssignee: Jan Friesse <jfriesse>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: agk, asalkeld, fdinitto, jfriesse, sdake
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:91248757b97aa5ec1c0b72e15c320f3a125c787f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 13:41:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Madison Kelly 2010-09-02 00:25:46 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: corosync -f
comment: See the steps above. General testing, so above-average start/stop of various cluster related daemons (cman, clvmd mainly).
component: corosync
crash_function: raise
executable: /usr/sbin/corosync
kernel: 2.6.34.6-47.fc13.x86_64
package: corosync-1.2.7-1.fc13
rating: 4
reason: Process /usr/sbin/corosync was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1283386296
uid: 0

How to reproduce
-----
1. Seems to be happening when daemons stop and start. In this case, I tried (and failed) to start clvmd.
2. Earlier, I'd had similar happen while testing fence_node with cman set to start and not start on boot. Didn't seem to matter either way.
3. In some cases, simply stopping a node's cman would cause it to be fenced. It seems that join/leave messages aren't getting through reliably
Comment 1 Madison Kelly 2010-09-02 00:25:48 UTC 
Created an attachment (id=442516)
File: backtrace
Comment 2 Madison Kelly 2010-09-02 01:55:57 UTC 
Here's the output from 'corosync-fplay' on the node that crashed: http://alteeve.com/files/fplay.out
Comment 3 Bug Zapper 2011-05-31 14:45:25 UTC 
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Jan Friesse 2011-06-28 13:41:10 UTC 

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