ERROR: SQLSTATE[08S01]: Communication link failure: Got a packet bigger than 'max_allowed_packet' bytes

When importing large MySQL database files, you may encounter the “MySQL server has gone away” or “Packet too large” error. This usually happens when the file size exceeds the server’s allowed packet limit.

This issue is common during database migrations, backups, or restoring large .sql dump files. If your MySQL configuration is not optimized for large imports, the process will fail midway.

By default, MySQL limits the size of data packets it can process at once. When you try to upload a database file larger than this limit, the server automatically stops the operation.

Understanding this error is essential for developers working with large databases in local environments like XAMPP or on live servers. Proper configuration can easily resolve the issue.

Common Causes

Below are the main reasons why this MySQL error appears:

Low max_allowed_packet Value

The default max_allowed_packet size in MySQL (especially version 5.6) is only 4MB. Large SQL dump files exceed this limit.

Large Database Import File

When importing big .sql files containing heavy data tables, images (BLOBs), or large inserts, MySQL cannot process them due to packet restrictions.

Server Configuration Not Updated

Sometimes configuration files like my.cnf or my.ini are not properly updated, or the MySQL service is not restarted after changes.

How to Fix the Error

Follow these practical solutions to fix the MySQL max allowed packet size error:

Update MySQL Configuration File

Please open your MySQL terminal and type "mysql" to get a MySQL prompt. In your MySQL settings, look for the following files.

1. my.cnf 
2. my.ini 

Open the above files and update

max_allowed_packet=100M
max_allowed_packet=1000M ; 1GB

After updating the above file in localhost or live server. Please restart the MySQL/Apache servers. So
That change will reflect. To restart the MySQL server, please run the following command.

Restart MySQL Server

Set Global Variables from MySQL Console

or you can open up your MySQL console and run the following command

set global max_allowed_packet=1000000000;
set global net_buffer_length=1000000;

The above commands basically increase and set the max allowed packet size in MySQL.

Note:
The default MySQL 5.6.6 max packet size is 4MB
Also, you can dump the  MySQL file using the below command by mentioning the size

Import Database with Custom Packet Size

You can also import your database using a command that specifies the packet size:

mysql --max_allowed_packet=100M -u root -p database < dump.sql

Conclusion

The MySQL max allowed packet size error is a common issue when importing large database files. Fortunately, it is easy to fix with proper configuration changes.

By increasing the max_allowed_packet value and restarting the MySQL server, you can prevent interruptions during large imports. This ensures smooth database migration and backup restoration.

Always check your MySQL default settings before importing heavy files, especially on shared hosting or live servers. Proper optimization improves performance and prevents unnecessary downtime.

Following the above steps will help you successfully import large MySQL dump files without errors and maintain a stable database environment.