>Number: 5790 >Category: general >Synopsis: Too many open files error via CGI (may be mod_cgi problem) >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Feb 21 09:50:00 PST 2000 >Closed-Date: >Last-Modified: >Originator: [EMAIL PROTECTED] >Release: 1.3.11 >Organization: apache >Environment: Linux, RedHat 6.1 (out of box install with IP aliasing patch), gcc latest version >Description: Until i installed 1.3.11, I was running 1.3.9 (both with mod_ssl) and didn't have this problem with identical software. After running for several hours, the system starts generating "too many open files" errors and must be manually restarted. I thought this might be a system instability, but have tracked it back to the install date of 1.3.11. It's happened daily since I installed that release.
I run a number of perl daemons that interact with Apache CGIs, and I'm wondering if the CGI perl is not having its filehandles properly closed on exit? I'm not sure how to better document this. I'm reverting to 1.3.9 right away to solve the problem. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
