Here is line 14 btw:
`Logging HTTP request messages to error_log
Sorry bad copy, it was this:
error_log( "$transport: {$response['response']['code']} {$response['response']['message']}" );
Nevermind I found the error_log it was in the root /blog directory… here are some of the most current contents:
[03-Mar-2011 04:23:24] GET http://api.wordpress.org/core/version-check/1.5/?version=3.0.5&php=5.2.9&locale=en_US&mysql=5.0.91&local_package=&blogs=1&users=3&multisite_enabled=0 HTTP/1.0
[03-Mar-2011 04:23:24] 200 OK
[03-Mar-2011 04:23:25] WP_Http_Curl: 200 OK
[03-Mar-2011 04:23:25] server: nginx
[03-Mar-2011 04:23:25] date: Thu, 03 Mar 2011 10:23:25 GMT
[03-Mar-2011 04:23:25] content-type: text/plain; charset=utf-8
[03-Mar-2011 04:23:25] connection: close
[03-Mar-2011 04:23:25] content-length: 842
[03-Mar-2011 04:23:25] Response body: a:3:{s:25:"add-to-any/add-to-any.php";O:8:"stdClass":5:{s:2:"id";s:3:"429";s:4:"slug";s:10:"add-to-any";s:11:"new_version";s:8:".9.9.7.7";s:3:"url";s:47:"http://wordpress.org/extend/plugins/add-to-any/";s:7:"package";s:62:"http://downloads.wordpress.org/plugin/add-to-any.0.9.9.7.7.zip";}s:23:"tweetmeme/tweetmeme.php";O:8:"stdClass":5:{s:2:"id";s:4:"6808";s:4:"slug";s:9:"tweetmeme";s:11:"new_version";s:3:"2.3";s:3:"url";s:46:"http://wordpress.org/extend/plugins/tweetmeme/";s:7:"package";s:55:"http://downloads.wordpress.org/plugin/tweetmeme.2.3.zip";}s:31:"wp-to-twitter/wp-to-twitter.php";O:8:"stdClass":5:{s:2:"id";s:4:"5140";s:4:"slug";s:13:"wp-to-twitter";s:11:"new_version";s:5:"2.2.7";s:3:"url";s:50:"http://wordpress.org/extend/plugins/wp-to-twitter/";s:7:"package";s:55:"http://downloads.wordpress.org/plugin/wp-to-twitter.zip";}}
[03-Mar-2011 04:23:25] POST http://api.wordpress.org/plugins/update-check/1.0/ HTTP/1.0
[03-Mar-2011 04:23:25] 200 OK
[03-Mar-2011 04:23:25] WP_Http_Curl: 200 OK
[03-Mar-2011 04:23:25] server: nginx
[03-Mar-2011 04:23:25] date: Thu, 03 Mar 2011 10:23:25 GMT
[03-Mar-2011 04:23:25] content-type: text/plain; charset=utf-8
[03-Mar-2011 04:23:25] connection: close
[03-Mar-2011 04:23:25] content-length: 6
[03-Mar-2011 04:23:25] Response body: a:0:{}
[03-Mar-2011 04:23:25] POST http://api.wordpress.org/themes/update-check/1.0/ HTTP/1.0
[03-Mar-2011 04:23:25] 200 OK
[03-Mar-2011 04:24:55] WP_Http_Curl:
[03-Mar-2011 04:24:55] Response body:
[03-Mar-2011 04:24:55] POST http://www.shortsaleartisan.com/blog/wp-cron.php?doing_wp_cron HTTP/1.0
[03-Mar-2011 04:24:55]
[03-Mar-2011 05:11:27] PHP Fatal error: Cannot use object of type WP_Error as array in /home/shortsal/public_html/blog/wp-content/plugins/error_log/akismet_test.php on line 14
[03-Mar-2011 05:25:19] WP_Http_Curl:
[03-Mar-2011 05:25:19] Response body:
[03-Mar-2011 05:25:19] POST http://www.shortsaleartisan.com/blog/wp-cron.php?doing_wp_cron HTTP/1.0
[03-Mar-2011 05:25:19]
[03-Mar-2011 06:25:45] WP_Http_Curl:
[03-Mar-2011 06:25:45] Response body:
[03-Mar-2011 06:25:45] POST http://www.shortsaleartisan.com/blog/wp-cron.php?doing_wp_cron HTTP/1.0
[03-Mar-2011 06:25:45]
[03-Mar-2011 07:33:41] WP_Http_Curl:
[03-Mar-2011 07:33:41] Response body:
[03-Mar-2011 07:33:41] POST http://www.shortsaleartisan.com/blog/wp-cron.php?doing_wp_cron HTTP/1.0
[03-Mar-2011 07:33:41]
There’s a lot of stuff there….. it goes for > 3000 lines.
Do you have any log entries for akismet.com?
Hmm I found this:
[08-Dec-2010 14:35:51] PHP Warning: Missing argument 1 for akismet_cron_recheck() in /home/shortsal/public_html/blog/wp-content/plugins/akismet/akismet.php on line 422
and this:
[16-Feb-2011 12:06:51] PHP Fatal error: Cannot use object of type WP_Error as array in /home/shortsal/public_html/blog/wp-content/plugins/error_log/akismet_test.php on line 14
Nothing for akismet.com specifically; though. Is this the correct error log to be reviewing, or should there be one somewhere else?
Thanks so much for the help Joseph, I’m really scratching my head here and am nearing my limits of technical knowledge 🙂
That error from 2010 has been fixed in more recent versions of the plugin.
Can you adjust line 14 to be:
error_log( print_r( $resposne, TRUE );
That will give us the details on $response no matter what data it contains.
I changed to this:
error_log(print_r($response, TRUE)); //( "$transport: {$response['response']['code']} {$response['response']['message']}" );
(note commenting out what it said before)
And now I’m getting this error:
Fatal error: Cannot use object of type WP_Error as array in /home/shortsal/public_html/blog/wp-content/plugins/http-debug/akismet_test.php on line 15
Line 15:
foreach ( $response['headers'] as $header => $value )
Ok, time for a direct, brute force approach. Lets just replace the wp_http_request_log function:
function wp_http_request_log( $response, $type, $transport=null ) {
error_log( "transport: {$transport}" );
error_log( print_r( $type, TRUE ) );
error_log( print_r( $response, TRUE ) );
}
This isn’t as elegant, but it shouldn’t have any problems logging data.
Well I updated the file, went to my comments and tried to recheck my spam queue. I get timed out after a while. I went and looked at the error log and didn’t see anything of note, then again i’m not 100% sure what I’m looking at.
[Code moderated as per the Forum Rules. Please use the pastebin]
“name lookup timed out” is interesting. It isn’t for an akismet.com request, but it could be an indication that your DNS servers aren’t doing their job. That could impact other things, like requests to akismet.com.
I’m going to contact my domain registrar… see if they can figure something out. I did notice earlier I’m having timeout issues on other things besides just Akismet
Hi, I followed the instructions on modifying the wp_http_request_log function and also fixed a sql query that was wrong and preventing this log to work.
I get http logs when posts are submited to google, bing, ask but nothing when I try to check the askimet servers. With this last modification on wp_http_request_log function I started getting something but it doesnt help:
04-Mar-2011 14:47:59] transport:
[04-Mar-2011 14:47:59] transports_list
[04-Mar-2011 14:47:59]
[04-Mar-2011 14:47:59] transport:
[04-Mar-2011 14:47:59] transports_list
[04-Mar-2011 14:47:59]
[04-Mar-2011 14:47:59] transport:
[04-Mar-2011 14:47:59] transports_list
[04-Mar-2011 14:47:59]
[04-Mar-2011 14:47:59] transport:
[04-Mar-2011 14:47:59] transports_list
[04-Mar-2011 14:47:59]
[04-Mar-2011 14:47:59] transport:
[04-Mar-2011 14:47:59] transports_list
[04-Mar-2011 14:47:59]
the function that I am usign now is:
function wp_http_request_log( $response, $type, $transport=null ) {
error_log( "transport: {$transport}" );
error_log( print_r( $type, TRUE ) );
error_log( print_r( $response, TRUE ) );
}
Not having a transport selected would be a problem, but also extremely odd. It looks for several functions to see if they are available for use, going all the way down to fsockopen.
The Akismet request is regular HTTP, so it shouldn’t be any different than any other other requests your WP install might make.
If you for the plugin (in akismet.php) to use fsockopen instead of the WP HTTP API does it work?
@joseph I forced akismet.php to use fsockopen changing the name of the wp http on line 134 – 135 and named it wp_remote_post2
// use the WP HTTP class if it is available
if ( function_exists( 'wp_remote_post2' ) ) {
When akismet started using fsockopen it worked. What is strange is that in this same server I have many others sites with wordpress and dont have this problem.
Where can I look to find why wp_remote_post doesnt work?
thank you
The wp_remote_post function is from the WordPress HTTP API – http://codex.wordpress.org/HTTP_API
I’d be really curious to find out why this particular WP install on this particular server isn’t happy with it. We’ve had a few other reports that are similar to this, but so far haven’t seen details on why this is happening.
To track this down you’d need to start adding more debug logging to the HTTP code in core WordPress.
