Oddly, I have to report that using both IE, and Opera, I've never lost a post in the last two days, even if I get the error message after hitting "Post message."

All I've had to do is hit F5 (refresh), and the browser automatically resends the form data (Opera), or asks me if I want to resend form data (IE). Either way, the originally typed post has gone through eventually, every time.

All I've had to do is hit F5 (refresh), and the browser automatically resends the form data (Opera), or asks me if I want to resend form data (IE). Either way, the originally typed post has gone through eventually, every time.

Same here (except only IE)

I've lost a lot of posts using IE.

This might be a clue.

If get an error clicking on Message Center, I usually get multiple errors until I click on Buffistas Home. I don't get any errors clicking on Buffistas Home. That's been pretty consistent. Obviously the message center needs to go through my account, which may not be much, but...something.

October 16, 2003, 2:01 pm Gandalfe[704]: ERROR [2] mysql_connect(): User bufforg_phoenix has already more than 'max_user_connections' active connections line 78 of file /home/bufforg/public_html/classes/giles.php

There has been an error. It's of the type we call fatal. Please don't be scared. You're not the one that's going to die.

Okay, where the $$&#&(@#& are the developers?

I'm getting the errors in netscape 7.02 for the Mac.

FYI, I guess.

As an aside - I am now using the wacky-ness of the Phoenix as my own personal Magic 8 Ball. "If I get an error this time, I am going to go eat another piece of office birthday cake." "If I lose this post, it's a sign to not e-mail that guy." ETC.

Kinda fun.

Hee! I've been sorta doing the same thing, tina!

Incidentally, whenever we need to connect to the database, it's the same bit of code that does the job. That's why the error message always points to that line. So no matter what you want to do (load headers, thread lists, posts; write new posts, edit, maintain your profile) it's all got to connect to the database, and it's all going to do it through that one bit of code.

This is not to contribute to the debugging process, but just to let people know it's probably not related to the specific activity you were doing at the time. Since it's a number of connections problem, it's more likely to do with how many things needed doing just at that moment, not what they were, precisely.

---

Now to the problem. Huh. That's weird.

It's strange because it's so intermittent. If it never happened, then happened one Sunday night, I would go, hmm, spider. If it happened due to peak usage, I'd go, hmm, it's just our usage and we'll have to find a way to deal. If it happened due to feature usage, I'd look at that feature. If it happened all the time, constantly, I'd go, hmm, code.

But it's just intermittent. So I go, huh.

Are we keeping track of browsers? I'm using Galeon and I've had Hell's own time getting in here today.