Over a nine-minute span (from 05:21:07 to 05:29:54 AM) something on my system made 36 calls to /blog/wp-cron.php. That’s one call every 15 seconds or so.
It looks like my shared host has therefore disabled access to that file, since I’m seeing lines like this in my error logs now:
[Thu Mar 8 05:29:54 2007]
client denied by server configuration:
The only thing I can see that calls wp-cron.php in my blog root is:
Fortunately, it appears that there is a check built-in that tests for the presence of /wp-cron.php, so WP doesn’t go into an infinite loop. (addressed by http://trac.wordpress.org/ticket/3713 )
Apparently, my ISP cut off access t wo-cron.php because of the excessive calls that were being made to the file, and it was eating up system resources.
- What am I missing by not being able to access wp-cron?
- Can I work around this?
- Can I limit how frequently WP calls wp-cron?
- Does the existence of the root wp-cron.php conflict with Scott Merrill’s earlier plugin, esp. wp-cron-mail and etc?
I understand that wp-cron is called upon every visit to check the cron schedule to see if something is queued. Is there some kind of check to verify that the cron schedule isn’t corrupted, or is there a way to clear out the cron schedule if there is a corrupt entry in it?
Other threads mention wp-cron.php consuming server resources, but I don’t see any resolution:
Any help would be appreciated.
- The topic ‘More wp-cron.php and cron.php woes (server overload)’ is closed to new replies.