#47868 Misleading message in access log for idle timeout
Closed: wontfix 3 years ago by spichugi. Opened 9 years ago by jamespfinn.

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


Metadata Update from @jamespfinn:
- Issue set to the milestone: 1.4 backlog

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: 1.4.4 (was: 1.4 backlog)

3 years ago

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1859301

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1199

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata