Bug 20160 - Failed logfile writes kill threads, kill performance
Summary: Failed logfile writes kill threads, kill performance
Status: CLOSED DUPLICATE of bug 13511
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0.45
Hardware: All Linux
: P3 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-22 16:19 UTC by Greg Alexander
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Alexander 2003-05-22 16:19:33 UTC
Upon restarting Apache for an upgrade, I noticed that all of the child threads
were going defunct immediately after beginning and load promptly soared to
unheard of levels on our production server.  It turns out our
/var/log/www/access_log was at 2GB so log writes were failing and the child
thread would die out.  /var/log/www/error_log had plenty of space left, but the
child thread did not write there.  It just died.  It had no fatal errors, it
just died.  Do you see the problem?  This is extremely poor error handling --
this is a webserver, not a compiler.  The number one job is to stay on-line and
performing.  Everything else is secondary, including whether or not the log
service is functioning.
Comment 1 Jeff Trawick 2003-05-22 18:39:45 UTC

*** This bug has been marked as a duplicate of 13511 ***