|
It is a work in progress. I have been working with our hosting company and finally dug deep enough to find the root cause. They found the variable which sets what vBulletin expects for the load limit is named "loadlimit". When searching through the code they found the operations which set this flag to "true".
Basically the code says if the operating system is NOT Windows, and if the 'loadlimit' value is greater than zero, and if the 'loadavg' value is greater than the 'loadlimit' value, then set the 'servertoobusy' flag to 'true'. This flag controls whether the "too busy" message is displayed on the site. The interesting thing is the 'loadlimit' value is set in the database to '0', meaning this feature "should" be disabled.
So it seems to be an issue with vBulletin interpreting the environment, or a vbulletin issue in general. For now, I have manually turned off the load limit process in vBulletin. We will see how things run or if this creates other issues. Server load will be monitored on the server side.
|