Forums

Mysterious hit by /wordpress/wp-cron.php?check= II (12 posts)

  1. modifoo
    Member
    Posted 11 months ago #

    For quite some while I have been experiencing the wp-cron problem, meaning that my server gets a lot of hits from wp-cron trying to execute.

    I have a number of word press installations running on the rented server, and this problem only occurs one my main blog (www.modifoo.com), but on none of the others. Some days the wp-cron makes over 10.000 hits, eating more than 1/3 of the server time.

    I read quite a few of the threads discussing this problem, and the only solution so far I have found is disabling wp-cron, which I know is not a good solution, and only works until the next update.

    I have tried running the wp-cron-fix.php script mentioned in another thread, but only got the following error messages:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/6252/domains/modifoo.com/html/wp-cron-fix.php:29) in /home/6252/domains/modifoo.com/html/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 119
    We are fixing Cron for Post ID :
    Warning: usort() [function.usort]: The argument should be an array in /home/6252/domains/modifoo.com/html/wp-cron-fix.php on line 51

    Warning: Invalid argument supplied for foreach() in /home/6252/domains/modifoo.com/html/wp-cron-fix.php on line 53

    I also tried changing the WP-cron permission to 644, as suggested in yet another thread. Again, no luck.

    I do not know my way around .htaccess - but there is no .htaccess file in the root folder of the domain, which is where wordpress is installed.

    I just updated to the current version of wp, and just like the last times, this has not helped.

    Hope someone can help - thanks a lot!

  2. modifoo
    Member
    Posted 11 months ago #

    I just had a look at my log, and all the wp-cron requests get a 200:

    64.13.205.47 - - [17/Nov/2008:02:01:06 -0800] "GET /modifoo.com/wp-cron.php?check=750f6724adfde56a416052cbd28a0f3f HTTP/1.0" 200 - "-" "-"
    64.13.205.47 - - [17/Nov/2008:02:01:24 -0800] "GET /modifoo.com/wp-cron.php?check=750f6724adfde56a416052cbd28a0f3f HTTP/1.0" 200 - "-" "-"

    All subsequent requests come from the same IP address and have the same check= number.

    Any help is greatly appeciated!

  3. modifoo
    Member
    Posted 11 months ago #

    Still running today:

    64.13.205.47 - - [27/Nov/2008:03:03:44 -0800] "GET /modifoo.com/wp-cron.php?check=750f6724adfde56a416052cbd28a0f3f HTTP/1.0" 200 - "-" "-"

  4. slavben
    Member
    Posted 11 months ago #

    Same issue here

  5. modifoo
    Member
    Posted 11 months ago #

    Otto?

    Anyone?

  6. n2nel
    Member
    Posted 11 months ago #

    I have the same problem.. wp-chron starting every 15/20 minutes and doing several access...

    Heres an example of wassup statics:

    * 20:33:52 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:36:56 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:40:00 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:43:55 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:46:58 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:50:02 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:53:07 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:56:10 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...
    * 20:59:15 ->/wp-cron.php?check=1257a7f5db1fdb05fc9d61bf...

    Someone help us please!

  7. modifoo
    Member
    Posted 11 months ago #

    Hmm... been doing a bit more of searching and trying.

    Turns out when I try to access wp-cron.php directly, I get a 403 error - even though the permissions are set to 755. Weirder still, if I delete wp-cron, I still get a 403, and not a 404.

    On my other domains I don't get any error messages at all.

    So - how do I fix the permissions? Or is that something that is wrong with the .htaccess?

  8. modifoo
    Member
    Posted 11 months ago #

    Fixed the 403 issue, there was a strange rewrite rule in .htaccess

    Alas, my server still gets hit with the wp-cron.php requests.

    Anyone here to help???

  9. n2nel
    Member
    Posted 11 months ago #

    I really can't undestand, maybe we are using some plugin that calls that cron request... my htaccess got the basic rewrite commands.. so i don't think it belongs to htaccess settings...

    I hope someone will help us solving this bad situation...

  10. n2nel
    Member
    Posted 11 months ago #

    btw, who is your hosting provider? i'm with Godaddy

  11. samboll
    moderator
    Posted 11 months ago #

  12. Tozzano
    Member
    Posted 6 months ago #

    I was having constant 403 hits in my logs, and from 127.0.0.1
    It turns out that when I installed, I had copied the files from /usr/share/wordpress to my web directory /var/www/html/public/wp
    In the configuration, I had set the main path to /var/www/html/public/wp as well.

    Into the Apache config, the installation had added this alias:

    Alias /wordpress "/usr/share/wordpress"
    <Directory "/usr/share/wordpress">
      Options FollowSymLinks
      AllowOverride Options
    </Directory>

    Since my Apache root is /var/www/html, I changed the alias to:

    Alias /public/wp "/usr/share/wordpress"

    And the errors are gone. I hope this helps someone.

Reply

You must log in to post.

About this Topic