« Free spammers to a good home | Main | Emptiness »

Don't code before having coffee

I was testing a new blog-spam detection script this morning and generated the same kind of hits a spammer would do on my blog, tested the script, all great, turned the script on, left for work.

Came home from work, sat down to check my email and noticed I can't get to my server. Checked traceroute.. times out at the gateway.. hmm.. odd.. Other people can get to it, how strange.. Logged in on a console, everything is working and people are using it. Yep, sure enough, I banned my own bloody IP using my spammer detection script. Hey, at least I know it works well.

Thank god for a remote console..

Comments

And thank God for a smart friend who helped you figure it out ;-)

I would have realized it in a few minutes :)

Paranoid about exactly that, I added a whitelist to my blacklist when I first implemented it...

Haha, since you work at a bank now, you'd better not try what Michael Bolton did in Office Space - you'll surely misplace the decimal point too.

Praise remote consoles and backups. There when you need them (hopefully), and out of sight when you're working.

Don't admin a box without them (unless you want to pray a lot).

why not "multiport 25,80"?