wp-cron.php server load

  • Chris

    (@chris)


    18 years ago

    My host keeps suspending my account. Here’s what they sent me as the problem:

    Hello your account has been suspended as it is causing severe loads on this shared server.
    26274 nobody 19 4 34052 21m 5676 R 24.6 1.1 0:48.34 httpd
    14519 nobody 19 4 33528 21m 5756 S 23.6 1.0 1:18.85 httpd
    13847 nobody 19 4 30896 20m 5556 S 23.6 1.0 0:03.39 httpd
    13735 nobody 19 4 37784 25m 5840 S 21.7 1.3 10:14.20 httpd
    13740 nobody 19 4 37680 25m 6004 R 21.7 1.3 9:39.34 httpd
    13744 nobody 20 4 39032 26m 5872 S 21.7 1.3 9:04.74 httpd
    2047 nobody 20 4 34912 22m 5716 S 21.7 1.1 7:37.89 httpd
    22651 nobody 19 4 33208 20m 5708 S 20.7 1.0 0:54.73 httpd
    13848 nobody 19 4 30896 20m 5556 S 20.7 1.0 0:01.66 httpd
    15358 nobody 20 4 30896 20m 5556 S 20.7 1.0 0:00.49 httpd
    13722 nobody 19 4 30900 20m 5612 S 19.7 1.0 1:19.86 httpd
    13733 nobody 19 4 37404 25m 6364 S 18.7 1.3 9:49.93 httpd
    24589 nobody 19 4 31748 21m 5576 S 18.7 1.1 0:56.22 httpd
    12922 nobody 20 4 30576 20m 5568 S 14.8 1.0 0:04.98 httpd
    13737 nobody 20 4 105m 49m 5872 S 10.8 2.4 7:57.68 httpd
    14747 nobody 19 4 30896 20m 5560 S 9.9 1.0 0:03.80 httpd
    14771 nobody 20 4 30896 20m 5560 S 9.9 1.0 0:03.93 httpd
    16054 nobody 20 4 34008 21m 5752 R 7.9 1.1 3:18.07 httpd
    12701 nobody 20 4 30580 20m 5560 R 7.9 1.0 0:09.15 httpd
    13734 nobody 19 4 37612 25m 5880 S 4.9 1.3 8:40.11 httpd
    14746 nobody 20 4 30612 20m 5580 S 4.9 1.0 0:02.21 httpd
    13743 nobody 20 4 37836 25m 5988 S 3.0 1.3 9:38.80 httpd
    4474 nobody 20 4 34016 21m 5664 S 3.0 1.1 1:28.25 httpd
    14858 nobody 20 4 30896 20m 5576 S 3.0 1.0 1:31.69 httpd
    29-5 – 0/0/11938 . 10.03 64 1586 0.0 0.00 37.89 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    30-5 – 0/0/11969 . 3.09 64 1835 0.0 0.00 22.14 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    31-5 – 0/0/11411 . 9.30 64 1684 0.0 0.00 25.13 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    32-5 – 0/0/10569 . 0.24 64 1827 0.0 0.00 25.13 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    33-5 – 0/0/10361 . 0.26 63 890 0.0 0.00 24.21 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    34-5 – 0/0/10102 . 0.08 55 2 0.0 0.00 16.03 213.58.96.114 http://www.lisboaescort.net GET /escorts/laura/images/prev6.jpg HTTP/1.1
    35-5 – 0/0/9036 . 0.24 63 1006 0.0 0.00 13.37 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    36-5 – 0/0/8907 . 0.96 135 1537 0.0 0.00 28.20 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    37-5 – 0/0/8185 . 8.38 81 768 0.0 0.00 9.10 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    38-5 – 0/0/7616 . 0.24 138 1817 0.0 0.00 15.82 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    39-5 – 0/0/7431 . 4.59 72 971 0.0 0.00 8.02 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    40-5 – 0/0/6441 . 5.68 92 1435 0.0 0.00 8.97 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    41-5 – 0/0/6207 . 4.82 101 1096 0.0 0.00 8.18 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    42-5 – 0/0/5961 . 2.63 117 1552 0.0 0.00 6.58 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    43-5 – 0/0/5386 . 1.67 125 1336 0.0 0.00 12.17 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    44-5 – 0/0/5036 . 0.97 130 1512 0.0 0.00 5.18 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    45-5 – 0/0/4287 . 2.60 250 1371 0.0 0.00 5.63 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    46-5 – 0/0/4224 . 5.19 137 1219 0.0 0.00 4.15 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    47-5 – 0/0/4114 . 1.21 258 1170 0.0 0.00 5.41 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    48-5 – 0/0/3680 . 1.94 254 2422 0.0 0.00 4.60 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    49-5 – 0/0/3110 . 1.91 257 2024 0.0 0.00 4.23 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    50-5 – 0/0/2818 . 1.45 260 1230 0.0 0.00 5.70 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    51-5 – 0/0/2527 . 1.20 263 2117 0.0 0.00 2.17 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    52-5 – 0/0/2138 . 0.96 260 1291 0.0 0.00 2.80 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    53-5 – 0/0/2010 . 0.48 270 646 0.0 0.00 11.05 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    54-5 – 0/0/1604 . 0.73 267 2010 0.0 0.00 0.84 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    55-5 – 0/0/1298 . 1.18 263 1627 0.0 0.00 1.24 72.18.130.57 http://www.chrism.us GET /journal/wp-cron.php?check=131accfed8363d4c40f4b38b43f9d129
    56-5 – 0/0/1184 . 0.47 2225 406 0.0 0.00 1.41 72.18.130.57 http://www.chrism.us

    I deleted wp-cron.php. I didn’t know what else to do.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Chris

    (@chris)

    18 years ago

    Can someone give me any information. My account remains suspended. All I am running is a wp journal.

    Thread Starter Chris

    (@chris)

    18 years ago

    No one is enterested even though this could mean there’s a way to hack wp-cron.php and use your site for sending spam?

    davidchait

    (@davidchait)

    18 years ago

    I’ve never learned how to read those server dumps — maybe someone with some experience can chime in.

    What exactly leads you to say “this could mean there’s a way to hack wp-cron.php and use your site for sending spam”?

    wp-cron is used to do certain things, such as pings and trackbacks. if you had an insanely long ping list, AND you are using feedwordpress or a reblogging tool, I could see a server getting overloaded. Otherwise, I’m not sure what the issue might be. The core devs don’t always read stuff unless one of the admin-types (Podz, etc.) bring it to their attention.

    But, maybe someone will see this and take a looksee… 😉

    -d

    Thread Starter Chris

    (@chris)

    18 years ago

    Ahhh my host was able to settle a few things.

    First its not the plugin wp-cron! It’s the cron.php in wp-includes. They have not been able to figure out exactly what’s going wrong with it but that’s a start.

    Thread Starter Chris

    (@chris)

    18 years ago

    Email from host:

    The issue with your site causing loads has been identified,
    The calling of wp-cron.php even though it was removed by the script cron.php was the culprit.
    I have renamed the cron.php to cronBAD.php so it does not cause issues
    I have unsuspended your site and will monitor the loads.
    please do not enable that cron job as it will cause server load issues and in turn get your site suspended.

    Thread Starter Chris

    (@chris)

    18 years ago

    Hmm..

    Line 70:

    $cron_url = get_settings( 'siteurl' ) . '/wp-cron.php';
    $parts = parse_url( $cron_url );

    $argyle = @ fsockopen( $parts['host'], $_SERVER['SERVER_PORT'], $errno, $errstr, 0.01 );
    if ( $argyle )
    fputs( $argyle,
    "GET {$parts['path']}?check=" . md5(DB_PASS . '187425') . " HTTP/1.0\r\n"
    . "Host: {$_SERVER['HTTP_HOST']}\r\n\r\n"
    );
    }

    davidchait

    (@davidchait)

    18 years ago

    As I said before:

    wp-cron is used to do certain things, such as pings and trackbacks. if you had an insanely long ping list, AND you are using feedwordpress or a reblogging tool, I could see a server getting overloaded. Otherwise, I’m not sure what the issue might be.

    The fsockopen is used to ‘spawn’ off a secondary ‘thread’ of execution to go process stuff waiting to be done. Do you have 20 sites in your ping list? Do you use any re-blogging plugins, or post heavily yourself?

    I guess if there was some error, and the list got backed up, then every session it’d try to start up cron stuff. Yeah, that would make some sense. Have you looked at error logs for any errors in the running of the wp-cron.php file?

    I believe you can set up a cron job to run say every 10 minutes or something and hit wp-cron.php, to process stuff all at once, completely offline. renaming it is probably ‘bad’, there’s likely a proper way to disable the async stuff and do it more directly (I believe for CGI interfaces, the code falls back to an IFRAME for post-related activities).

    Unless you see stuff in the error log, this might need to be ‘raised’ to the folks on the wp-hackers mailing list, as someone there might have a better idea.

    Thread Starter Chris

    (@chris)

    17 years, 11 months ago

    This behavior continued after the wp-cron plugin was removed. I do not believe it was the plugin. I have NO sites in my ping list. I do not accept pings. I have no auto processes set up ie check links for updates. My rss files are removed.

    davidchait

    (@davidchait)

    17 years, 11 months ago

    “This behavior continued after the wp-cron plugin was removed.”

    You mean, wp-cron.php being called and taking up resources? Or some other script? Is the IP address listed the IP address of the server itself?

    You don’t ping any sites? That’s different. Well, if no pinging OUT, no pings IN, no trackbacks, etc., you can probably safely not use the cron stuff. But, in all reality, this topic needs a core developer to chime in.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘wp-cron.php server load’ is closed to new replies.