Under attack!

So says the host, anyway:

Our network is experiencing some kind of attack right now. Our admins are looking into this and working on resolution. We’ll post details and updates as soon as we get them, sorry about the inconvenience.

And this is up, just in case we’re fried at the Regular Site.

Update, 18 January:

The attack has mostly stopped, but we still have a few servers affected, so we’re not resolving this post until it’s all cleared up. As always, if you believe you’re affected or have any questions, don’t hesitate to contact our support team. Thanks for your patience.

So far, so good.

Presumably we’ve been updated

WordPress.com, I am told, gets the newest release before they turn it loose on the guys with their own servers, so presumably this is already running 2.9.1.

The only problem I had with 2.9 was some sort of cron failure — scheduling a post for time X did not necessarily translate into “this post will be published at time X” — and it never happened here.

Life goes on, and so forth.

Being Googled to death

Last night about sixish, the dreaded Googlebot dropped by the main site and scared the database into running off and hiding.

Seriously. This appeared in the error log:

[Thu Dec 31 16:04:20 2009] [error] [client] WordPress database error MySQL server has gone away for query SELECT * FROM [name of database redacted] WHERE ID = 1 LIMIT 1 made by require, require_once, include, the_post, WP_Query->the_post, setup_postdata, get_userdata

The IP in question traces right back to Google’s army of bots.

This, of course, caused everyone else’s database access to go south, and it left dozens of unfinished PHP calls sitting on the server, which is the sort of thing which annoys tech types.

Didn’t take too long to fix — thank you, JoelW — but it was a trifle unnerving just the same.