Expedition migration is stacked with below errors messages (/tmp/error): 'max_allowed_packet' bytes or Error while sending QUERY|STATISTICS packet

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
L4 Transporter
Did you find this article helpful? Yes No
No ratings

Symptoms

While executing a migration you get one of bellow message errors on the /tmp/error file: 

  • Got a packet bigger than 'max_allowed_packet' bytes
  • Error while sending QUERY|STATISTICS packet

Also the migration process could be stacked at some point for a long period of time.

Diagnosis

MySQL is not supporting to create the among of objects defined on your config so you need to give more resources to MySQL.

Solution

Resize the max allowed packets property on Mysql.

1) Locate your max_allowed_packet mysql configuration (for instance inside: /etc/mysql/mariadb.conf.d/50-server.cnf).
2) Edit the mysql config file and increase the MB for the property max_allowed_packet (for instance: max_allowed_packet = 100M).
3) Restart mysql (for instance: service mysql restart). 
4) Execute the migration in a new clean Expedition project.
Rate this article: