Bug 636774
| Summary: | [abrt] corosync-1.2.8-1.fc13: raise: Process /usr/sbin/corosync was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Corosync Cluster Engine | Reporter: | Lorenzo Sartoratti <lorenzo.sartoratti> | ||||||
| Component: | unknown | Assignee: | Jan Friesse <jfriesse> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 1.2 | CC: | agk, asalkeld, fdinitto, jfriesse, sdake | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:011b02d62eff11adfd6b8085b5dcf0ce27c6db70 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-06-28 13:41:20 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
Lorenzo Sartoratti
2010-09-23 08:33:05 UTC
Created attachment 449149 [details]
File: backtrace
Thanks for filing the bugzilla. Could you run corosync-fplay on the crashed node? This will playback the flight record. Are you running a two node cluster? If you have a "FAILED TO RECEIVE" condition in the fplay, that would indicate there is some logic error remaining in the failed to receive handling. Please note that Bug 619496 should offer relief from this problem. Regards -steve Likely a dup of Bug 636583. Created attachment 449282 [details]
Fplay of the coredump
I've attached the fplay requested
Tomorrow I will test my network switches
I'm running a four node cluster Same as 636583 I think we can consider the bug closed Thank for the support! Lorenzo Sartoratti 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 *** This bug has been marked as a duplicate of bug 636583 *** |