general/8752: Log files reaching 2GB file size limit causes child processes to seg fault.

[Mike Zimmerman <ta...@spamcop.net>]

>Number:         8752
>Category:       general
>Synopsis:       Log files reaching 2GB file size limit causes child processes to seg fault.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Nov 13 23:20:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     tarmon@spamcop.net
>Release:        1.3.20
>Organization:
apache
>Environment:
Linux 2.4.9 
ext2 fs
>Description:
On a high load server I run, its been observed that a log file reaching the ext2 filesize limit of 2GB causes an unexpected exit on the part of the child process during its attempt to log the access. Once the connection is made by the client and the request sent, the connection terminates without any response. 
>How-To-Repeat:
Load a log file with 2GB of data on a Linux ext2 based system and attempt a page retrieval. 
>Fix:

>Release-Note:
>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 make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]
 
 

Re: general/8752: Log files reaching 2GB file size limit causes child processes to seg fault.

[Mike Zimmerman <ta...@spamcop.net>]

For further reference, a "good" request will output the full response 
before terminating (the child process still segfaults) in the case of the 
transfer log being full, but a "bad" request (404, what have you) 
terminates if the error log is full without sending data. Either way, the 
child still dies.

At 07:20 AM 11/14/2001 +0000, you wrote:
>Thank you very much for your problem report.
>It has the internal identification `general/8752'.
>The individual assigned to look at your
>report is: apache.
>
> >Category:       general
> >Responsible:    apache
> >Synopsis:       Log files reaching 2GB file size limit causes child 
> processes to seg fault.
> >Arrival-Date:   Tue Nov 13 23:20:00 PST 2001