Common MySQL Error Messages 
A comprehensive list of MySQL error codes can be found in the MySQL Documentation. Here are some of the more common ones that can affect your vBulletin installation.

OS Error Code 11: Cannot create thread
This is an out of memory error. The operating system does not have enough memory to create a new process for MySQL to perform the query. You should increase the amount of memory available to MySQL by editing the MY.CNF file.

OS Error Code 13: Permission denied
You do not have permission to write to a directory. Most commonly the temporary files directory. Create a directory in your User Home directory on the server and chmod it 777. If this does not resolve the issue then you must contact your host and have them fix your permissions.

OS Error code 28: No space left on device
Either the swap, a partition, temp directory or hard drive on the web server is out of space or doesn't have enough space to complete the above operation.

This is a server issue, you need to contact your hosting provider to get more space to write to. I advice you to shut down your forum to prevent more errors or data loss. You can upload the tools.php file from the vbulletin .zip file do_not_upload/ folder into your forumdir/admincp/ directory and run it through the browser, there's a switch there to turn your forum on/off.

MySQL error code 126: Index file is crashed / Wrong file format
MySQL error code 127: Record-file is crashed
MySQL error code 132: Old database file
MySQL error code 134: Record was already deleted (or record file crashed)
MySQL error code 135: No more room in record file
MySQL error code 136: No more room in index file
MySQL error code 141: Duplicate unique key or constraint on write or update
MySQL error code 144: Table is crashed and last repair failed
MySQL error code 145: Table was marked as crashed and should be repaired

These error codes all have the same solution. They specify that something has gone wrong with your data. You should run optimize & repair on your database tables. You can upload the tools.php file from the vbulletin .zip file do_not_upload/ folder into your forumdir/admincp/ directory and run it through the browser, there's a switch there to run optimize and repair. Run it a few times for best result.

For more information on repairing your database please view the MySQL documentation at:

Socket Connection Error
This most commonly looks like this:
mysql_connect(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' 
(2) /home/exampledomain/public_html/forums/includes/class_core.php on line 273
This error means either:
1. The info in your config.php file is wrong (in which case your forums wouldn't work at all), or
2. MySQL crashed, it's not running or it can't find the socket. You need to contact your host about this. Here is more info on this error:

mysql_connect(): Too many connections
The server has maxed out the number of MySQL connections it allows. You can try turning persistent connections off by adding this to your config.php:
$config['MasterServer']['usepconnect'] = 0
But if you still have problems after that, you will need ask your host to raise the maximum number of connections they allow.

Here is more info on that error:

Error code 1064: MySQL Parse Error (error in SQL syntax
SQL parse errors are mostly caused by installed modifications. In order to test this temporarily disable all products and plugins by adding this line to your config.php file under <?php:
Error code 1153: Got a packet bigger than 'max_allowed_packet' bytes
It means that a query is sent that is larger than your host allows for.

MySQL Error : Got a packet bigger than 'max_allowed_packet' bytes

You need to ask your host to increase the 'max_allowed_packet' variable in the my.cnf file and restart MySQL. The default is 1Mb, but most hosts run 8-16 Mb without problems.

More info here:

Copyright © 2021 MH Sub I, LLC dba vBulletin. All rights reserved. vBulletin® is a registered trademark of MH Sub I, LLC dba vBulletin.