There goes another one

Oops, another pending shockwave has turned into an explosion.
Yet another 'well, we noticed, and would have sorted it, but didn't have the time'.

Is it good or bad that when you stop feeling concerned that you screwed up?
(By virtue of the fact that I'm the only one who actively bothers checking this particular backup server, I was the only one who could have noticed, and therefore should have done something about it.)

Server splattage

There's a server in Knutsford.
It's gone 'sproinggg' and is no longer working.
Normally, we would assign this to $collegue, who would probably sort it in short order.
Unfortunately, he left on friday, which is what these recent job adverts are about.

There is a temptation to close this call with "your admin left, because you pissed him off, and now you're hosed. HAHAHAHAHAHAHAHA!"

That server

Well, the problem:
Server is up, oracle is running.
Disks are mirrored, but no one can login (telnet, ssh, rsh, or on the console).

Information to hand is from systems monitoring - out of date:

( geeky stuff )

Hopefully that'll fix it, so this afternoon, we find out if my remote best guess diagnosis is correct. If it is, I get to do the 'wahoo I'm fantastic dance'. If it's not, I get to shrug and do the 'well, you can't even log in to the damn box, and i'm 100 miles away, what do you expect' fob off.

Someone snitched?

Friday's Dilbert
Saturday's Dilbert

Sometimes Dilbert is just scarily apt.

About that server...

About that server, mentioned in this post.
Turns out my diagnosis was correct.
S4 had been carved as swap, but mounted from each disk, rather than mirrored.
However the fix was simply to reseat and reboot the drive in question, rather than actually having to change any config.

I do so love being right.