IE 5.2 on Mac System 10.2.3 here, and I just ran into a couple myself.
Zoe: I thought you wanted to spend more time off-ship this visit. Wash: Out there is seems like it's all fancy parties. I like our party better. The dress code is easier and I know all the steps.
'Shindig'
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.
Matt the Bruins fan - Oct 16, 2003 8:08:09 pm PDT #5269 of 10000
"I remember when they eventually introduced that drug kingpin who murdered people and smuggled drugs inside snakes and I was like 'Finally. A normal person.'” —RahvinDragand
RobertH - Oct 16, 2003 8:30:51 pm PDT #5270 of 10000
Disaffected college student
I don't get any errors clicking on Buffistas Home. That's been pretty consistent.
Sadly, I have gotten a couple of the errors loading the home page.
DXMachina - Oct 17, 2003 2:24:17 am PDT #5271 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
Still getting the error at 7:24 a.m. on the east coast. Man, the posting volume is just brutal this time of day.
juliana - Oct 17, 2003 4:44:05 am PDT #5272 of 10000
I’d be lying if I didn’t say that I miss them all tonight…
Man, the posting volume is just brutal this time of day.
Snerk.
I get the error message in Mozilla and IE, at completely random times of day, with random frequency. It would seem that it's not a browser issue.
However, that's all I've got in the way of mildly useful info, so I'ma go back to lurking now.....
Typo Boy - Oct 17, 2003 8:46:32 am PDT #5273 of 10000
Calli: My people have a saying. A man who trusts can never be betrayed, only mistaken.Avon: Life expectancy among your people must be extremely short.
Again, to repeat what has been said, it is unlikely to be browser specific. (That is this problem probably has nothing to do with what browser you are using.) And, as has also been said, it is unlikely to be specific to the activity you are doing. Whether you are reading a thread, posting or whatever should not affect it.
1) If it is a spider, then it has zero to do with regular user activity.
2) We see this happening during comparatively light activity - lighter than other times when it does not happen. This means that if it is not a spider, but in the code or host configuration, it must be some specific type of connection is causing a problem or not being released. At this point the code has been gone over pretty throughly, so it seems that spider is still the most likely, with host the second most probable, and obscure code problems still not impossible, but definitely third in probability.
DXMachina - Oct 17, 2003 8:59:40 am PDT #5274 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
Yeah, I agree with Gar. I don't know what we can about a spider, but we can ask if they've changed any settings on the server.
(After having first post eaten) Because bored now.
Consuela - Oct 17, 2003 9:36:17 am PDT #5275 of 10000
We are Buffistas. This isn't our first apocalypse. -- Pix
I just got errors twice while trying to connect to my Message Center.
Consuela - Oct 17, 2003 10:02:27 am PDT #5276 of 10000
We are Buffistas. This isn't our first apocalypse. -- Pix
I'm having a hell of a time reading anything, much less posting.
Is anyone else having this much trouble? And do we have any information from our hosts as to what's causing the connections not to close?
Sean K - Oct 17, 2003 10:04:28 am PDT #5277 of 10000
You can't leave me to my own devices; my devices are Nap and Eat. -Zenkitty
I'm not having enough trouble to make posting or reading difficult, but I am getting the error message fairly often.
Nutty - Oct 17, 2003 11:23:33 am PDT #5278 of 10000
"Mister Spock is on his fanny, sir. Reports heavy damage."
It comes and it goes, for me. Three errors in a row, and then no problems for an hour.
I was reading something else and remembered that this same problem happened 3 weeks ago. Back before, our server usage problem was such that it was invisible until the number of open connections racked up enough for us to go into the red WARNING section of the dial. And it was, like, every 3 months, or something like that: build up, crash, lose database bits, restart (and reset the connection counter to 0), and we're fine for another 3 months.
So, this pattern is different -- for one thing, we haven't been taken completely offline at any time, to my knowledge -- but we are experiencing a build-up of errors server-usage-related errors, a peak, and then a slow die-off of those errors. Every 3 weeks, so far, since the code got adjusted and the people Kristen talks to installed the Magic Doohickey that times out connections.
I'm just thinking out loud, trying to help construct this all in my mind, in hopes it's a help. What is there about the installation of the Magic Doohickey, or the change in code, that could perpetuate the cyclical problem, on a smaller time- and disaster-scale? I mean, as disasters go, I like small ones, but I prefer no ones.