After monitoring the comments that Akismet blocked very carefully, I can report that I’ve had no false positives for nearly a week. I’m not quite sure what changed to fix things.
With a dynamic system like Akismet, things will change over time. That is the nature of the beast. I don’t know whether Matt and the crew tweaked something, or whether a concerted poisoning attempt stopped being effective, but I’m glad I can start trusting it again.
I suspect it was the former because the change back was very dramatic, though I’m sure Automattic would not want to admit to it.

Server Trouble

In the meantime, at around one this morning, my server went down, or rather my blog stopped working. After a quick investigation, I determined that the database server was complaining of too many connections. I checked and there were a large number of httpd processes running. Presumably each, or most had a database connection open. Static files were being served ok, but anything involving the database was failing.

I restarted the Apache and that seemed to cure it. I started checking through log files to see if I could determine the culprit, but found nothing suspicious. Fifteen minutes later the site was down again. I then spent the next two hours monitoring the situation. A quick script allowed me to watch the process count:

ps -ef | grep httpd | wc -l

It was growing quite rapidly from an initial 16 to over 100, though the site would start failing at about 80. In the end I gave up when the process count stayed stable for 20 minutes. Though when I checked after a few hours sleep, it had gone down again and was down for over 5 hours. I’m presuming it was an attack of some kind.
It has since gone down again, but the growth in number of processes seems to take a much longer time. I didn’t find anything obvious in the logs that I checked, but maybe it is one of the lesser sites which is being attacked. I will continue to investigate…

I’ve just spent a rather painful 45 minutes recovering legitimate comments from my Akismet admin panel. Painful because Akismet had over 1400 comments marked as spam from the last week.

That number is not excessive for my blog: Akismet has caught over 12,000 spam comments since I installed it; but I’ve not been keeping on top of the list this week. Unfortunately checking for false positives is impossible once you have more than 150 spam comments.

The Akismet plugin displays the newest 150 comments each with a check box to allow you to separate the legitimate ones from the rubbish (the ham from the spam). That’s great: check the boxes, push the “not spam” button.

However, the only other action is to delete all the comments that Akismet has determined are spam. But if you have legitimate comments that are not in the most recent 150, you cannot see them to rescue them.

Luckily for me, I’m technical enough that I can figure out how to get round problems like this, but most people are not.

In the end, I rescued somewhere between 40 and 50 comments. I’m not sure of the exact number because I wasn’t paying attention, and releasing them from Akismet’s clutches doesn’t trigger the email notification so I can’t count the emails either. Not one single comment was let through in the last 6 days. I don’t know whether this is a minor hiccup from Akismet or the start of an alarming trend.

I then spent another 20 minutes responding to some of them. Oh yeah, and I’ve spent another 30 minutes writing this post!

I think I will have to look at enhancing the Akismet plugin. Either by adding a ‘delete just spam in the list’ button or by adding pagination to the list of spams. The former sounds far easier than the latter.

Although it has been available for a few days now, WordPress 2.0 ‘Duke’ is now official.

In fact has already had been downloaded more than 33,000 times as I write this! You can download it from the revamped WordPress.org web site.

There is a lot of new code in this release, most of which is concerned with either the Administration interface, especially the WYSIWYG write interface, or under the hood stuff which will benefit plugin and theme developers. There are a whole bunch of bug fixes too.

There are some very compelling reasons to upgrade to this new version, but there are a whole bunch of reasons to hold off too: Continue reading →

I see that Matt has opened up WordPress.com for signups without invites. So you no longer need an invite or a copy of Flock to signup for a WordPress.com blog

The service has been scaling very well since we got the problems from the move worked out.

This is very exciting news. I think there will be some great things to come out of this project. Especially the community aspects.

I also noticed that Google’s Gmail has removed the “invitation” block from the logged in screens. Though there isn’t a general “sign up here” notice on their home page. However like using Flock to get into WordPress.com, there has been a non-invitation route in to gmail for a while; you can sign up to Gmail via SMS.

I noticed a few people are reporting the new WordPress MU site webloog.com. I’d be interested to know which version of WordPress MU they are running, there is no version string in the normal output.

I also notice that the feature list from wordpress.org is included verbatim. Thus it mentions, Full standards compliance. Unfortunately none of the pages that I’ve tried to validate manage to be standards compliant! In their eagerness to include Google adsense adverts, they didn’t bother to insert them in a compliant way! There are other issues too.

It seems to be run by the same people who are behind Free.TV. You know, the free-set-top-box-but-you-have-to-buy-it-first-and-you-might-get-a-refund people! Hmmm… Proceed with caution.

Update:It turns out the domain owner is Ric Johnson the guy behind OpenDomain.org, and also connected with free.tv, however webloog.com is run by Scott Sykes who really needs to add some contact information to make things clear. Scott is behind some other community sites, including blogsforjesus.com and nationofchrist.com. He also runs a blog at vivablog.com