MetaChat - Gah!

MetaChat is an informal place for MeFites to touch base and post, discuss and chatter about topics that may not belong on MetaFilter. Questions? Check the FAQ. Please note: This is important.

01 June 2005

Gah! The curse of MeFi strikes metachat. Looks like we got a bit of myximatosis for a while there but we're back now.

post by: dodgygeezer at: 11:58 | 19 comments

This is now forever burned in my memory:

MySQL error!

Error establishing a database connection!

1. Are you sure you have typed the correct user/password?
2. Are you sure that you have typed the correct hostname?
3. Are you sure that the database server is running?

I can't believe I only got a 66% on the test! I answered #1 and #2 correctly, but crapped out on #3. I should have studied.

posted by iconomy 01 June | 12:01

It's ok. There's this other place we go while MetaChat is down

posted by blag 01 June | 12:07

I was just going to say you could add a new tag line (in addtion to "We're still all in this together").

I was going to suggest the tag line "Never fear JRun errors again!" Maybe that's not such a good idea though...

posted by Doohickie 01 June | 12:18

Why not... we now fear MySQL errors instead? not JRun!

posted by kellydamnit 01 June | 12:25

Sorry about hangin' up on ya yesterday..... My parents wanted me to mow the lawn. They are *so* unfair!

posted by Doohickie 01 June | 12:56

Well that was weird.

The database server was timing out connections however I could see the db fine from the console. I mailed the support guys to see if there was a problem. I clicked the big red Optimize Now button and then everything sprang back into life - I suspect that's a coincidence though, the tables can't be that fragmented already. Just in case I'm going to run a few things on the database tonight and hopefully this won't happen again.

Shall we just say it crashed because Mefi's been down so much?

posted by dodgygeezer 01 June | 13:01

"Never fear JRun errors again!"

I concur!

posted by jrun 01 June | 13:02

It's an STD (Server Transmitted Disease).

posted by taz 01 June | 13:08

Can someone explain to me why any competently designed website would ever pass along these administrative error messages to the user?

posted by kmellis 01 June | 13:14

why? didn't you read the RFC?

posted by quonsar 01 June | 13:48

No, I did, but it wasn't helpful.

posted by kmellis 01 June | 13:59

now MeFi is down again.

posted by quonsar 01 June | 14:00

Is it just me or has there been a bunch of really crappy posts on mefi in the last 12 hours (not all of course).

posted by peacay 01 June | 14:03

Matt needs to rearchitect the site and build it from the ground up to be robust. He's resistant to do it because it'd be more trouble or money than he can afford; but also, I think, because he's drunk the CF koolaid and believes that the status quo should be sufficient.

posted by kmellis 01 June | 14:03

I have no idea, since my connection was just refused - again.

posted by mygothlaundry 01 June | 14:04

he pulls out a bandaid when surgery is needed

posted by peacay 01 June | 14:05

That CF koolaid is some pretty heady stuff, lemme tell you. But then, I tried drinking that before Python and Ruby were mixed up.

posted by loquacious 01 June | 17:12

I like pie.

posted by bshort 01 June | 19:51

1. Are you sure you have typed the correct user/password?
2. Are you sure that you have typed the correct hostname?
3. Are you sure that the database server is running?

How can you be sure of anything the way the word is today? All I know is, everything would work better if quonsar didn't store his machine tools in the giraffe.

posted by wendell 02 June | 01:30

← You've been waiting for this... || How many MeFites, do you think, →

HOME || REGISTER || LOGIN