Server Upgraded, Report Errors Here

Play some Funky Music..What else?

 

That usually happens when the page doesn't load all it's data?
Do you have anything running in the background?

It might be time to do some maintenance. Have you checked for spyware?

 

Ahhh sooo....wise one, I'll give it a shot. Keep the whiskey cold and the cigars ready, I'll be back.

 

Well, Done. Upgraded browser to IE 8 . Trucker home page looks better but my rr track icon is still leaching into the header a lil bit.

No biggie and thanks.

 

I moved to Chrome. It loads faster and performs better than IE. I was a die hard IE fan, try Chrome you'll like it. I haven't looked back.

It has all the same features with the same favorites bar plus you have a built in spell check which makes you look smart and a password and auto form fill which is handy.

 

Reloading doesn't help.Only get following message if/when I am logged in.vBulletin MessageThe server is too busy at the moment. Please try again later.Cleared cache, cookies and history. Nothing is helping. I can navigate just fine if logged out. Took me 1/2 hour just to get to the point where I can type this message and even then not sure if it will post when I hit submit.

 

Still getting:vBulletin MessageThe server is too busy at the moment. Please try again later.Reloading and clearing cache, cookies, history and temporary internet files doesn't help

 

The new server smell is starting to fade.

 

After some research, I discovered that there really isn't a problem with the server at all (it wasn't "too" busy). It turns out that the default setting in vBulletin is very low, and may trigger this message depending on the server's CPU. Here's how to fix it:Go to:vBulletin Options > Server Settings and Optimization Options > *NIX Server Load LimitBy setting the option to a higher CPU usage percentage (10 or higher), you can keep the functionality of the warning and only trigger this message under "high" load times. If you're running more than one site or server app on your server, then it's possible that this function would be better off disabled with a '0'.