DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29243>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29243 Logs hitting max file size limit cause server to fail without reporting anything useful... Summary: Logs hitting max file size limit cause server to fail without reporting anything useful... Product: Apache httpd-2.0 Version: 2.0.49 Platform: Sun OS/Version: Solaris Status: NEW Severity: Normal Priority: Other Component: mod_log_config AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] When this happens (truss output) open("/usr/local/apache2/logs/xml.whatsonwhen.com-access_log", O_WRONLY|O_APPEND|O_CREAT, 0666) Err#79 EOVERFLOW write(21, " [ T h u M a y 2 7 ".., 167) = 167 write(2, " U n a b l e t o o p".., 20) = 20 the system reports... Unable to open logs It doesn't say why; it doesn't say which log, nor does it give you any idea of what's actually taking place. Can that be modified to tell you both which log failed, and what the status code of the open operation provided by the OS was? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
