Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’m experiencing exactly the same issue. Analog and Webalizer are both showing vastly higher statistics than the GA Plug-in. The difference is enormous.

    I’ve disabled the plug-in for now, and inserted the GA code manually to see if the discrepancy remains or if GA starts showing data more in line with the server logs.

    Thread Starter EvilTactician

    (@eviltactician)

    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.

    Thread Starter EvilTactician

    (@eviltactician)

    @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.

    Thread Starter EvilTactician

    (@eviltactician)

    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

    Thread Starter EvilTactician

    (@eviltactician)

    * 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.

    Thread Starter EvilTactician

    (@eviltactician)

    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.

    Thread Starter EvilTactician

    (@eviltactician)

    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.

Viewing 7 replies - 1 through 7 (of 7 total)