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 1432336 - doveadm backup: assert-crash when syncing mailbox deletion
Summary: doveadm backup: assert-crash when syncing mailbox deletion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dovecot
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: David Jež
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-15 07:22 UTC by Rob Garth
Modified: 2018-10-30 10:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:54:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3182 0 None None None 2018-10-30 10:55:11 UTC

Description Rob Garth 2017-03-15 07:22:13 UTC 
Description of problem:

dsync panics when syncing a mailbox deletion. It was fixed up stream in 2.22.11 https://github.com/dovecot/core/commit/aea7f72aa97f0f3c2e181ab3ae432f2e22148f3b


Version-Release number of selected component (if applicable): 2.22.10-7

How reproducible: On an affected mailbox dsync will panic everytime

Actual results:

dsync(******): Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain->no_backup_overwrite)
dsync(******): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x6a06e) [0x7f47a81cc06e] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f47a81cc0da] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f47a818452c] -> doveadm(dsync_brain_mailbox_tree_sync_change+0x442) [0x7f47a8df9262] -> doveadm(dsync_brain_recv_mailbox_tree_deletes+0x13b) [0x7f47a8df8d6b] -> doveadm(dsync_brain_run+0x4e3) [0x7f47a8df60a3] -> doveadm(+0x2e894) [0x7f47a8df3894] -> doveadm(+0x15b7b) [0x7f47a8ddab7b] -> doveadm(doveadm_mail_try_run+0x26c) [0x7f47a8ddb92c] -> doveadm(main+0x414) [0x7f47a8dda6d4] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f47a7dc2b35] -> doveadm(+0x15925) [0x7f47a8dda925]


Expected results: Backup of mailbox would complete cleanly


Additional info:

The fix upstream in 2.22.11 can be seen here: https://github.com/dovecot/core/commit/aea7f72aa97f0f3c2e181ab3ae432f2e22148f3b
Comment 2 Michal Hlavinka 2017-03-16 16:14:47 UTC 
Thanks for reporting this. Could you describe configuration and procedure how to reproduce this, so our QA team can create a test for this to make sure the fix is correct and it won't happen in the future?

Also, did you test the linked commit or it was just suggested to you that it should fix this problem?

Thanks
Comment 3 Rob Garth 2017-03-22 23:59:17 UTC 
I backported 2.22.11 here: https://copr.fedorainfracloud.org/coprs/rgarth/

The bug is fixed in this version. But I cannot confirm that this particular commit was the fix.

We have a nightly backup of all of our mailboxes on one system. It is hard to trace where the actual problem is happening, but it looks like if a user deletes an mbox, that night the dovadm dsync will crash on that user.
Comment 4 Rob Garth 2017-03-23 20:56:17 UTC 
I will setup another dovecot box, not in production and recreate the problem next week.

But I believe it should be as simple as running a dovadm backup of a MAILDIR, deleting a folder in that MAILDIR and then trying to run a second backup.
Comment 8 errata-xmlrpc 2018-10-30 10:54:44 UTC 
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://access.redhat.com/errata/RHBA-2018:3182
Note You need to log in before you can comment on or make changes to this bug.