It is our fault in the sense that we selected MySQL for our system, which means we would have this problem where ever we were hosted.

No, we'd only have this problem at places that use the MySQL per-user connection limit as a way of limiting server resource use for shared hosting. Not all hosts do it that way.

Netgate just gives you a CPU/memory limit and you get an error from in your browser if an attempt to load a page exceeds the account limits.

Dreamhost has this conuries system, where you don't have a limit but you pay more a a lot extra if you exceed your allocation. At our rate of use we'd be their favorite customer, but that's another issue.

So moving to another shared hosting situation isn't necessarily going to put us in this situation again, but I think the stress for the stompies would be much less with a dedicated server. They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.

They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.

And, that will cost more money, but not necessarily 1000% more.

Just heard back from Steven. They've scheduled a shutdown/restart for 11:00 pm PST tonight so minimize the impact on other sites' traffic.

Steven's the man!

1000% increase, actually.

Frelling maths. Thanks, Jon.

I love the new error message.

Oh, I was just running over to giggle over the new error message. Love it!

homminnigobbeddymoo. ptui! ptui!

There. That should fix it.

I got a new error message. I love the Geekies.

t x-post

Thanks. I just realised it was doing *two* checks to get all that error message out, so I trapped for the specific string. It won't help the problem any, but the page should load microscopically quicker.

And it made me feel a little better.

Shame we can't have a bunch of random error messages, because that would be cool.

No, I'm not seriously suggesting it.