WordPress.org

Ready to get started?Download WordPress

Forums

Cannot allocate memory Error (13 posts)

  1. skullz
    Member
    Posted 3 years ago #

    Hello,
    I my cpanel error log is being flooded with the below error(s).
    My hosting support said that there is a problem with the script. The max memory for php script is "128M" and for wp its "64M". I have tried keeping even "128M" for wp. Total RAM is 1GB and the other process excluding wp take only 150-200M, 300M at max never more than that. I tried even deleting all wp files reinstalled again with just 5 essential plugins, still I get error.

    press is the folder of wp installation.

    Regards,
    Skullz.

    ------------------------Just a part of the error log-------------------
    [Thu Jan 06 17:02:30 2011] [error] [client 122.183.136.53] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://press.rockinfrnz.com/2010/12/03/what-is-the-musculine-form-of-postmistress/
    [Thu Jan 06 17:02:30 2011] [error] [client 122.183.136.53] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/wp-comments-post.php, referer: http://press.rockinfrnz.com/2010/12/03/what-is-the-musculine-form-of-postmistress/
    [Thu Jan 06 17:02:27 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:27 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:26 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:26 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:26 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://www.google.de/search?q=fame-girls&hl=de&ndsp=21&prmd=ivnsfdl&ei=Z8slTfjUJcX6lwfH7eTJAQ&start=260&sa=N
    [Thu Jan 06 17:02:26 2011] [error] [client 217.114.211.243] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://www.google.de/search?q=fame-girls&hl=de&ndsp=21&prmd=ivnsfdl&ei=Z8slTfjUJcX6lwfH7eTJAQ&start=260&sa=N
    [Thu Jan 06 17:02:26 2011] [error] [client 75.101.204.5] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:26 2011] [error] [client 75.101.204.5] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 17:02:22 2011] [error] [client 184.73.107.3] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://feeds.feedburner.com/~r/RockinfrnzArchive/~3/N9f8xYgj2iA/?utm_source=feedburner&utm_medium=twitter&utm_campaign=rockinfrnz
    [Thu Jan 06 17:02:22 2011] [error] [client 184.73.107.3] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://feeds.feedburner.com/~r/RockinfrnzArchive/~3/N9f8xYgj2iA/?utm_source=feedburner&utm_medium=twitter&utm_campaign=rockinfrnz
    [Thu Jan 06 17:02:18 2011] [error] [client 80.98.164.46] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php, referer: http://press.rockinfrnz.com/2010/12/03/what-is-the-musculine-form-of-postmistress/
    [Thu Jan 06 17:02:18 2011] [error] [client 80.98.164.46] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/wp-comments-post.php, referer: http://press.rockinfrnz.com/2010/12/03/what-is-the-musculine-form-of-postmistress/
    [Thu Jan 06 16:52:41 2011] [error] [client 74.112.128.62] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:41 2011] [error] [client 74.112.128.62] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:40 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:40 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:38 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:38 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:36 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:36 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php
    [Thu Jan 06 16:52:35 2011] [error] [client 211.43.152.54] (12)Cannot allocate memory: couldn't create child process: /opt/suphp/sbin/suphp for /home/p828691r/public_html/press/index.php

  2. hedronist
    Member
    Posted 3 years ago #

    When did this start happening? Have you recently changed themes? Added a plugin?

    64M should be enough for medium-large sized WP sites. If you are routinely using that much or more then something very inefficient/suspicious is happening.

  3. skullz
    Member
    Posted 3 years ago #

    This problem has been there for a week now, So I re-installed wp deleting all the files(inc plugins,themes,etc), still I am getting this error. But the TPC! Memory usage plugin shows Peak memory used as 3.2M and always it shows ~2M, The server has 8 cores and the load avg ~ 2.36 1.85 1.43
    A weird problem?!

  4. skullz
    Member
    Posted 3 years ago #

    Does somebody experience the same problem. I guess this started after upgrading to 3.0.4. My error log is being flooded with the same error, please suggest a solution soon.
    Thanks.

  5. hedronist
    Member
    Posted 3 years ago #

    The number of cores, total memory on the machine, and load average have nothing to do with this. You have a shared hosting account and that always comes with hard limits on things like max memory and max CPU time.

    If a completely vanilla install of WP is causing you to max out on 64M of memory, something is definitely wrong. Unfortunately, we can't do anything for you, only your hosting company can.

  6. skullz
    Member
    Posted 3 years ago #

    I am on VPS not shared hosting. The hosting support told me that the script is poorly written. I have upgraded the RAM to 2GB now. Can you suggest any steps to over come this?

  7. skullz
    Member
    Posted 3 years ago #

    Have you had any experience with lighttpd or nginx, will those reduce the load and are there any backdrops for them? Also, how many users will be able to access the site simultaneously on a 2GB an 1 GB RAM?
    Thanks. :)

  8. hedronist
    Member
    Posted 3 years ago #

    I haven't played with WP under either of those, but I used nginx as the front-end server for a Django site I did.

    Since this is a VPS and you have 2GB, then getting an out of memory error is much more serious. Just cranking up the allowed memory for PHP without knowing the cause of the problem is the wrong way to approach this.

    My gut is that there is something that is either a) doing infinite recursion (e.g. function foo() calls foo() calls foo(), etc. etc.) or b) some function is allocating massive amounts of memory to do ... something.

    Since you don't have a good idea of what the problem is, I suggest backing off to something simple (like a file that just does phpinfo()) to verify that things aren't completely hosed. Then I would do a 100% vanilla WP and verify that it works. If you are comfortable at the command prompt you might want to run top in ans SSH window while doing the above.

  9. skullz
    Member
    Posted 3 years ago #

    When I used top, mysql and wp was in top. There are 7 instances of wp running at the same time. Each wp process uses around 8 to 15% of RAM.

  10. hedronist
    Member
    Posted 3 years ago #

    8 to 15% of 2GB? That's 160MB to 300MB per instance. What are you doing?

    I think your problem is beyond anything that can be solved by posting to this forum. You need someone to take a look at you entire setup to figure out where all of the memory is being sucked up.

  11. skullz
    Member
    Posted 3 years ago #

    Thanks for your time. Site's now working fine after installing Litespeed.

  12. 1stAngel
    Member
    Posted 2 years ago #

    I have exactly the same issue and it started after the last upgrade of WP.

    I tried moving from shared to VPS thinking that would solve it but now my server keeps crashing and this is the error.

    I cannot afford to upgrade memory, this is a joke. I have been with WP for many many years but cannot keep upgrading servers to keep up with things.

    I will have a look to see what lightspeed is but it looks like wp and me may finally have to part company as I am not at my wits end. Not all of us are technically adept.

  13. denede19
    Member
    Posted 2 years ago #

    have the same problem since i've upgraded to wp 3.2
    i get this in error log when i try to insert image to a post
    i guess it's from the PHP version installed
    it says 5.2.4 or hight..
    and i have 5.2.14 ..or smomething ..
    i'll tell the admin to upgrade the php ..
    and see if that works..
    maybe u guys should try this too

Topic Closed

This topic has been closed to new replies.

About this Topic