Too busy?
Thread Starter
|
Senior Member
Joined: Jul 1999
Posts: 3,367
Likes: 0
From: Illinois
Too busy?
Lately I have been getting this prompt when trying to log on...
vBulletin Message
Sorry, but the server is too busy to handle your request at the moment.
Please wait at least 30 seconds before clicking on the "RELOAD" button or try again in a few minutes.
Is the server really too busy?
vBulletin Message
Sorry, but the server is too busy to handle your request at the moment.
Please wait at least 30 seconds before clicking on the "RELOAD" button or try again in a few minutes.
Is the server really too busy?
F150online
Founder
Founder
Joined: Nov 1996
Posts: 3,008
Likes: 0
From: Roswell, GA USA
There are two reasons that you would get this message:
1) The load on the server, ie. how hard the processors are actually working, is very high. While this happens periodically, I would not say it is the most likely reason you see the message. Even with 900+ "users" on right now, the load is well under 2. (dual Xeon processors for those that want to know)
2) The number of current sessions on the forums has exceeded 1000. To limit the potential load on the database from too many users, the warning message comes up. This is more likely at the moment, as we have set simultaneous user records several time during the past few days. The site appears to be getting hammered by spiders at the moment. I've upped the number to 1250 for the time being.
We've also had a couple of longer term outages in the past few days, one of them due to app server corruption and another due to networking issues this afternoon.
1) The load on the server, ie. how hard the processors are actually working, is very high. While this happens periodically, I would not say it is the most likely reason you see the message. Even with 900+ "users" on right now, the load is well under 2. (dual Xeon processors for those that want to know)
2) The number of current sessions on the forums has exceeded 1000. To limit the potential load on the database from too many users, the warning message comes up. This is more likely at the moment, as we have set simultaneous user records several time during the past few days. The site appears to be getting hammered by spiders at the moment. I've upped the number to 1250 for the time being.
We've also had a couple of longer term outages in the past few days, one of them due to app server corruption and another due to networking issues this afternoon.