WordPress.org

Forums

Out of Memory when updating to 3.0.3 (13 posts)

  1. EvilTactician
    Member
    Posted 4 years ago #

    When trying to update from 3.0.2 to 3.0.3 we constantly get this error:
    Fatal error: Out of memory (allocated 16777216) (tried to allocate 2975715 bytes) in /home/manapool/public_html/wp-includes/class-http.php on line 1406

    I've read hundreds of topics about this and followed all advice in regards to ensuring PHP has anough memory allocated in php.ini, wordpress itself has it specifically defined. htaccess, etc. The works.

    The odd thing is - we already had 32M set in php.ini - and even when increasing it to 64M the issue remains.

    memory_limit 64M 64M

    phpinfo(); states we have 64M available, WordPress also states that - but the error remains when updating.

    * PHP Version : 5.3.3 / 32Bit OS
    * Memory limit : 64 MByte
    * Memory usage : 8.04 MByte

    I'm completely at a loss here, we have tried to resolve it for 3 days. I've got a systems administrator looking at it who is also baffled, we tried restarting the server, restarting apache, everything. Even when everything claims we only have 7M in use, as soon as we hit update - the script fails and claims we only have 16M and that there isn't the available 3M to update. It just doesn't make sense!

    Anyone who can provide insight - it would be VERY welcome.

  2. Tara
    Member
    Posted 4 years ago #

    probably you already know, here is Codex guide on memory increase.
    http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

    Also, may be you try manual update:
    http://codex.wordpress.org/Updating_WordPress

  3. EvilTactician
    Member
    Posted 4 years ago #

    Thank you - we've gone through all methods of allocated memory and PHP/Wordpress both clearly state there is 64M available. But then when we try updating it claims there is 16M...

    As for a manual update, yeah we could do that. But that doesn't explain why the update script thinks there is only 16M available.

    We had one instance where we got a fatal error when browsing the site too, also out of memory on 16M. But when monitoring health, using a monitoring plugin or when checking phpinfo(); it clearly states there is 64M available.

    WP-config & the rest of the back-end code also clearly make 64M available. We've even done searches through all source code to try and find a plugin/script which would override this to 16M but no luck... Kind of at a loss here.

  4. hyperdude
    Member
    Posted 4 years ago #

    Which hosting provider are you using?

  5. Tara
    Member
    Posted 4 years ago #

    @ EvilTactician, have discussed this issue with your hosting provider?

  6. EvilTactician
    Member
    Posted 4 years ago #

    This website is hosted on a dedicated server. We have full root access.

    Our systems administrator has looked at all possible server side settings that we can think of, to no avail.

  7. CSD-Images
    Member
    Posted 4 years ago #

    I had a similar issue, and had the servers configured both in the wp-config and PHP.ini. The way I got round it was twofold:

    1) Dsable all plug-ins on the site. Test if WordPress is running, if it does then go to stage 2.

    2)Install TPC! Memory Usage. This is a great plug-in for giving tons of information on your server and memory usage. Run this plug-in and see if WP starts up.

    3) If 1 didn't work and/or you can't run TCP then increase the RAM usage to 128Mb or 256Mb accordingly. Then rinse and repeat.

    If you fail at 256Mb then try re-uploading the WP files.

  8. EvilTactician
    Member
    Posted 4 years ago #

    * Usage Sample: 8.31MB (13%)
    * Peak Usage: 8.5MB (13%)
    * All-Time: 14.41MB on 12/11/10 @ 12:45 pm (shutdown)
    * Load Averages: 0.1 0.09 0.02
    * WP Memory Limit: 32M
    * PHP Memory Limit: 64M

    Problem is - when trying to upgrade it still gives a fatal error and claims there's only 16M available:

    Fatal error: Out of memory (allocated 17039360) (tried to allocate 2975715 bytes) in /home/manapool/public_html/wp-includes/class-http.php on line 1406

    This is inconsistent with what all other settings/statistics are telling us.

  9. EvilTactician
    Member
    Posted 4 years ago #

    I've increased WP Memory Limit to 64M as well by editing default-constants.php - but that made no difference whatsoever to upgrading. It still claims it has 16M available.

    * Usage Sample: 8.31MB (13%)
    * Peak Usage: 8.5MB (13%)
    * All-Time: 14.41MB on 12/11/10 @ 12:50 pm (shutdown)
    * Load Averages: 0.07 0.07 0.02
    * WP Memory Limit: 64M
    * PHP Memory Limit: 64M

    Fatal error: Out of memory (allocated 17039360) (tried to allocate 2975715 bytes) in /home/manapool/public_html/wp-includes/class-http.php on line 1406

  10. CSD-Images
    Member
    Posted 4 years ago #

    Just do a manual ugprade, if you're doing an automatic update for 3.03 I've heard of a few issues with it for some strange reason. This word of mouth and I can't verify at present (the guy's asleep!)

    I've had issues with WordPress seeing one value and the system reporting another, and I know the system is right due to other scripts.

    Might be worth logging a possible bug?

  11. hyperdude
    Member
    Posted 4 years ago #

    Have you tried rebooting the server? (not just restart web services). I had an issue with my Linode VPS running nginx. I changed php.ini file and did not see any changes take place until I restarted the server.

  12. EvilTactician
    Member
    Posted 4 years ago #

    @hyperdude Yes - I actually stated that in my original post. As you can see from further provided information, phpinfo as well as WordPress itself recognise there is 64M available.

  13. EvilTactician
    Member
    Posted 4 years ago #

    This issue is now resolved. For anyone running into this situation in the future, WHM had set RLimitMem to 85mb and for some reason that was limiting WordPress to the above limits.

    When removing said limit in httpd.conf - the issue was gone entirely.

Topic Closed

This topic has been closed to new replies.

About this Topic