X-Cart:SQL errors - Revision history

Mouse at 14:04, 22 July 2020

2020-07-22T14:04:07Z

Seyfin: /* Lost connection to MySQL server during query */

2014-06-19T07:49:02Z

‎Lost connection to MySQL server during query

Seyfin: /* Lost connection to MySQL server during query */

2014-06-16T07:12:18Z

‎Lost connection to MySQL server during query

Mixon at 07:15, 28 November 2012

2012-11-28T07:15:13Z

Seyfin: /* MySQL server has gone away */

2011-09-05T11:43:05Z

‎MySQL server has gone away

Seyfin: /* Can't create/write to file */

2011-05-13T11:09:53Z

‎Can't create/write to file

Seyfin at 05:40, 14 April 2010

2010-04-14T05:40:29Z

Seyfin at 05:40, 14 April 2010

2010-04-14T05:40:06Z

Seyfin at 05:35, 14 April 2010

2010-04-14T05:35:44Z

Admin: /* User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000) */

2010-02-03T12:27:45Z

‎User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000)

@@ Line 7: / Line 7: @@
 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 such errors are numerous, most likely the reason is the same as described here: https://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 server 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
+* also the problem may be caused by the low value of the max_allowed_packet option: https://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:
+The limit of simultaneous connections to MySQL server is exceeded. This limit is set by the max_connections MySQL option - see https://dev.mysql.com/doc/refman/5.0/en/too-many-connections.html. The problem can be resolved in the following ways:
 * Increase the <u>max_connections</u> option value
@@ Line 31: / Line 31: @@
 * 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
+Additional info on the matter can be found here: https://dev.mysql.com/doc/refman/5.0/en/gone-away.html
-A possible solutions in this case - increase the <u>wait_timeout</u> option value (default value is 28800). Please contact your hosting regarding the matter. More info about this option: http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout
+A possible solutions in this case - increase the <u>wait_timeout</u> option value (default value is 28800). Please contact your hosting regarding the matter. More info about this option: https://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout
 As a quick workaround solution, you can 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.
@@ Line 72: / Line 72: @@
 The above error is caused by the fact that there was an attempt to transmit  via MySQL the data package, which size was greater than the ''''max_allowed_packet'''' MySQL option value.
-The detailed description can be found here: http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html
+The detailed description can be found here: https://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html
 In order to fix this issue it is required to change the  '''max_allowed_packet''' to a larger value
@@ Line 94: / Line 94: @@
 MySQL allows to limit any user's activity.  The max_questions option contains a number of queries of 'SELECT' type which a user can  execute per hour.
-If such an error is received, this means that X-cart executes a lot of queries and exceeds the limit. You can find more info about this option here: http://dev.mysql.com/doc/refman/5.1/en/user-resources.html
+If such an error is received, this means that X-cart executes a lot of queries and exceeds the limit. You can find more info about this option here: https://dev.mysql.com/doc/refman/5.1/en/user-resources.html
 The problem can be resolved in the following ways:
@@ Line 128: / Line 128: @@
 For more details about the "Can't create/write to file" error please refer to:
-http://dev.mysql.com/doc/refman/5.0/en/cannot-create.html
+https://dev.mysql.com/doc/refman/5.0/en/cannot-create.html
 If you have McAfee On-Access Scanner running on your server, add the temporary directory or the MySQL filetypes (MYD, MYI) into On-Access Scanner's exclude list. See: [https://kc.mcafee.com/corporate/index?page=content&id=KB50998 How to manage file and folder exclusions in VirusScan Enterprise 8.x]

@@ Line 8: / Line 8: @@
 * 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 sever restart
+* if it is a one time error, then most likely it was caused by the MySQL server 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

@@ Line 7: / Line 7: @@
 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 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
+* if it is a one time error, then most likely it was caused by the MySQL sever 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

