On one server, where I have a custom directory where all the Apache (httpd) error and access logs are written, one set per virtualhost, I noticed the folder had grown to multiple gigabytes in size (found using
du -h --max-depth=1)—in this situation, there's a handy utility on pretty much every Linux/UNIX system called logrotate that is made to help ensure log files don't grow too large. It periodically copies and optionally compresses the log files and deletes old logs, daily, monthly, or on other schedules.
For this server, to quickly fix the problem of growing-too-large log files, I added a file 'httpd-custom' at
/etc/logrotate.d/httpd-custom, with the following contents:
rotate 5<br />
size 25M<br />
/sbin/service httpd reload > /dev/null 2>/dev/null || true<br />
- rotate 5: tells logrotate to only keep the past five rotated log files (it will delete the oldest one after it has run more than 5 times).
- size 25M: tells logrotate to rotate the log after it's grown to 25+ MB.
- compress: tells logrotate to use gzip (with the -9/most compression option) to compress the log file—this saves a TON of disk space for large log files.
- If logrotate is deleting all rotated logs, and not just compressing/moving them, you probably need to add the 'rotate X' command, where X is the number of rotated logfiles to keep.
Read much, much more here: logrotate man page.