There are two pages called when posting. The first is what does the actual posting (it's called something like post.php), the second is the refreshed thread page with your new post. If you get the error while the system is trying to get the first page, it doesn't post. If you get the error on the second, it means it posted, but couldn't refresh the page. You can tell what happened by looking at the URL.
I hope you don't think that I just come over for the spells and everything. I mean, I really like just talking and hanging out with you and stuff.
Willow ,'First Date'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
DXMachina - Oct 16, 2003 10:40:36 am PDT #5256 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
Sean K - Oct 16, 2003 10:48:33 am PDT #5257 of 10000
You can't leave me to my own devices; my devices are Nap and Eat. -Zenkitty
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.
JenP - Oct 16, 2003 10:49:53 am PDT #5258 of 10000
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)
Deena - Oct 16, 2003 11:01:19 am PDT #5259 of 10000
How are you me? You need to stop that. Only I can be me. ~Kara
I've lost a lot of posts using IE.
DavidS - Oct 16, 2003 11:22:14 am PDT #5260 of 10000
"Look, son, if it's good enough for Shirley Bassey, it's good enough for you."
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.
Gandalfe - Oct 16, 2003 12:04:05 pm PDT #5261 of 10000
The generation that could change the world is still looking for its car keys.
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?
DCJensen - Oct 16, 2003 12:27:08 pm PDT #5262 of 10000
All is well that ends in pizza.
I'm getting the errors in netscape 7.02 for the Mac.
FYI, I guess.
tina f. - Oct 16, 2003 12:32:29 pm PDT #5263 of 10000
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.
lori - Oct 16, 2003 12:45:56 pm PDT #5264 of 10000
Hee! I've been sorta doing the same thing, tina!
Liese S. - Oct 16, 2003 12:50:27 pm PDT #5265 of 10000
"Faded like the lilac, he thought."
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.