MySQL problem!! Please help!

[The Chief]

Ok, there have been two problems so far with my MySQl table while I was gone, and I recieved over 100 emails from my vBulletin board telling me that there has been an error.

Here are the 3 emails:

De: <thechief@gamebgs.com>
À: <thechief@gamebgs.com>
Objet: vBulletin Database Error!
Date: November 9, 2005 7:23 PM

Database error in vBulletin :



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



Here is another email...



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



And the last one...




Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------






Can some please help me fix this, my users can't login bvecause of this and they keep getting errors!!

Thanks!

[Psionic Vision]

This is hoster's fault. Tell him about it, as he is the only one who can fix it.

[The Chief]

Well I have contacted them, I really hope they will respond soon, I thought maybe it had something to do with vB???

[stonyarc]

Well it might be

Can you please check your /includes/config.php for this line and tell us what the value is?

If the value is 1 try setting it to 0


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------

[The Geek]

Im not a master admin, however unless you have access to your mysql conig file, your host will need to change it. It may also be some rouge script that has hijacked mysql resources. I had this once. Only solution was to periodically reboot which was a serious pain. I eventually moved servers and left behind whatever script caused it (my personal feelings was that it was with a particular email program that plugged into vb).

Personally, I would be my money its a rouge script.

[Marco van Herwaarden]

Using pconnect can also cause these symptoms.

What vB version are you using? If you look at vb.com you will see an increased number of reports on similar errors since 3.5.1