Bug 52481 - Rotatelog.exe crashes Apache after setting 256MB rotatation limit
Summary: Rotatelog.exe crashes Apache after setting 256MB rotatation limit
Status: RESOLVED INVALID
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.2.21
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 07:48 UTC by Benny
Modified: 2018-05-28 17:48 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benny 2012-01-18 07:48:19 UTC
We found that the rotatelog.exe will crash apache give the following settings under httpd.conf

CustomLog '|" "*Apache-Path/bin/rotatelogs.exe" "*Apache-Path/logs/backup/internet_access_%d-%m-%y.log" 86400 256M' combined


The apache hanged after a 15mins stress test with 50 robots.
Comment 1 Jeff Trawick 2012-01-18 16:36:19 UTC
> The apache hanged after a 15mins stress test with 50 robots.

A crash is one thing, a hang is quite another.  Did the error log have anything about a child process exiting and being restarted?

Secondly, what files (and sizes) had been created or written to by rotatelogs at the time the hang was detected?
Comment 2 Eric Covener 2012-01-18 16:54:04 UTC
Isn't the syntax wrong, it has time and size.  So maybe some buffer gets full trying to write to the piped logger that is never able to init enough to read lines.
Comment 3 Jeff Trawick 2012-01-18 17:29:28 UTC
That's right about the syntax; "256M" is taken as the UTC offset.

Benny, please fix the syntax (leave only the rotation time OR the rotation size) and see how that works.
Comment 4 Rainer Jung 2012-01-18 23:44:15 UTC
Just in case there is confusion: Apache 2.2 only allows one of the two rotation rules, either size or time based, as stated by Eric and Jeff.

Apache 2.4 allows to combine both, i.e. what ever happens first will rotate the file. One of the small nice things coming with 2.4. Though this ticket was opened against 2.2, so yes: please fix your config and try again.

If the problem happens again, please see the questions of Jeff in Comment #1.

Rainer
Comment 5 Christophe JAILLET 2018-05-28 17:48:15 UTC
8 years old report and no feedback.

Explanation given for 2.2.x are convincing enough for me. So closing.