|
Nope. I've been watching it and the site begins by taking database errors. No error code, just standard vBulletin text about try again later and the administrators have been notified. Then after about 30 seconds of errors, the site stops responding for about five minutes. My hunch is we've got a corrupted table.
There are some database maintenance routines on the bottom of the vBulletin Admin Console nav bar. You might start with those. If you've got access to the database server, the MySQL Administrator also has some table maintenance routines when you select the vBulletin catalog.
Just a hunch, but it's a place to start.
__________________
Mark Tomlinson
"I am not a trouble maker; I'm a catalyst for change."
|