upgraded to 3.0.1.
If I schedule a post, or fire off wp-cron.php manually, in both cases
noticed the following example from my httpd logs.
192.168.0.1 - - [16/Aug/2010:13:51:05 -0400] "HEAD /images/47_cedar_street_small.jpg HTTP/1.0" 200 - "-" "WordPress/3.0.1; /wp"
192.168.0.1 - - [16/Aug/2010:13:51:05 -0400] "HEAD /images/twojjs_logo.jpg HTTP/1.0" 200 - "-" "WordPress/3.0.1; /wp"
192.168.0.1 - - [16/Aug/2010:13:46:56 -0400] "POST /wp/wp-cron.php?doing_wp_cron HTTP/1.0" 500 - "-" "WordPress/3.0.1; /wp"
192.168.0.1 is my internal IP for my network, take that as the server requesting from itself. Last line indicates when request for wp-cron was made and finished. NOTE: the 500 response code.
above that shown are hundreds of requests for IMAGES only, no html or wp pages.
Scheduled post is updated to published... but there is no sense or reason for it to check HEAD on these image files... they are NOT even in the wp directories!
This seems to fire off anytime a change is made on the blog.
wp-cron has settings, by default, to check for modifications every 10 minutes, I think.
Any clues as to what is up?
I'm considering just disabling wp-cron altogether for now.... as this situation leads to a blockage of the server to other users (almost, it consumes MOST of the connections available to the server for a given period).