We're back up

[Gantry]

But I may take it down for a few minutes later on, have a flaky network jack...

[TβG]

how about you do that at 4 am instead of during rush hour.    check the tubes for any clogging.

[broiler]

Remember how you once asked me how a bullet comes out of a gun

[Shooty]

Ball bearings.

[Big Hath]

can I step away from the ledge now?

[Gantry]

the jack works fine until you touch the cable.  So I guess it can wait, doubly so since our punch down tool sucks donkey balls.  Consider dee-nee to be up all day today!

[Guy Smiley]

can I step away from the ledge now?

I wish you would step back from that ledge... my friend...

[BeeJay]

I'm not sure what's worse, Nacho's Will and Grace reference or quoting Third Eye Blind.

[TβG]

nacho's.... by far.

[BDawk]

the jack works fine until you touch the cable.  So I guess it can wait, doubly so since our punch down tool sucks donkey balls.  Consider dee-nee to be up all day today!

How about you just don't touch the fucking cable

[malnuboy]

whats the matter with the punch down tool.

[Gantry]

The blade is all dull and we bought the wrong blade to replace it.  But we got our new punch down tool today, so the jack may be fixed tomorrow.  Expect 20-45 seconds of downtime during working hours.  When that happense will be a surprise...

[Big Hath]

the longest 20-45 seconds of my life

[moses]

I'm not sure what's worse, Nacho's Will and Grace reference or quoting Third Eye Blind or the fact i recognized the Will and Grace reference.

[Gantry]

The blade is all dull and we bought the wrong blade to replace it.  But we got our new punch down tool today, so the jack may be fixed tomorrow.  Expect 20-45 seconds of downtime during working hours.  When that happense will be a surprise...

Jack rewired, downtime was a little longer than expected.  Sorry...

[Gantry]

Nasty little database problem, "kill -9" to the mysqld process probably isn't the best way to handle that...

wulf - when you paged me about a db issue last week, what happened?  This time, the mysqld was using a ton of cpu and I couldn't stop it or reboot or anything.

[nightwulf]

wulf - when you paged me about a db issue last week, what happened?  This time, the mysqld was using a ton of cpu and I couldn't stop it or reboot or anything.

No idea. Just tried to connect and couldn't, ssh'ed in and ran top and found mysqld going haywire.

No idea about this one either. I tried looking at the forums and couldn't connect, other PCs on your network were up but not this one, so I tried ssh'ing in. Saw you online, sent a write.

[Gantry]

I figured mysqld was doing some sort of maintenance (their logs are worthless, that or I have to up the level) but it was slow/unaccessible for a good 15 minutes so I killed it...

I kept httpd & mysqld down during the db check to speed it up.  Only took about 20 minutes this time...