This is so frustrating. Traffic seems pretty slow, (though, hey, what do I know?) so it seems odd to me that we're using up all the connections.
So. Frustrating.
Do you know what else has blood in it? Blood.
Spike ,'Sleeper'
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.
Allyson - Oct 20, 2003 5:41:36 am PDT #5319 of 10000
Wait, is this real-world child support, where the money goes to buy food for the kids, or MRA fantasyland child support where the women just buy Ferraris and cocaine? -Jessica
Theodosia - Oct 20, 2003 5:45:13 am PDT #5320 of 10000
'we all walk this earth feeling we are frauds. The trick is to be grateful and hope the caper doesn't end any time soon"
Got my first two errors of the morning just now.
Megan E. - Oct 20, 2003 5:50:30 am PDT #5321 of 10000
The only time I got an error was when I hit "next". Hitting "read new" did not result in errors.
Tom Scola - Oct 20, 2003 5:53:21 am PDT #5322 of 10000
Remember that the frontier of the Rebellion is everywhere. And even the smallest act of insurrection pushes our lines forward.
Stop me if you've done this already, but can you connect to mysql from the command-line and mail me the output to the following queries?
- SHOW VARIABLES LIKE 'MAX%';
- SHOW PROCESSLIST;
Cindy - Oct 20, 2003 6:24:43 am PDT #5323 of 10000
Nobody
ita changed that after we started getting the errors, but I'm all for changing it back just for the sake of ruling things out completely, one variable at a time.
I'm sorry DX, I'm not sure which change you mean. Do you mean when she made the html coding that was showing up in the browser window line blinvisible? There were quite a few changes going on to that thread title coding, in the hours leading up to the wonkiness. When I skimmed back, it looks like we put up the thread, then the code was broken and she and Jon fixed that, and then you & Fred got the first errors, but most likely I missed something. Here's what I see wrt chronology:
First Natter 17 Post: Oct 14, 2003 6:38:25 am PDT #1
Natter won't load for Beverly: Beverly "Buffistas Building a Better Board" Oct 14, 2003 6:40:29 am PDT
ita fixes strangely broken title: ita "Buffistas Building a Better Board" Oct 14, 2003 6:43:24 am PDT (she notes she fixed it in an edited in comment at 6:43:51am)
Jon also notes he fixed it: Jon B. "Buffistas Building a Better Board" Oct 14, 2003 6:46:21 am PDT
Jon fixes it again: Jon B. "Buffistas Building a Better Board" Oct 14, 2003 6:54:43 am PDT
DX gets the first noted "more than 'max_user_connections'" message: DXMachina "Buffistas Building a Better Board" Oct 15, 2003 8:19:24 am PDT
(DX's error message above cites 8:17 am as the error time). I know Fred Pete got an error too, but either he reported it elsewhere, or I'm missing it in BBaBB and Bureaucracy. ita notes Fred got the error too, and also that she "changed the code to strip tags from the t title tag.": ita "Buffistas Building a Better Board" Oct 15, 2003 9:58:01 am PDT
The error message onslaught starts in earnest: Jess PMoon "Buffistas Building a Better Board" Oct 15, 2003 12:06:11 pm PDT
Jon B. - Oct 20, 2003 6:30:15 am PDT #5324 of 10000
A turkey in every toilet -- only in America!
While I hate to rule anything out, I can say with confidence that the thread title is not not cause of the wonkiness.
Rob - Oct 20, 2003 6:30:29 am PDT #5325 of 10000
ita, I bet Tom would love to see the output from that MySQL status script I gave you the other day.
DXMachina - Oct 20, 2003 6:33:25 am PDT #5326 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
Cindy, I meant when ita changed the coding for the Title Bar, which involved changing the code for the page. The other changes, that happened earlier, had to do with the format we followed in entering a particular piece of data, i.e., the title for Natter 17.
Cindy - Oct 20, 2003 6:36:29 am PDT #5327 of 10000
Nobody
Cindy, I meant when ita changed the coding for the Title Bar, which involved changing the code for the page. The other changes, that happened earlier had to do with the format we followed in entering a particular piece of data, i.e., the title for Natter 17.
Thanks, DX. Sorry for the slowness. Okay, well, it was just a stab in the dark. The thread header stuff was the only change (and different than usual kind of change) I could think of. I don't know how it works, so I didn't know if by using htmlified font and funky characters in the title, it was causing some other connection to be opened, or something.
DXMachina - Oct 20, 2003 6:44:27 am PDT #5328 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
I don't know how it works, so I didn't know if by using htmlified font and funky characters in the title, it was causing some other connection to be opened, or something.
The title, as stored in the database, doesn't actually contain the special characters, only the codes for the special characters. The translation doesn't actually occur until it reaches the browser window, so it's hard to see how it could be causing connection errors.
(The problems we had when we opened the thread were sort of the result of this. When I went to open the previously created thread, the maintain threads page translated the codes to the special characters, then when I unchecked the "closed" flag to open the thread and hit submit, the page submitted the special characters as the revised title data, with hilarity ensuing until Jon went in and fixed it.)