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 1570283 - Dovecot should use portrelease to avoid port conflicts with NFSv4 mounts
Summary: Dovecot should use portrelease to avoid port conflicts with NFSv4 mounts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dovecot
Version: 7.5
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Evgeny Fedin
URL:
Whiteboard:
Depends On: 1570282
Blocks: 1716965
TreeView+ depends on / blocked
 
Reported: 2018-04-21 14:04 UTC by Robert Scheck
Modified: 2023-09-07 19:07 UTC (History)
4 users (show)

Fixed In Version: dovecot-2.2.36-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:45:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1062 0 None None None 2020-03-31 19:46:02 UTC

Description Robert Scheck 2018-04-21 14:04:03 UTC 
Description of problem:
After rebooting a system I found a non-working dovecot. Some investigation
lead me to this:

[root@tux ~]# netstat -alpen | grep :993
tcp     0    0 192.168.0.29:993     192.168.2.30:2049    TIME_WAIT  0    0    -
[root@tux ~]# 

After umounting my NFSv4 share, I was able to restart dovecot successfully.

Version-Release number of selected component (if applicable):
dovecot-2.2.10-8.el7.x86_64

How reproducible:
Not always, requires some "bad" random after reboot.

Actual results:
Dovecot's ports 993/tcp and 995/tcp might conflicts with NFSv4 mounts.

Expected results:
$ cat /etc/portreserve/dovecot
993/tcp
995/tcp
$ 

$ cat /usr/lib/systemd/system/dovecot.service
…
ExecStartPre=-/sbin/portrelease dovecot
…
$ 

Additional info:
Unfortunately portreserve doesn't seem to work as documented, thus that
issue needs to be addressed first, see bug #1570282 for details.
Comment 2 Robert Scheck 2019-03-22 12:57:45 UTC 
Cross-filed case 02344539 in the Red Hat customer portal.
Comment 4 Ondrej Vasik 2019-06-26 07:46:36 UTC 
I don't think this can be fixed on dovecot side - and fixing portreserve should fix this. SUNRPC has known disadvantage of randomly assigning rpc ports 665-1023 (well - not completely randomly - it is something like 6XX+pid which results in regular issues with 993/995 ports on certain systems) - thus when NFSv4 is in-place and it has not static ports assigned, it can consume randomly 993/995 port. Solution can be to have static port assigned to nfsv4 or other rpc services. So this can be at least a workaround.
Comment 5 Michal Hlavinka 2019-06-26 08:40:59 UTC 
Small correction, the previous comment should probably go to the portreserve bug.
ATM dovecot does not use portreserve, that's why this bug is here, but it will require portreserve to work (that's the other bug).
On the other hand, looking at man bootup, portreserve contains After=sockets.target, Before=basic.target which means that if you enable socket activation for dovecot, those ports should be already reserved by systemd even before portreserve is started.
Comment 9 errata-xmlrpc 2020-03-31 19:45:54 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/RHSA-2020:1062
Note You need to log in before you can comment on or make changes to this bug.