[ERROR] mysqldump: Error 2013: Lost connection to server during query when dumping table

HoSSaM MoSTaFa

• March 18, 2023 12:19

Hello, I use Current Version MariaDB 10.6.12-MariaDB During the process of backing up all sites All copying operations succeed except for one site that shows this error while copying the database [ERROR] mysqldump: Error 2013: Lost connection to server during query when dumping table `wpyk_postmeta` at row: 38674 mysqldump: Couldn't execute 'SELECT engine, table_type FROM INFORMATION_SCHEMA.TABLES WHERE table_schema = DATABASE() AND table_name = 'wpyk_posts'': Server has gone away (2006) How do I solve this problem? Thank you

• 

  cPRex Jurassic Moderator

  • March 19, 2023 03:06

  Hey there! It looks like MySQL may have had a larger issue while backing up that account. Do you see that the service was restarted around that time? If not, do you see any errors in the MySQL error log during that time?

  0
• 

  HoSSaM MoSTaFa

  • March 19, 2023 03:39

  Hey This problem only occurs for one database . But the remaining databases are copied successfully /var/log/mysqld.log [Warning] Aborted connection 271543 to db: 'whitxbgl_WP958' user: 'root' host: 'localhost' (Got an error writing communication packets) /etc/my.cnf # For advice on how to change settings please see # MySQL :: MySQL 5.7 Reference Manual :: 5.1.2 Server Configuration Defaults [mysqld] performance-schema=0 # # Remove leading # and set to the amount of RAM for the most important data # cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%. # innodb_buffer_pool_size = 128M # # Remove leading # to turn on a very important data integrity option: logging # changes to the binary log between backups. # log_bin # # Remove leading # to set options mainly useful for reporting servers. # The server defaults are faster for transactions and fast SELECTs. # Adjust sizes as needed, experiment to find the optimal values. # join_buffer_size = 128M # sort_buffer_size = 2M # read_rnd_buffer_size = 2M datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Disabling symbolic-links is recommended to prevent assorted security risks symbolic-links=0 log-error=/var/log/mysqld.log # pid-file=/var/run/mysqld/mysqld.pid innodb_buffer_pool_size=134217728 max_allowed_packet=268435456 open_files_limit=40000 innodb_file_per_table=1 bind-address=127.0.0.1 unix_socket=OFF

  0
• 

  HoSSaM MoSTaFa

  • March 21, 2023 01:44

  Does it have a problem solution? :rolleyes:

  0
• 

  cPRex Jurassic Moderator

  • March 21, 2023 01:57

  There isn't anything helpful in that error statement. I would try a manual dump of that database on the command line to see if that generates a more helpful error message, since the problem only seems to be present with that one database.

  0

Please sign in to leave a comment.