@@ Line 132: / Line 132: @@
 If you have McAfee On-Access Scanner running on your server, add the temporary directory or the MySQL filetypes (MYD, MYI) into On-Access Scanner's exclude list. See: [https://kc.mcafee.com/corporate/index?page=content&id=KB50998 How to manage file and folder exclusions in VirusScan Enterprise 8.x]
 [[Category:X-Cart user manual]]
 [[Category:X-Cart user manual]]

@@ Line 33: / Line 33: @@
 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:
+A possible solutions in this case - increase the <u>wait_timeout</u> option value (default value is 28800). Please contact your hosting regarding the matter. More info about this option: http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html#option_mysqld_wait_timeout
-* increase the <u>wait_timeout</u> option value (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
+As a quick workaround solution, you can 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.
-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.
+If the error still persists and it is impossible to change the <u>wait_timeout</u> option value then it is recommended to change the hosting company.
 === SQL error when deleting products ===

@@ Line 123: / Line 123: @@
 * no writable permissions set for the temporary directory;
 * the temporary directory is defined incorrectly in MySQL configuration file;
-* problems with the storage device (not enough free disk space).
+* problems with the storage device (not enough free disk space);
 Contact your server administrators and ask them to look into and fix the problem.
@@ Line 129: / Line 130: @@
 For more details about the "Can't create/write to file" error please refer to:
 http://dev.mysql.com/doc/refman/5.0/en/cannot-create.html
 [[Category:X-Cart user manual]]

← Older revision		Revision as of 05:40, 14 April 2010
Line 120:		Line 120:

	If you get an error of the "Can't create/write to file" type for some queries, it means that MySQL cannot create a temporary file for the result set in the temporary directory. The probable reasons are:		If you get an error of the "Can't create/write to file" type for some queries, it means that MySQL cannot create a temporary file for the result set in the temporary directory. The probable reasons are:
−
−

	* no writable permissions set for the temporary directory;		* no writable permissions set for the temporary directory;

← Older revision		Revision as of 05:35, 14 April 2010
Line 116:		Line 116:

	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.		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.
		+
		+	=== Can't create/write to file ===
		+
		+	If you get an error of the "Can't create/write to file" type for some queries, it means that MySQL cannot create a temporary file for the result set in the temporary directory. The probable reasons are:
		+
		+	- no writable permissions set for the temporary directory;
		+	- the temporary directory is defined incorrectly in MySQL configuration file;
		+	- problems with the storage device (not enough free disk space).
		+
		+	Contact your server administrators and ask them to look into and fix the problem.
		+
		+	For more details about the "Can't create/write to file" error please refer to:
		+	http://dev.mysql.com/doc/refman/5.0/en/cannot-create.html

	[[Category:X-Cart user manual]]		[[Category:X-Cart user manual]]

← Older revision		Revision as of 12:27, 3 February 2010
Line 88:		Line 88:

	=== User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000) ===		=== User 'mysqluser' has exceeded the 'max questions' resource (current value: 50000) ===
		+
		+	You receive the following SQL errors:
		+
		+	<pre>INVALID SQL: 1226 : User 'mysqluser' has exceeded the 'max_questions' resource (current value: 50000)</pre>
		+
		+	MySQL allows to limit any user's activity. The max_questions option contains a number of queries of 'SELECT' type which a user can execute per hour.
		+
		+	If such an error is received, this means that X-cart executes a lot of queries and exceeds the limit. You can find more info about this option here: http://dev.mysql.com/doc/refman/5.1/en/user-resources.html
		+
		+	The problem can be resolved in the following ways:
		+
		+	* increase the <u>max_questions</u> value
		+	* the following workaround can be used: it is required to create a few MySQL users, realize in the config.php a random choice of user from the list. Since every user has a limit of max_questions, X-Cart will be able to fulfill the following number of queries: max_questions * the number of users in the config.php
		+	* [[X-Cart:Images Location Management\|move the images to the file system]], disable the unnecessary modules, disable the statistics, which will decrease page load time
		+	* change the hosting provider

	=== User [name] has already more than 'max_user_connections' active connections ===		=== User [name] has already more than 'max_user_connections' active connections ===