Bug 885620
Summary: | imapd segfaults while stripping attachment using Horde 4/IMP 5 application | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Anant <athavale.anant> | ||||||||
Component: | cyrus-imapd | Assignee: | Pavel Šimerda (pavlix) <psimerda> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Radka Brychtova <rskvaril> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 6.3 | CC: | athavale.anant, psimerda, psklenar, rskvaril, thozza | ||||||||
Target Milestone: | rc | Keywords: | Patch | ||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | cyrus-imapd-2.3.16-14.el6 | Doc Type: | If docs needed, set a value | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2017-03-21 11:24:35 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 1356054, 1359261 | ||||||||||
Attachments: |
|
Description
Anant
2012-12-10 09:02:10 UTC
Could you obtain core file and attach it to this bug (gziped) ? Thanks Created attachment 663892 [details]
Coredump file after crash
As requested attaching the core file.
Created attachment 663893 [details]
Messages file extract for the crash
Created attachment 663894 [details]
mailog extract for the same crash
Please try this package: http://mhlavink.fedorapeople.org/bz885620/ It could fix this issue and if not, it has some extra assert checks. So if it does not work, attach new core file (no need for logs). Thanks (In reply to comment #7) > Please try this package: > http://mhlavink.fedorapeople.org/bz885620/ > It could fix this issue and if not, it has some extra assert checks. So if > it does not work, attach new core file (no need for logs). Thanks 1. The server is in production. 2. Our earlier version of Horde 3/IMP 4 has no problems with the current version of Cyrus-imapd, problem comes when we use with Horde 4/IMP 5. Please let me know, If I upgrade the cyrus-imap, will it stop and restart cyrus-imapd? In that case, I need to take some downtime. Please let me know, possible impacts. Regards, Anant. Yes, every time you update some daemon, it's restarted. Despite the probability is extremely low, changes in that packages can have negative side effects. So it'd be better to test it in test environment, not the production one, if it's possible. The best option would be to install cyrus-imapd (original version) on different machine, copy mail archive and try to reproduce. Then update to new packages and try to reproduce again. If you don't know how to reproduce this, you can enable IMAP raw log for some affected user: mkdir /var/lib/imap/log/<username> chown cyrus /var/lib/imap/log/<username> this will enable imap logging (only) for <username> after problem shows again, log file should contain IMAP communication. You can try to reproduce the problem by sending the IMAP commands from the log using netcat, that way you should be able to reproduce it without the need of setting up the horde webmail. OK. I will try. Need some time to setup another machine for testing purpose. -Anant. Yesterday, I setup a new server with RHEL 6.3. Copied few mailboxes (copied /var/spool/imap/user/x and y) and created respective mailboxes (cm user.x and cm.user.y) and reconstrctured those mailboxes. Tried to strip the attachments. I am not facing any problem. i.e. I am unable to reproduce the problem. One more thing, I will try before giving up is "disable logging" and try. ie. removing the /var/lib/imap/log/<username> directory. Becuase, this seems to be now the only difference. BTW, let me give a history. Earlier our cyrus was running on RHEL 5.3 having cyrus-imapd-2.3.7-2.el5 with EMC storage. /var/lib/imap was on local OS disk, whereas /var/spool/imap came from EMC storage (as FC disk). We migrated to RHEL 6.3 having cyrus-imapd-2.3.16-6.el6-2.5 with NetApp Storage. Here both /var/lib/imap and /var/spool/imap come from NetApp Storage (as FC disk). I did follow the steps writeen in README.HOWTO-recover-mailboxes.db, so that all mailboxes are recreated. This I did, since, it was mentioned in cyrus documentation (Upgrading from Previous Versions) that, Upgrading from 2.3.3 or later, Due to byte alignment issues in cyrus.index, all mailboxes will have to be reconstructed. After this, I released it to the users. Same old Horde version is working fine, but in new version, I am getting problem. But, right now, I am unable to reproduce it on another RHEL 6.3 server with local disk based cyrus-imap folders. Any other hints to reproduce the problem? Regards, Anant. Now, I am able to reproduce the problem on another server using NetApp storage. So, if I use local disk, problem does not come, where as, if I use NetApp OnTap 8.1 FC disk, the problem is seen. I am yet to apply the rpm's given. I will wait for a day, since, I have reported the same in cyrus-info mailing list under this thread http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=54436 Regards, anant. As I am not any response on other mailing list, I decided to ahead with rpms provided. Today, I upgraded to those rpms on a test system. Though, there is no coredump, but, functionality is not working. i.e. stripping attachment does not work. Following is the log entry. Jan 3 10:40:09 imapserver imap[11495]: Fatal error: Internal error: assertion failed: mailbox.c: 1499: !message_guid_isnull(&record->guid) Jan 3 10:40:09 imapserver master[11487]: process 11495 exited, status 75 Jan 3 10:40:09 imapserver master[11487]: service imap pid 11495 in BUSY state: terminated abnormally -anant. This assert error looks like cyrus-imapd bug: https://bugzilla.cyrusimap.org/show_bug.cgi?id=3754 I'll backport that fix and prepare new test package. New test packages can be found here: http://mhlavink.fedorapeople.org/bz885620/ I installed the new test packages. Now, rpm -qa shows rpm -qa |grep cyrus-imap cyrus-imapd-debuginfo-2.3.16-10.el6.0.bz885620.1.x86_64 cyrus-imapd-devel-2.3.16-10.el6.0.bz885620.1.x86_64 cyrus-imapd-2.3.16-10.el6.0.bz885620.1.x86_64 cyrus-imapd-utils-2.3.16-10.el6.0.bz885620.1.x86_64 But, I see the same error as I saw in the previous fix. Jan 10 12:14:19 imapserver imap[30530]: open: user asa opened INBOX Jan 10 12:14:19 imapserver imap[30530]: Fatal error: Internal error: assertion failed: mailbox.c: 1499: !message_guid_isnull(&record->guid) Jan 10 12:14:19 imapserver master[30526]: process 30530 exited, status 75 Jan 10 12:14:19 imapserver master[30526]: service imap pid 30530 in BUSY state: terminated abnormally OK. Apart from this, I have also tried the following 1. Compiled latest version of Cyrus-IMAPD 2.4.17 and found it working without any issue. 2. Used the src.rpm provided at invoca.ch and used rebuild and tested. stripping attachment works fine. I just thought to share this inputs with you. BTW, are there no 2.4 versions of RPM with RHEL 6? Regards, Anant. Any updates for this from RedHat Team? I am unable to release the new version due to this problem. I request you to provide support as I still believe that, RPMs provided by RHEL will be very stable. -anant. I don't see obvious reason why it fails now. Could you get core file for this new test package? Also, the best solution would be if you could prepare reproducer for this - configuration needed on fresh installation and some crashing mailbox. (In reply to comment #18) > I request you to provide support as ... Beware, that bugzilla is bug tracking tool, nothing more. For support you should open support case at https://access.redhat.com/home Support case has bigger priority and guaranteed response time, which bugzilla has not. There is no CORE file getting generated. Only error is seen in the log. Were you able to create reproducer for this? I am always able to reproduce. What I can definitely say is, if the disk used for IMAP is on local disk, no problems. If the disk used for IMAP is from SAN, it is a problem. Using NetApp SAN. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. As I was not able to reproduce this bug, I did just Sanity testing. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0742.html |