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 1859301 - Misleading message in access log for idle timeout
Summary: Misleading message in access log for idle timeout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: 389-ds-base
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.4
Assignee: Jamie Chapman
QA Contact: RHDS QE
Josip Vilicic
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-21 16:22 UTC by mreynolds
Modified: 2021-05-18 15:45 UTC (History)
7 users (show)

Fixed In Version: 389-ds-devel-1.4-8040020201105165416.866effaa
Doc Type: Bug Fix
Doc Text:
.Network connection idle timeouts are no longer reported as resource errors Previously, Directory Server reported a misleading error that a resource was temporarily unavailable when an idle network connection timed out. With this update, the error macro for network connection idle timeouts has been changed from `EAGAIN` to `ETIMEDOUT`, and an accurate error message describing a timeout is written to the Directory Server access logs.
Clone Of:
Environment:
Last Closed: 2021-05-18 15:45:18 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1199 0 None closed Misleading message in access log for idle timeout 2021-02-19 00:40:26 UTC

Description mreynolds 2020-07-21 16:22:23 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/47868

The wording for a connection being closed due to an idle time out is reported in the access log as:
[30/Jul/2014:14:23:22 -0500] conn=204887 op=-1 fd=66 closed error 11 (Resource temporarily unavailable) - T1

I would suggest changing this to clearly state that it is Idle Timeout Exceeded.  The present wording would suggest that there is a resource issue preventing a request from being fulfilled.  

*Note* when logconv.pl consumes a log, it does report these as:
Resource Unavailable:         387
    -  387  (T1) Idle Timeout Exceeded

Comment 3 bsmejkal 2020-11-16 09:10:54 UTC
Changes to log message are present in 389-ds-base-1.4.3.16-1.module+el8.4.0+8740+d5ec8778.x86_64 package.
Marking as Verified:Tested.

Comment 10 sgouvern 2020-11-23 09:48:35 UTC
verified:tested (see comment 3) with build 39-ds-base-1.4.3.16-1.module+el8.4.0+8740+d5ec8778.x86_64
-> marking as VERIFIED

Comment 18 errata-xmlrpc 2021-05-18 15:45:18 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 (389-ds:1.4 bug fix and enhancement update), 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-2021:1835


Note You need to log in before you can comment on or make changes to this bug.