Bug 289081
| Summary: | Kernel error for cyrus: *** glibc detected *** lmtpd: double free or corruption (out): 0x00002aaaacdeaa10 *** | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ali Nebi <anebi> | ||||
| Component: | cyrus-imapd | Assignee: | Tomas Janousek <tjanouse> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6 | CC: | anebi, triage | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-04-04 10:59:28 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
Ali Nebi
2007-09-13 11:25:25 UTC
Created attachment 194521 [details]
Kernel errors for cyrus
Sorry for the late reply. I tried to reproduce this but did not succeed. I applied a few patches and made a new build, so you can try this one: http://koji.fedoraproject.org/koji/taskinfo?taskID=170944 I don't think it will help though. I'd be glad if you can provide me a gdb backtrace. If you're able to connect to the server via IMAP/POP3 (ie. the crash occurs only after you do something or close the connection), use netstat -tpn to find the process you're connected to and attach gdb using `gdb /usr/lib/cyrus-imapd/imapd pid'. Then try to reproduce the crash. Don't forget to install the debuginfo package. Oh, I forgot: After attaching gdb, type 'c' to resume the running program. And the backtrace can be obtained using "bt full". Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers Sorry for too late reply. I was forgot for this bug. I received the message in my e-mail and remember for this bug report. We moved our systems to CentOS 5.1 and we can't reproduce this bug again. I suppose this bug is solved in the lastest release and suggest to close this bug report. Best regards, Ali Nebi! Sorry for too late reply. I was forgot for this bug. I received the message in my e-mail and remember for this bug report. We moved our systems to CentOS 5.1 and we can't reproduce this bug again. I suppose this bug is solved in the lastest release and suggest to close this bug report. Best regards, Ali Nebi! |