| |
Wednesday, November 15 2006 @ 11:43 AM PST Contributed by: Views:: 6,714 |
|
If you see the following in your apache error log (typically in /var/log/httpd/error_log or /usr/local/apache/logs/error_log on RH systems), you have a problem.
[notice] child pid 13628 exit signal File size limit exceeded (25)
[notice] child pid 13629 exit signal File size limit exceeded (25)
[notice] child pid 13631 exit signal File size limit exceeded (25)
[notice] child pid 13632 exit signal File size limit exceeded (25)
Apache seems to croak on files larger than 2GB. To determine which file(s) are causing the issue, try the following command:
find / -size +1000000000c
This command will almost certainly take quite some time and will cause significant load on the system. I'd suggest changing the search path ("/") to the directory your apache/logs exist. Ultimately the issue is resolved by killing the file. However, it would be wise to take notice of the effective permissions and ownership before doing so. Alternatively, you could run a command such as the following which will keep the the permissions intact:
# > /usr/local/apache/domlogs/foo.com
|
|
|
| |
|
|
|
|
|
Trackback URL for this entry: http://www.destr0yr.com/trackback.php/Apache_file_size_limit_exceeded
No trackback comments for this entry.