To follow up from Matts post yesterday here’s an update;
Matt did some tracing through the logs and the bits he pasted to me looked suspiciously like Code Red problems. Interesting how the media spin on this is how brilliant Microsoft has been when in reality its their crappy code that caused the problem in the first place. But still – we’re not using IIS (and you couldn’t pay us enough to use it) so Code Red is not infecting us.
Just for the record, I try to keep up with goings on at BugTraq and SecurityFocus, so hopefully things such as that won’t ever affect us, except in ways we can’t avoid (such as the hundreds of hits we’ve received by various IIS machines searching for others to infect).
On a more personal note, this is what happens when you get clueless f..kwits running internet servers. Thanks Microsoft, for making it easy for everyone to run web and other internet servers… Its a bit like allowing anyone to make and sell cars, wonder what the state of the highway would be then? *sigh* Half the domains don’t even have a hostmaster or postmaster address you can write to in event of trouble any more!
Anyway, the REAL reason the system was running like a pig yesterday was nothing at all to do with Code Red – though if we were just like any other company it would be a fantastic excuse – but actually because our Jabber server decided that 300M of memory should be sufficient for its needs and to hell with what anything else wanted to do… I’ve taught it the error of its ways and will be putting in place extra checks on the system to catch it in future.
Sorry for that, but to re-iterate what Matt says, PLEASE let us know if you notice something is up. We probably won’t fix it if we don’t know about it!