downtime

By anders pearson 27 Jan 2003

this weekend’s downtime was brought to you by Microsoft SQL Server.

apparently a few machines in the server room were infected with <a href=”http://slashdot.org/article.pl?sid=03/01/25/1245206&mode=nested&tid=109”>the worm</a> and generated so much traffic that the network people had to reboot the router sometime on saturday. this, unfortunately, meant that i needed to refresh the network interface on the server for it to reconnect to the network. so it was stuck until i could come in this morning, log in to the console and type ‘ifup eth0’. once bitten, i now have a script that runs every hour and runs that if it can’t find the network so this shouldn’t be a problem again.

still, i’m sick and tired of being fucked by microsoft worms. i haven’t run any MS code on any of my machines for about 3 years now. i keep up to date on security patches on the stuff i do run. and still, every few months i have to deal with the fallout of Nimda, or Code Red, or Melissa, or whatever that week’s worm is.

ok, i guess it isn’t fair to blame microsoft. the vulnerability that this worm exploited was fixed in a patch from last june. if people would actually apply their security patches, these things pretty much wouldn’t happen.

Tags: venting sql server worm downtime