General error 2006 mysql server has gone away laravel

Tutorials

Having problem importing your SQL dump, be it via command line or via container management console, here is the solution.

$ ./mysql -u root -p my_db < file.sql
Enter password: 
ERROR 2006 (HY000) at line 1: MySQL server has gone away

Error Message: ERROR 2006 (HY000): MySQL server has gone away, see above.

Description: This is caused by SQL import file being too big or field carrying too much information, causing it to exceed the max_allowed_packet setting.

System: Linux

Solution: increase the maximum allowed packet by changing the parameter in my.cnf file will resolve this problem.

Steps:

1. SSH or SFTP to the Server

2. Look for my.cnf with whereis command or

3. my.cnf can be found on linux: /etc/mysql

4. Add the following line to my.cnf

5. Save and close the file

6. Restart MySQL server using or Restart the Server

sudo service mysql restart

7. Try importing the SSL file again.

• Octane Version: 1.0.1
• Laravel Version: 8.42.0
• PHP Version: 8.0.6
• Server & Version: Swoole 4.6.6
• Database Driver & Version: MySQL 5.6.10

Description:

We are using AWS Aurora as our database and by default they have a wait_timeout and interactive_timeout of 300 seconds (5 minutes) so if the system does not receive any request for more than 5 minutes it starts throwing

SQLSTATE[HY000]: General error: 2006 MySQL server has gone away (SQL: ...)

The exception is being thrown while trying to authorize a user through the auth middleware.

Steps To Reproduce:

1. Start an octane server.
2. Set the wait_timeout and interactive_timeout to a minimum for your MySQL server.
3. Make a few HTTP requests that uses MySQL connection. Enough requests to warm up all the workers.
4. Wait a couple of minutes more than the set timeouts.
5. Make another HTTP request.
6. An exception should be thrown.

My input:

From what I've seen the framework will try to reconnect if a connection is dropped. Here's the exception trace:

{
	"trace": [
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Database/Connection.php",
			"line": 752,
			"function": "runQueryCallback",
			"class": "Illuminate\\Database\\Connection",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Database/Connection.php",
			"line": 732,
			"function": "tryAgainIfCausedByLostConnection",
			"class": "Illuminate\\Database\\Connection",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Database/Connection.php",
			"line": 641,
			"function": "handleQueryException",
			"class": "Illuminate\\Database\\Connection",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Database/Connection.php",
			"line": 346,
			"function": "run",
			"class": "Illuminate\\Database\\Connection",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php",
			"line": 2315,
			"function": "select",
			"class": "Illuminate\\Database\\Connection",
			"type": "->"
		},
		...
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Auth/TokenGuard.php",
			"line": 85,
			"function": "retrieveByCredentials",
			"class": "App\\Auth\\RepositoryUserProvider",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/framework/src/Illuminate/Auth/AuthManager.php",
			"line": 204,
			"function": "user",
			"class": "Illuminate\\Auth\\TokenGuard",
			"type": "->"
		},
		...
		{
			"file": "/app/vendor/laravel/octane/src/Worker.php",
			"line": 92,
			"function": "handle",
			"class": "Laravel\\Octane\\ApplicationGateway",
			"type": "->"
		},
		{
			"file": "/app/vendor/laravel/octane/bin/swoole-server",
			"line": 118,
			"function": "handle",
			"class": "Laravel\\Octane\\Worker",
			"type": "->"
		},
		{
			"function": "{closure}"
		},
		{
			"file": "/app/vendor/laravel/octane/bin/swoole-server",
			"line": 164,
			"function": "start",
			"class": "Swoole\\Server",
			"type": "->"
		}
	]
}

And it looks like the tryAgainIfCausedByLostConnection() is being called but that is not working.

After skimming through the code for Laravel's queue worker I see that if an exception is thrown due to lost connection, the worker process is exited and new worker is created (https://github.com/laravel/framework/blob/39459134a81ef3cc4b078b2f9de1495459bba50a/src/Illuminate/Queue/Worker.php#L377). Maybe implement something like that for the HTTP workers as well?

How do I fix error code 2006 MySQL server has gone away?

Why MySQL server has gone away?

How do I fix MySQL connection error?

Can't connect to MySQL server timed out?