Difference between revisions of "X-Cart:SQL errors"
(→Mysql connect(): Too many connections) |
|||
| Line 1: | Line 1: | ||
| − | ===Got error 28 from storage engine=== | + | === Got error 28 from storage engine === |
This error appeared due to the lack of free space in the file system on the hard disc drive where MySQL is installed. The solution is rather simple - to clean up some disc space. | This error appeared due to the lack of free space in the file system on the hard disc drive where MySQL is installed. The solution is rather simple - to clean up some disc space. | ||
| − | ===Lost connection to MySQL server during query=== | + | === Lost connection to MySQL server during query === |
This error message means that when executing the query the conenction with MySQL server was lost | This error message means that when executing the query the conenction with MySQL server was lost | ||
| Line 11: | Line 11: | ||
* also the problem may be caused by the low value of the max_allowed_packet option: http://kb.x-cart.com/article/the-size-of-the-data-package-being-transmitted-is-greater-than-maximum-allowed-by-the-server | * also the problem may be caused by the low value of the max_allowed_packet option: http://kb.x-cart.com/article/the-size-of-the-data-package-being-transmitted-is-greater-than-maximum-allowed-by-the-server | ||
| − | ===Mysql connect(): Too many connections=== | + | === Mysql connect(): Too many connections === |
The limit of simultaneous connections to MySQL server is exceeded. This limit is set by the max_connections MySQL option - see http://dev.mysql.com/doc/refman/5.0/en/too-many-connections.html. The problem can be resolved in the following ways: | The limit of simultaneous connections to MySQL server is exceeded. This limit is set by the max_connections MySQL option - see http://dev.mysql.com/doc/refman/5.0/en/too-many-connections.html. The problem can be resolved in the following ways: | ||
| Line 19: | Line 19: | ||
* change the hosting company | * change the hosting company | ||
| − | ===MySQL server has gone away=== | + | === MySQL server has gone away === |
| − | + | When you get a number of '''MySQL server has gone away''' errors in logs, this means that the MySQl server aborted the connection to PHP script but the script is still trying to execute a certain query. | |
| − | + | This usually occurs if : | |
| − | + | * a customer opens a store page in the browser | |
| + | * PHP script connects to the MySQL | ||
| + | * for some reason the script stops for a while ,during this pause MySQL server timed out and the connection was closed | ||
| + | * the script finishes its work and tries to execute the MySQL query again | ||
| + | * since the connection is already lost, the error message is shown | ||
| + | ; Additional info on the matter can be found here: http://dev.mysql.com/doc/refman/5.0/en/gone-away.html | ||
| − | + | There are two possible solutions in this case: | |
| − | ===User [name] has already more than 'max_user_connections' active connections=== | + | * increase the '''wait_timeout''' mySQL option value. Its default value is : 28800. More info about this option: http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout |
| + | * If it is impossible to change this option then it is recommended either to change the hosting company or apply the [[File:mysql_server_has_gone_away.txt]] patch. | ||
| + | |||
| + | After this patch is applied, X-cart will reconnect to MySQL in case of such errors. This patch is already included to X-Cart 4.1.11 and higher. | ||
| + | |||
| + | === SQL error when deleting products === | ||
| + | |||
| + | === The size of the data package being transmitted is greater than maximum allowed by the server === | ||
| + | |||
| + | === Unknown column 'xcart products.productid' in 'on clause' === | ||
| + | |||
| + | === User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000) === | ||
| + | |||
| + | === User [name] has already more than 'max_user_connections' active connections === | ||
<pre> | <pre> | ||
Revision as of 16:04, 3 February 2010
Contents
- 1 Got error 28 from storage engine
- 2 Lost connection to MySQL server during query
- 3 Mysql connect(): Too many connections
- 4 MySQL server has gone away
- 5 SQL error when deleting products
- 6 The size of the data package being transmitted is greater than maximum allowed by the server
- 7 Unknown column 'xcart products.productid' in 'on clause'
- 8 User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000)
- 9 User [name] has already more than 'max_user_connections' active connections
Got error 28 from storage engine
This error appeared due to the lack of free space in the file system on the hard disc drive where MySQL is installed. The solution is rather simple - to clean up some disc space.
Lost connection to MySQL server during query
This error message means that when executing the query the conenction with MySQL server was lost
- if such errors are numerous , most likely the reason is the same as described here: http://kb.x-cart.com/article/mysql-server-has-gone-away
- if it is a one time error, then most likely it was caused by the MySQL srever restart
- also the problem may be caused by the low value of the max_allowed_packet option: http://kb.x-cart.com/article/the-size-of-the-data-package-being-transmitted-is-greater-than-maximum-allowed-by-the-server
Mysql connect(): Too many connections
The limit of simultaneous connections to MySQL server is exceeded. This limit is set by the max_connections MySQL option - see http://dev.mysql.com/doc/refman/5.0/en/too-many-connections.html. The problem can be resolved in the following ways:
- Increase the max_connections option value
- if the images are stored in the database(are called via image.php), move them to the file system
- change the hosting company
MySQL server has gone away
When you get a number of MySQL server has gone away errors in logs, this means that the MySQl server aborted the connection to PHP script but the script is still trying to execute a certain query.
This usually occurs if :
- a customer opens a store page in the browser
- PHP script connects to the MySQL
- for some reason the script stops for a while ,during this pause MySQL server timed out and the connection was closed
- the script finishes its work and tries to execute the MySQL query again
- since the connection is already lost, the error message is shown
- Additional info on the matter can be found here
- http://dev.mysql.com/doc/refman/5.0/en/gone-away.html
There are two possible solutions in this case:
- increase the wait_timeout mySQL option value. Its default value is : 28800. More info about this option: http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout
- If it is impossible to change this option then it is recommended either to change the hosting company or apply the File:Mysql server has gone away.txt patch.
After this patch is applied, X-cart will reconnect to MySQL in case of such errors. This patch is already included to X-Cart 4.1.11 and higher.
SQL error when deleting products
The size of the data package being transmitted is greater than maximum allowed by the server
Unknown column 'xcart products.productid' in 'on clause'
User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000)
User [name] has already more than 'max_user_connections' active connections
Warning: mysql_connect(): User [name] has already more than 'max_user_connections' active connections in /home/[path_to_xcart_dir]/include/func.php on line 43 Could not connect to SQL db
This means that your mysql user has exceeded the max_user_connections limit (mysql configurable parameter). For example, when several users browse your site, several instances of x-cart scripts are called and the scripts try to connect to the mysql database. If the number of those scripts instances is higher than the max_user_connections limit defined on your server, user will see such error message.
You should contact your hosting administrators and ask them to increase the limit number of mysql connections per mysql user, i.e. 'max_user_connections' limit.
