Received: (qmail 3720 invoked by uid 2012); 26 Feb 1999 07:00:11 -0000
Message-Id: <19990226070011.3719.qmail@hyperreal.org>
Date: 26 Feb 1999 07:00:11 -0000
From: Dave Walton <walton@emusic.com>
Reply-To: walton@emusic.com
To: apbugs@hyperreal.org
Subject: Apache child process eats up all CPU.
X-Send-Pr-Version: 3.2

>Number:         3971
>Category:       os-windows
>Synopsis:       Apache child process eats up all CPU.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Feb 25 23:10:00 PST 1999
>Closed-Date:    Sun Oct 01 13:24:35 PDT 2000
>Last-Modified:  Sun Oct 01 13:24:35 PDT 2000
>Originator:     walton@emusic.com
>Release:        1.3.4
>Organization:
>Environment:
Windows NT Server 4.0 sp3
>Description:
Apache is running on a lightly hit (~200 hits/hr) server running Perl CGI 
scripts, some of which output large files (several MB).
Some time after starting, generally within an hour, the Apache child process 
will suddenly start using all available CPU.  The child continues handling
requests normally, but the entire system is bogged down.  When the child in 
this state reaches MaxRequestsPerChild, it hangs rather than exiting.  Also, 
attempting to shut down Apache results in this entry in the error.log, after
a long delay:
D:\Apache\Apache.exe: [Thu Feb 25 22:18:00 1999] [error] forcing termination of child #0 (handle 140)
>How-To-Repeat:
No idea how to repeat it.
>Fix:
Fix it?  I can't tell what's causing it!
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: wrowe
State-Changed-When: Sun Oct  1 13:24:35 PDT 2000
State-Changed-Why:

This was freqently observed in older versions of the Apache
server for Win32.  Please upgrade to the latest version of
Apache (1.3.12) to help resolve your issue.
Thanks for your report and interest in the Apache project.

>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]