Spam is evil!

Wow. Just wow. So if you see my previous entry, you will notice that I had broken my MySQL. This means that my website was down over the weekend. One of the first things I did when I got it back up was to delete all the comment spam I had. I just happened to go back into the admin interface and noticed that I received _ANOTHER_ comment spam within minutes of my WordPress being available.

Professionally I hate dealing with spam, personally I hate dealing with spam. Spam is just evil on multiple levels and I really wish people would not encourage the spammers.

Thankfully I use the Akismet plugin which takes a lot of the pain out of comment spam but it still sucks.

Broke MySQL the other day.

On an impulse I upgraded my personal server from Debian Lenny to Squeeze. All appeared to go well except MySQL didn’t want to start up and only gave the unhelpful error that starting of the MySQL process failed. It being a Friday and with better things to do (beer) I left it with the intention to fix it over the weekend.

Well, I got back to work on Monday and had completely forgotten about working on my server over the weekend thanks to regular house chores and SWOTR but looked into it again today.

A quick look showed that the old mysql-5.0 package may not have been removed completely so I apt-get remove’ed it, after which I got the following:

After this operation, 0B of additional disk space will be used.
Setting up mysql-server-5.1 (5.1.61-0+squeeze1) …
Stopping MySQL database server: mysqld.
Starting MySQL database server: mysqld . . . . . . . . . . . . . . failed!
invoke-rc.d: initscript mysql, action “start” failed.
dpkg: error processing mysql-server-5.1 (–configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.1; however:
  Package mysql-server-5.1 is not configured yet.
dpkg: error processing mysql-server (–configure):
 dependency problems – leaving unconfigured
Errors were encountered while processing:
 mysql-server-5.1
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

A quick google of the phrase “Package mysql-server-5.1 is not configured yet.” pulled up this website, the long and short is that MySQL 5.1 can not have skip-bdb in its my.cnf file. I loaded up my my.cnf file, found the line with skip-bdb and hashed it out. After a restart of the MySQL service, MySQL started up correctly.