2.1 Gb size limit??

pk21 · 08-30-2003, 05:59 AM

Hi all.

Ive had my apache logs grown to 2.1 Gb size and apache hangs.
Yesterday i had the same problem with gzip. It was creating a file and stopped at 2.1 Gb.

Is this an apache/gzip problem, or is it a kernel problem???

320mb · 08-30-2003, 09:32 AM

Is /var on it's own partition?? if so, how large is the partition set to??
if not, Why not?? If /var grows too big it will make your OS hang!!
/var should be on it own partition so it won't interfere with /etc, /usr, or the rest of your system!!

michaelk · 08-30-2003, 12:16 PM

It could be the kernel if you do not have large file support included. Do quota limits apply to logs?

Check ulimit -f to find out.

Anyway... you should setup the logs to rotate and delete the old stuff.

pk21 · 08-30-2003, 12:42 PM

I am rotating the logs weekly, the problem is that it just recieves a lot of hits

For the kernel i always use a standard rpm. So it stays easy to upgrade.

pk21 · 08-30-2003, 12:51 PM

by the way, /var is on an own partition, but i put all my access_logs in a users home dir so they can view them. Disk space is not the problem here.

michaelk · 08-30-2003, 02:40 PM

Here is my swag... the kernel probably has large file support but apache might not be compiled to use it.

So the easist method would be to set the logrotate to limit the file size to less than 2 gb. I don't know the best method but you could probably find something by searching the web.