You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Dave Walton <wa...@emusic.com> on 1999/02/26 08:00:11 UTC
os-windows/3971: Apache child process eats up all CPU.
>Number: 3971
>Category: os-windows
>Synopsis: Apache child process eats up all CPU.
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Feb 25 23:10:00 PST 1999
>Last-Modified:
>Originator: walton@emusic.com
>Organization:
apache
>Release: 1.3.4
>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!
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@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! ]