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.
We seemed to have calmed down. [nevermind.]
Just got a couple more now. I'm using Opera 6 or 7, depending what machine I'm on.
IE 5.2 on Mac System 10.2.3 here, and I just ran into a couple myself.
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.
Still getting the error at 7:24 a.m. on the east coast. Man, the posting volume is just brutal this time of day.
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.....
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.
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.