up vote 0 down vote favorite
share [g+] share [fb]

Recently one of my apache installations went down, and after looking around we found out that it's the apache's error_log and access_log size that had reached 2GB. Once we rename the logs and create a new empty ones, everything's ok.

My OS is Redhat 4 and filesystem is ext3. According to wikipedia, a file in ext3 can have up to 16 GB to 2 TB in size. Is it the apache implementation or is it something else that rendered the apache unable to start after 2 GB?

Thank's in advance.

-A

link|improve this question
80% accept rate
You could use logrotate to avoid the logs growing too big. This way you won't have to deal with the consequences. – halp Oct 22 '10 at 13:21
looks useful, thank's! – andreas Nov 18 '10 at 1:35
feedback

1 Answer

up vote 0 down vote accepted

What version of apache are you using? A quick google shows that older versions had a bug regarding logfiles that were 2gb.

link|improve this answer
turned out it's the buggy version of apache, thank's :D – andreas Nov 18 '10 at 1:35
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.