Received: (qmail 9542 invoked by uid 501); 9 Oct 2001 00:54:55 -0000 Message-Id: <20011009005455.9540.qmail@apache.org> Date: 9 Oct 2001 00:54:55 -0000 From: Cameron Gregory Reply-To: cameron@bloke.com To: submit@bugz.apache.org Subject: SIGXFSZ when log file > 2gb X-Send-Pr-Version: 3.110 >Number: 8493 >Category: mod_log-any >Synopsis: SIGXFSZ when log file > 2gb >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon Oct 08 18:00:00 PDT 2001 >Closed-Date: Wed Oct 10 18:36:08 PDT 2001 >Last-Modified: Wed Oct 10 19:00:00 PDT 2001 >Originator: cameron@bloke.com >Release: 1.3.19 >Organization: >Environment: red hat 7.1, rpm from redhat .. SPM machine not really important. >Description: all the kids die writing to the log file when it reaches 2gb this is because the kids are getting SIGXFSZ and default action is to die. [Thu Oct 4 12:29:08 2001] [notice] child pid 13456 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13444 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13414 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13406 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13404 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13399 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13386 exit signal File size limit exceeded (25) [Thu Oct 4 12:29:08 2001] [notice] child pid 13379 exit signal File size limit exceeded (25) one pertentent point was this was a TransferLog /www/logs/xxx.log entry inside a in the end caused my machine to crash quite quickly, but that is not really because of apache. >How-To-Repeat: make a big log file and log to it. >Fix: force a rotate? >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Wed Oct 10 18:36:08 PDT 2001 State-Changed-Why: Apache can not "force a rotate" since it is up to the admin to configure how and when they want logs rotated. It is also not the case that all systems have such 2 gig file size limits. And Apache can not magically reopen logfiles without a server restart due to the server architecture. It is really up to the admin to make sure that they have some type of log rotation in place so that log files don't get too big. There is no "proper" way Apache can handle this condition; it is a fatal error on the part of the admin to let a logfile hit maximum filesize limit... From: cameron gregory To: marc@apache.org Cc: apbugs@apache.org Subject: Re: mod_log-any/8493: SIGXFSZ when log file > 2gb Date: Wed, 10 Oct 2001 21:59:12 -0400 G'Day Marc, No worries, and I agree it's mostly an admin problem, but perhaps the a good addition is to catch sigfilesz and write a warning, but don't exit the child, at least the machine wouldn't trash so much under this condition (we currently would fill the log file to 2gig in 3-5 days, so it perceivable that this could happen in less than one day). [I was suprised that r/h had the 2gig limit...] thanks, cameron marc@apache.org wrote: > > [In order for any reply to be added to the PR database, you need] > [to include 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! ] > > Synopsis: SIGXFSZ when log file > 2gb > > State-Changed-From-To: open-closed > State-Changed-By: marc > State-Changed-When: Wed Oct 10 18:36:08 PDT 2001 > State-Changed-Why: > Apache can not "force a rotate" since it is up to the admin to configure how and when they want logs rotated. It is also not the case that all systems have such 2 gig file size limits. > And Apache can not magically reopen logfiles without a server restart due to the server architecture. > > It is really up to the admin to make sure that they have some type of log rotation in place so that log files don't get too big. There is no "proper" way Apache can handle this condition; it is a fatal error on the part of the admin to let a logfile hit maximum filesize limit... -- - I get a lot of email, please include previous message in reply. -------------------------------------------------------------- Cameron Gregory - http://www.bloke.com/ - cameron@bloke.com http://www.flamingtext.com/ - Awesome online image generation OutSource Laboratories 732-544-5001 x124 - cameron@olabs.com >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]