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.

Description of problem:
Dovecot 2.2.5 panics when using director.

Version-Release number of selected component (if applicable):
dovecot-2.2.5-1.el7. 

Steps to Reproduce:
1. Setup 2 instances of Dovecot configured to use Dovecot Director
2. Review Logs

Actual results:
director: Error: Ring SYNC appears to have got lost, resending
director: Panic: file login-connection.c: line 88 (login_host_callback): assertion failed: (strncmp(request->line, "OK\t", 3) == 0)

Expected results:
No assertions/panics.

Additional info:
The problem is also described in http://www.dovecot.org/pipermail/dovecot/2013-September/092384.html including 2 patches.

I tested dovecot 2.2.6, shut down then restarted all dovecot director servers, and the problem appears to have been resolved in that release.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

I saw some recent action on this, and thought I would comment.

While dovecot 2.2.5 seemed to have this issue (Known issue at the time), they fixed it for dovecot 2.2.6.  When I originally tested, this was prior to Centos 7.0

At the time Centos 7.0 was released, it looks like they were using a newer version (2.2.10?), and it was working for us at this time.

Since then, I am no longer using dovecot director and unable to retest, but I have no reason to believe this is still an issue.

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