This usually happens if your WordPress install is having problems reaching akismet.com to check a comment for spam. Check to see if your network/firewall/proxy have had any problems that would cause this.
Thread Starter
yeswap
(@yeswap)
Thanks Joesph,
Theres nothing in my server error logs and there have been no connectivity issues reported for either site. Pingdom is checking connectivity to the sites every 60 seconds 24/7 and shows no problems either.
The fact that two sites on different servers experienced this issue shortly after the upgrade to 2.5.3 points to either a problem with the update or a connectivity issue on Akismet’s end. As the error hasn’t recurred I suspect the latter.
Also, the fact that the error wasn’t cleared after I successfully connected to the Akismet servers by pressing the “Check for spam” button seems to be a bug.
Double checking with our systems folks, it looks like there was a small window where one of the datacenters was having issues. It is certainly possible that you hit that.
In general you can checkout akismet.com uptime at http://status.automattic.com/9931/136079/Akismet-API
The message should get automatically cleared with the scheduled re-check job gets run.
If this is the case that you hit this window, then the plugin did the right thing, by scheduling the comments to be re-checked later.
I have the same exact problem when I updated to Akismet 2.5.3 with the latest WordPress 3.1.2. I have no network issues and the Akismet config page reports everything is accessible. Definitely looks like a code problem to me.
@dmulter –
Any thing in your web server error logs that would provide a hint as to what is happening? What does the history listing show on an individual comment that didn’t get properly checked look like?
I am getting the same after server migration and no errors in the log
Am now trying a time out of 30….
