Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1614239

Summary: dovecot Panic: file mail-index-sync-update.c: line 1013
Product: Red Hat Enterprise Linux 7 Reporter: Eugen <gman86>
Component: dovecotAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5-Alt   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-07 18:31:13 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:
Attachments:
Description Flags
dovecot log outout none

Description Eugen 2018-08-09 08:50:12 UTC
Created attachment 1474608 [details]
dovecot log outout

Description of problem:
An email came to several users but one user didn't receive it and we got 'Mail delivery failed' message.

As I see from the log below, there were broken index file.
Then dovecot repaired that index and we got the error:
Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid
== 0)
Please, see the attached logs.

It is supposed that Dovecot had to repair index file and put the email in
/mnt/mail//user05/Maildir/.Queue.A_Sup.group_05/ directory but it didn't.
Is there something wrong with Dovecot?

Thanks.

-------

Version-Release number of selected component (if applicable):
Operating system: Linux Centos 7   3.10.0-862.3.2.el7.x86_64 #1 SMP Mon May 21 23:36:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

rpm -qa |grep dovecot
dovecot-pigeonhole-2.2.10-8.el7.x86_64
dovecot-2.2.10-8.el7.x86_64


How reproducible:
It was one-time error and it has not reappeared yet.
At the moment the user receives emails successfully  (in .Queue.A_Sup.group_05 as well).

Steps to Reproduce:
no STR

Actual results:
an email isn't put in the folder and "mail delivery failed" letter is generated

Expected results:
an email is put in the folder

Additional info:
I have written to Dovecot mailing list here:  https://dovecot.org/pipermail/dovecot/2018-August/112588.html
and received the answer that this issue was fixed in newer versions.

Comment 2 Michal Hlavinka 2020-02-07 18:31:13 UTC
dovecot was recently updated to a version newer than that was mentioned upstream as containing the fix. closing. If you still see this issue, try to reproduce with rhel8 version and if still present, open new bug.