The server is too busy at the moment. Please try again later.

[yamaha_rider619]

I also had a database error, then serve too busy within the last hour.

[devilfluff]

All day? This is the kind of problem that we are just recovering from... We really need to get whatever the problem is fixed.

[Admiral AGbar]

I didn't know what to do at work today. Without clubwrx I actually...worked.

Sent from my PC36100 using Tapatalk

[xFalleNx]

It was really bad today

[Redline730]

passed weekend i was getting it every time i tried logging on... between the hours of 2200 est and 0300 saturday night

[SamXp]

Server busy most of yesterday and this morning. Just now able to get on for the first time today.

[djclue8713]

Today was the worst it's ever been for me. Just able to sign on.

[rage-wrx]

It's usually a lot worse on Fridays

[xFalleNx]

This is happening way too often and actually getting really annoying.

[Heide264]

For what it's worth.. probably beating a dead horse... But I'm still getting it most days in the late morning 8-10am (Eastern Standard Time)

[yamaha_rider619]

I have been getting it a lot lately too. I sometimes get it throughout the day and a lot at night.

[shadowpr]

maybe an admin can chime in?????

[MagnumXL]

From what I've read, there seems to be a bug in the VBulletin software that supposedly can be resolved with a change to *NIX Server Load Limit. At least that fixed the problem for most of the forums that had it that asked on the VBulletin forums about the problem.

[RayfieldsWRX]

An admin is happy to chime in, but there are a very limited number of folks that actually have access to the box.
As far as the *NIX Server Load Limit, as I said before it's set at 7. Did the vBulletin info that you read suggest a value? Some folks have turned it off by setting it to 0, unless I'm wrong.

[MagnumXL]

Actually, most in that thread disabled it (i.e. zero) at the time, but looking again, that thread is a few years old so the error in question (V4 of Vbulletin, I think) is probably corrected by now (don't know which version you're using here).

By its intended function, I gather it's a trade-off of board loading speed versus the number of users before it simply won't allow you to view anything (i.e. when you get that message, you can't even check to see if any replies are in subscribed threads, etc.). I imagine it would be a matter of finding an acceptable speed versus a given number of users. In other words, if it loads reasonably fast with 12 users on, why limit it to 7. OTOH, if it crawls at 12, then perhaps 7 is reasonable. When I get the error, the page with the error on it comes up instantly which makes me think it's not exactly crawling at 7. I figured it was more of a glitch since the last time I got the error, I got it for like 12 hours straight (although I didn't sit there and try to get on every 10 minutes or anything, but rather every time I did try with over an hour in-between, it kept giving the same error and oddly, it started doing it in the middle of the night (hard to believe the forum had that much activity constantly given I usually have no trouble at all).

I haven't seen it happen in over a week now, though.