hardcore crashing 28 December, 2005 at 4:35 pm
i ended up at the office briefly this afternoon. was doing some stuff, and checked one of the servers and … no response
so i check the window i have up for monitoring it (a holdover from a previous build where part of hte pipeline broke a lot, so i would watch for that on this system so i could fix it before it became an issue) … that connection crashed. so i reconnect, but not getting anywhere
so i end up at the office, where apparently my desktop’s wireless kbd needs new batteries. makes it harder to check things from there :o
down to the lab, bring up console … bring up console … check all the other switches on the kvm and all the other active connections are, in fact, active. go back, bring up console …
nothing. nada. zip. zilch. it’s like the screen is in saver mode, but not waking up. which usually means kernel crash (wakeup is a signal from the system, triggered by an internal event or a keystroke … except the keystroke isn’t passing to wakeup b/c the system isn’t there anymore)
reboot it. reboots itself a few times, then has me manually check the drives for errors. but it finally all came back up. works fine, too, it seems, now.
no idea what caused a crash like that. i’m guessing a brute force attack/dos on the sshd (seeign as thats the only port actually listening on that machine). so i locked ssh to only allow my two regular login points. meant to do that a while ago, but i was working on a tool to allow open ssh and lockouts for password attacks. never finished it, oops :)
If it’s any better than sshdfilter let me know…