Red Hat Bugzilla – Bug 479463
Bad file descriptor: apr_file_close(child input)
Last modified: 2012-07-04 10:25:26 EDT
Description of problem:
I have a cluster of two RHEL 5.2 machines running Apache, in which I've configured a small perl script to be invoked as an input filter (mod_ext_filter) on access to a certain URL.
Now, this is working fine, except for the message that is logged to the Apache error log every time the script is invoked.
This seems to be a known bug (#9644 in the Apache bugzilla) which is already fixed in later versions of Apache. Any chance of having this fix backported to RHEL in the near future?
Steps to Reproduce:
1. Configure Apache to use an input filter with mod_ext_filter;
2. Go into the URL that triggers the filter;
3. Look at the error log.
An error containing the message "Bad file descriptor: apr_file_close(child input)" is logged every time.
BTW, the referred bug in the Apache bugzilla refers to Apache 2.0. I'm seeing this in the RHEL 5.2' Apache (2.2).
The referenced bug was fixed back in 2.0.37.
Can you give an exact mod_ext_filter configuration which reproduces this?
The following virtual-host uses SSL.
ExtFilterDefine my-filter mode=input cmd="/etc/httpd/scripts/my-filter.pl" enableenv=my-auth
SetEnvIfNoCase Request_Method "POST" my-post
SetEnvIfNoCase Request_URI "/object\.dll$" my-post my-auth
The location "/path/" is later defined as a proxy with ProxyPass and ProxyPassReverse.
Sorry for the bug spam, but I have something else to add. This doesn't seem to always be reproducible with Internet Explorer 7 as the client. But with Firefox it is.
As far as user-agent specific configuration goes, I'm using the RHEL defaults, which means this is the only bit that explicitely matches MSIE7:
SSLProtocol all -SSLv2
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.