destr0yr.com
Advanced
Welcome to destr0yr's asylum
Saturday, July 04 2009 @ 04:31 AM PDT
     Google Search   
Google
Web destr0yr.com

     Topics   
Home
cPanel (4/0)
GeekLog (2/0)
Linux (17/0)
Gentoo (6/0)
Personal (2/0)
IT News (1/0)
Windows (15/0)
Ubuntu (3/0)
General News (1/0)

     User Functions   
:

:

Don't have an account yet? Sign up as a New User
Lost your password?

     Older Stories   

Sunday 21-Jan

  • Ubuntu: X: client 2 rejected from local host (0)

  • Tuesday 16-Jan

  • Microsoft CRM: Application Error (8004022c) SOAP Server Application Faulted (0)

  • Thursday 07-Dec

  • Linux: SMTP Mail Relay, Moxy SMTP Proxy, Qmail and Exim (0)

  • Monday 20-Nov

  • Windows: The current time on this computer and the current time (5)

  • Wednesday 15-Nov

  • Apache: [notice] child pid 13628 exit signal File size limit exceeded (25) (0)

  • Monday 06-Nov

  • Ubuntu: tsclient, rdesktop NOT IMPLEMENTED: System pointer message 0x7f00 (1)

  • Thursday 02-Nov

  • cPanel: su: cannot set user id: Resource temporarily unavailable (0)
  • Linux: CentOS and Out of socket memory (0)
  • Ubuntu: My move from Gentoo to Ubuntu (0)

  • Tuesday 24-Oct

  • Windows: AutoEnrollment Event ID 13 (0)


  •    Apache: [notice] child pid 13628 exit signal File size limit exceeded (25)  
     
    Wednesday, November 15 2006 @ 11:43 AM PST
    Contributed by:
    Views:: 6,714

    LinuxIf 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


     

      

     
             


         What's Related   
  • More by destr0yr
  • More from Linux

  •      Story Options   
  • Printable Story Format

  • Trackback

    Trackback URL for this entry: http://www.destr0yr.com/trackback.php/Apache_file_size_limit_exceeded

    No trackback comments for this entry.
    Apache: [notice] child pid 13628 exit signal File size limit exceeded (25) | 0 comments | Create New Account
    The following comments are owned by whomever posted them. This site is not responsible for what they say.