PHP Fatal error: Out of memory (Apache crash)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • solinem
    New Member
    • Sep 2008
    • 2

    PHP Fatal error: Out of memory (Apache crash)

    Hi:
    I am trying to find a solution for an error that consequentially leads to Apache Server crash.
    Following is the message, as seen in the error.log file:
    PHP Fatal error: Out of memory (allocated 786432) (tried to allocate 32768 bytes)

    SERVER CHARACTERISTICS :

    * Windows 2008 Enterprise Server
    * PHP 5.2.6
    * Apache/2.2.4 (Win32) DAV/2 mod_ssl/2.2.4 OpenSSL/0.9.8e
    * RAM=8gb,

    PHP SERVER PARAMETERS:

    * max_execution_t ime = 720
    * max_input_time = 360
    * memory_limit = 5120 MB

    After a few messages like this, the server ends with the message:
    [notice] Parent: child process exited with status 255 -- Restarting.

    Whenever it happens, I don't see a substantial rise in memory usage (well under the 5GB established in the configuration)
    I think part of the problem is originated because the server is not releasing memory, and the data is adding-up.
    It is surely a misconfiguratio n of my server
    I have searched everywhere but didn't found a satisfying solution.

    Thanks for your help.
  • MarkoKlacar
    Recognized Expert Contributor
    • Aug 2007
    • 296

    #2
    Hi,

    Have you checked the log? I once a had a similar problem, not sure it's the same...

    /MK

    Comment

    • solinem
      New Member
      • Sep 2008
      • 2

      #3
      Originally posted by MarkoKlacar
      Hi,

      Have you checked the log? I once a had a similar problem, not sure it's the same...

      /MK
      Thanks, yes I did, the extract of the contents of the log is the following:
      PHP Fatal error: Out of memory (allocated 786432) (tried to allocate 32768 bytes)
      [notice] Parent: child process exited with status 255 -- Restarting.

      Comment

      • MarkoKlacar
        Recognized Expert Contributor
        • Aug 2007
        • 296

        #4
        Hi,

        Sorry for the late reply, I did not run into that error message...sorry ...

        /MK

        Comment

        Working...