httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 13511] New: - Apache misbehaves if log files can't be written
Date Thu, 10 Oct 2002 19:38:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13511>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13511

Apache misbehaves if log files can't be written

           Summary: Apache misbehaves if log files can't be written
           Product: Apache httpd-2.0
           Version: 2.0.32
          Platform: All
               URL: no url available
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: ddyer@real-me.net


If the error log can't be written, it appears that any process that
tries to write to the error log is quietly terminated.   This can 
cause serious errors where no serious errors existed.

Suggest 1) "quiet termination" should be noisier, to attract attention.
2) there should be some sort of overall status information that could be
routinely monitored for such "alarm" conditions as the inability to make
log file entries.

Here are some details from an event that led to this report.  The "symptom"
was that some scripted emails arrived blank.  There was no other indication
of a problem, but once someone complained about the blank emails, It was 
noticed that the error_log was 2GB in size and had stopped growing due to 
maximum file size.  The web site was otherwise operating normally, except
that errors weren't being logged.

Further investigation showed that a CGI subprocess invlolved in sending the 
email was routinely emitting a warning message, which was logged, and the
inability to log the warning caused the process to terminate.  Since the main 
thread emitting HTML didn't fail, the user's screen didn't indicate any 
problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message