Received: (qmail 29236 invoked by uid 501); 1 Nov 2000 15:57:35 -0000 Message-Id: <20001101155733.29229.qmail@locus.apache.org> Date: 1 Nov 2000 15:57:33 -0000 From: Philip Rohanna Reply-To: prohanna@cnavsystems.com To: submit@bugz.apache.org Subject: runaway libhttpd.ep process X-Send-Pr-Version: 3.110 >Number: 6779 >Category: mod_so >Synopsis: runaway libhttpd.ep process >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Nov 01 08:00:01 PST 2000 >Closed-Date: >Last-Modified: >Originator: prohanna@cnavsystems.com >Release: 1.3.14 >Organization: apache >Environment: uname -a: Linux delldev.cnavsystems.com 2.2.14-6.1.1smp #1 SMP Thu Apr 13 19:55:55 EDT 2000 i686 unknown Linux-redhat 6.2, gcc 2.91.66 on a dual processor dell poweredge server we are also running coldfusion 4.5 and JRun 3.0 as modules into apache. >Description: every once in a while we get runaway libhttpd.ep processes that will eventually eat up all cpu time on the server. This happened quite often with apache 1.3.12 but disappeared for a while once upgrading to version 1.3.14. In the past couple of days though it has resurfaced. The problem also occurs on a pair of laptops running the same software configuration. >How-To-Repeat: It happens sporadically, and we're still trying to repeat it or find out if it is a specific module, mod_jrun.so or mod_coldfusion.so or mod so in general. Suggestions on how we could track it down would be helpful. >Fix: wish I did, right now we just do a restart and it clears them out. >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]