500 Internal error and CPU overload

  • namcoibn

    (@namcoibn)


    13 years ago

    Im running my site with WordPress using Hostgator package. Last 2 months, everything seem be fine. But now Im having the problem with the CPU load which cause the 500 Internal Error. At 1st, this error just sometimes happen but few days agon it start to occur continously. I have checked the processes running and see that it always above 20 processes. The plugin that I use are:
    1. WordPress SEO
    2. CKeditor
    3. Google XML SiteMap
    3. WP Super Cache

    When I check to see all the processes it show alot of index.php is running:
    8084 /usr/bin/php /home/…/public_html/index.php 0.5% 0.2% Kill Process
    7535 /usr/bin/php /home/…/public_html/index.php 0.4% 0.6% Kill Process
    8054 /usr/bin/php /home/…/public_html/index.php 0.6% 0.3% Kill Process
    7995 /usr/bin/php /home/…/public_html/index.php 0.6% 0.5% Kill Process
    7904 /usr/bin/php /home/…/public_html/index.php 0.5% 0.6% Kill Process
    7794 /usr/bin/php /home/…/public_html/index.php 0.5% 0.6% Kill Process
    7633 /usr/bin/php /home/…public_html/index.php 0.5% 0.6% Kill Process
    7579 /usr/bin/php /home/…public_html/index.php 0.4% 0.6% Kill Process
    8143 /usr/local/cpanel/cpanel ./frontend/x3/hg/processes.php 1.8% 0.4% Kill Process
    8145 /usr/bin/php /home/…/public_html/index.php 0.5% 0.0% Kill Process
    7584 /usr/bin/php /home/…/public_html/index.php 0.5% 0.6% Kill Process
    7476 /usr/bin/php /home/…/public_html/index.php 0.4% 0.6% Kill Process
    8044 /usr/bin/php /home/…/public_html/index.php 0.7% 0.4% Kill Process
    7632 /usr/bin/php /home/…/public_html/index.php 0.5% 0.6% Kill Process

    Is there anyone have the same problem with me?

Viewing 4 replies - 1 through 4 (of 4 total)
  • M Asif Rahman

    (@asif2bd)

    13 years ago

    You have Caching enabled, though I dont know the setting, but I am guessing its configured with basic setting. Without super load, I mean at least fifty user visiting your site at a time and you update content very frequently you should never get any issue.

    Few key pointed:
    1. WordPress SEO now could generate Sitemap, but you also have “Google XML SiteMap” I hope you are not running both.

    2. In “Google XML SiteMap” uncheck built the Sitemap in each GET request. Assign specific memory, may be “64M” and dont let the screen run for unlimited time, keep it under 60sec or something, there should be limit by HG.

    3. If you are not updating content too much, maybe try to refresh cache only when you update any content or change something, to reduce load.

    I personally like W3 Total Cache for more control, but its true if you cant use Memcache or APC using W3TC is useless.

    I use W3TC in my blog and posted few tips too.

    Thread Starter namcoibn

    (@namcoibn)

    13 years ago

    Thanks for your advice. I think I’m using both SiteMap together. I will take a look at it. So which sitemap should I disable? Google XML SiteMap or WP-Seo SiteMap?

    Thread Starter namcoibn

    (@namcoibn)

    13 years ago

    I take a look at both plugin and you are correct. Im running both sitemap at the same time. Which one should I disable now?

    Thread Starter namcoibn

    (@namcoibn)

    13 years ago

    After diable XML sitemap of WPSEO and change the setting of “Google XML SiteMap” like your suggestion. It seem to reduce abit of process but after sometimes it increase again eventhough online people on my site is not really alot. I mean when there was 150 people online at a time. The number of process is quite low (<10 process) but now only 61 people online and number of process if above 20. I really dont understand what happen. It suddenly come up from 1 process to 20, then back to 1 then 20.

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

The topic ‘500 Internal error and CPU overload’ is closed to new replies.