Dedicated server with lots of resources, RAM, disk space, and bandwidth.
Three vBulletin 4.1.10 forums running, two with vbstopforumspam installed.
ONLY ONE of these (and not the most active one) has lately been throwing frequent errors like the following (these started just 2 or 3 weeks ago - prior to that, all was fine):
Quote:
Database error in vBulletin 4.1.10:
Invalid SQL:
INSERT INTO vbstopforumspam_log (date, ipaddress, email, username, message, blocked, userhash) VALUES (now(), '91.207.5.126' , 'kinotru@gmail.com', 'UsasseSaf', 'Result on field ip - 91.207.5.126 [REMOTEERR] Unverfied but allowed by policy', 0, 'b70728cf449d36b0ad5f2f7f713814ec');;
MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Monday, February 27th 2012 @ 08:35:37 AM
Error Date : Monday, February 27th 2012 @ 08:36:07 AM
Script : http://domain.com/register.php?do=addmember
Referrer : http://domain.com/register.php
IP Address : 91.207.5.126
Username : UsasseSaf
Classname : vB_Database
|
Quote:
Database error in vBulletin 4.1.10:
Invalid SQL:
INSERT INTO vbstopforumspam_log (date, ipaddress, email, username, message,
blocked, userhash) VALUES (now(), '72.64.146.136' , 'sunnie2088@gmail.com',
'usbflashdriveppx', 'Result on field ip - 72.64.146.136 [REMOTEERR]
Unverfied but allowed by policy', 0, '781be45ede1bf941343ca68fd875b7ec');;
MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Monday, February 27th 2012 @ 05:53:45 AM
Error Date : Monday, February 27th 2012 @ 05:54:15 AM
Script : http://domain.com/register.php?do=addmember
Referrer : http://domain.com/register.php
IP Address : 72.64.146.136
Username : usbflashdriveppx
Classname : vB_Database
|
Normal registrations are still succeeding on that forum and as noted it is not a very active forum as yet. All of the errors are for usernames that look spammy but I have it set so that only email and IP are checked against the database, so it's not the username that's triggering this.
Also, despite the "MySQL server has gone away", there are no MySQL errors coming from several other sites on that server using MySQL incoluding at the same time that these errors are appearing, so the error seems to be misleading, i.e., it seems it's the invalid SQL statement that is throwing the error, not MySQL crashing.
Any idea what is causing this?