Database Driver Errors
Submitted Mark, Feb 04 2010 11:51 AM | Last updated Feb 08 2011 10:23 PM
SQL Error Logs
When you see a driver error message this means that IP.Board is having trouble communicating with your database. When this happens, IP.Board will log the error in ./cache/sql_error_log_MM_DD.cgi where MM and DD are the month and day the log was generated. If you look at the end of this text file it will show you the most recent log entries being generated. From there you can learn what to do.
Note that in version IP.Board 3.1.4, a feature was introduced to allow you to view the last few kilobytes of each existing error log. Go to ACP -> Logs -> SQL Error Logs. On the right, any existing logs in the ./cache directory will be listed. Clicking any entry will show you the last few enties in it. To view the entire log, you'd need to connect with FTP and download the relevant file. They can be opened in any text editor.
Missing Columns
Though rare, sometimes an upgrade can miss creating a column in the database and this will generate an error. Before submitting a support ticket, first try logging into the AdminCP, going to Support tab, and then using the database checker to see if IP.Board can diagnose and fix the problem itself.
Crashed Tables
IP.Board by default uses a MySQL database to store data in. MySQL database tables can under some circumstances crash causing a repair to be necessary.
If this happens, your community will display a driver error, and a message will appear in the database error log that says something along the lines of "Table is Marked as Crashed and Should be Repaired".
It is important to understand that while there are several reasons that a table crash might occur, it is always caused by the server. For example it can be caused by the server being improperly shut down or restarted, hard disk drive failure/errors, improper repair attempts on a database, etc.
IP.Board cannot in itself cause a table to crash.
Repairing a crashed table is a simple process, however we strongly recommend that if you experience a crashed table you should contact your hosting provider and ask them to repair it. Attempting a repair yourself could cause further complications, and it is important regardless to report the issue to your hosting provider so that they can investigate and resolve any server issues which might cause the problem to happen again.
If you experience a crash on the sessions table, due to the nature of the way IP.Board interacts with the table, you may wish to change the table to memory storage. If you are unsure if this is necessary or how to do this, you should discuss this with your hosting provider.
MySQL server has gone away
This error means that, while IP.Board was trying to query your MySQL database, the server disconnected from the request. There is nothing in IP.Board itself that can cause this error directly and you, or your host, should look closer into the server configuration to resolve the problem.
MySQL has a lot of specific things you should look into for such an error. The page on MySQL's site describing what to do for this error is here:
http://dev.mysql.com.../gone-away.html
One of the most common causes of this error is a MySQL wait_timeout or interactive_timeout configuration value set too low. By default, both are set to 28800 seconds, however many hosts lower this. Generally, that is safe to do however when the values get lowered too low, then you can encounter the error.
When you see a driver error message this means that IP.Board is having trouble communicating with your database. When this happens, IP.Board will log the error in ./cache/sql_error_log_MM_DD.cgi where MM and DD are the month and day the log was generated. If you look at the end of this text file it will show you the most recent log entries being generated. From there you can learn what to do.
Note that in version IP.Board 3.1.4, a feature was introduced to allow you to view the last few kilobytes of each existing error log. Go to ACP -> Logs -> SQL Error Logs. On the right, any existing logs in the ./cache directory will be listed. Clicking any entry will show you the last few enties in it. To view the entire log, you'd need to connect with FTP and download the relevant file. They can be opened in any text editor.
Missing Columns
Though rare, sometimes an upgrade can miss creating a column in the database and this will generate an error. Before submitting a support ticket, first try logging into the AdminCP, going to Support tab, and then using the database checker to see if IP.Board can diagnose and fix the problem itself.
Crashed Tables
IP.Board by default uses a MySQL database to store data in. MySQL database tables can under some circumstances crash causing a repair to be necessary.
If this happens, your community will display a driver error, and a message will appear in the database error log that says something along the lines of "Table is Marked as Crashed and Should be Repaired".
It is important to understand that while there are several reasons that a table crash might occur, it is always caused by the server. For example it can be caused by the server being improperly shut down or restarted, hard disk drive failure/errors, improper repair attempts on a database, etc.
IP.Board cannot in itself cause a table to crash.
Repairing a crashed table is a simple process, however we strongly recommend that if you experience a crashed table you should contact your hosting provider and ask them to repair it. Attempting a repair yourself could cause further complications, and it is important regardless to report the issue to your hosting provider so that they can investigate and resolve any server issues which might cause the problem to happen again.
If you experience a crash on the sessions table, due to the nature of the way IP.Board interacts with the table, you may wish to change the table to memory storage. If you are unsure if this is necessary or how to do this, you should discuss this with your hosting provider.
MySQL server has gone away
This error means that, while IP.Board was trying to query your MySQL database, the server disconnected from the request. There is nothing in IP.Board itself that can cause this error directly and you, or your host, should look closer into the server configuration to resolve the problem.
MySQL has a lot of specific things you should look into for such an error. The page on MySQL's site describing what to do for this error is here:
http://dev.mysql.com.../gone-away.html
One of the most common causes of this error is a MySQL wait_timeout or interactive_timeout configuration value set too low. By default, both are set to 28800 seconds, however many hosts lower this. Generally, that is safe to do however when the values get lowered too low, then you can encounter the error.
0 Comments