Have they really done much try and fix our problem? Other than fixing some parameters on one occasion, and the auto-overload message we get now, what changes have they made?

Mayhaps that's where the host is coming from.

And that makes even more sense.

I guess I'm just worried because that seems to indicate that we'll never have a home of our own. I mean, if that's going to be the case here, and everywhere we go, how will we ever solve our problems?

They met on AIM with Kristen several times, trying to solve the problem. I'd host a site with them, if I were using a different code. It just seems to be the MySQL that's stuck in their bellies. Or, I'm on crack, because i really know JACK CRAP about coding.

Somewhere
We'll find a new way of living
We'll find a way of forgiving
Somewhere
There's a place for us
A time and place for us
Hold my hand
And we're halfway there
Hold my hand
And I'll take you there
Somehow
Someday
Somewhere

Well, I think Fangeek now has enough info for us to be able to say to a host, "these are our problems, can you help us?"

I understand both Nutty's metaphor, and Allyson's, and even accept it. Here comes the but... But, I see Sean's point. What I would like to understand (and perhaps this is out there, and I already should understand it) is the following.

Does IH (that's our ISP, right?) already know the stuff that Tom Scola seems to have just discovered, and if they do, are they refuting it? Perhaps (and if this isn't possible, fine) if we contacted them with this (what seems to me to be) new information, they wouldn't feel we were so problem-childish, and would have a forehead slapping moment of, "Oh! So that's the problem. Yes, we'll just push these 5 buttons here. All set now."

Who is our host, now?

Rob, what do you make of the inability to open two mysql command line connections at once?

I think we've leaked all but one of our allowed connections and we're sharing it. The command line host keeps a connection open permanently, so while you were using it there were no more connections available to use.

That's just a guess, I have to dig down into the MySQL source code again to find out just how max_user_connections is enforced.

I think we've leaked all but one of our allowed connections and we're sharing it.

If that's the case, then they should be showing up in the SHOW PROCESSLIST query.

I think we've leaked all but one of our allowed connections and we're sharing it.

Problem is (well, okay, a bunch of problems) that 24 hours off, and the 99 connections didn't unleak.

So as bad as our code may be -- mysqld is bogarting like crazy.