Issue Unable to backup WordPress site in Plesk "Backup created with minor issues occurred"

[meymigrou]

Server operating system version

CentOS 7

Plesk version and microupdate number

18.0.64

I have a WordPress website running on a dedicated server (Plesk Obsidian v18.0.64 and CentOS 7) which I am unable to backup from Plesk (or any other plugin whatsoever).

Each time I try to backup the database I get this error: The backup Nov 11, 2024 05:55 PM was created and can be restored, although some minor issues occurred.

Looking at the log file it says: Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 3: mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping table NvR0P1evBv_options at row: 1165

Looking at the file in the same row I can see the following:

What I’ve Tried​

• I’ve increased the max_allowed_packet in the my.cnf to max_allowed_packet=1G and made sure it has been placed below the [mysqld].
• I’ve used the SQL Command OPTIMIZE TABLE NvR0P1evBv_options; but it didn’t help.
• I’ve cleaned Rank Math’s analytics and tables and used all the options/tools they provide to clean and reset them. I’ve also tried to completely uninstall it.
• I’ve tried backing up the database through a Scheduled Task: mysqldump --max_allowed_packet=512M -u your_username -p'your_password' your_database_name > /var/www/vhosts/your_site.com/httpdocs/database_backup.sql but that didn’t help either.

The database is 771 MB and I am the only one who manages the dedicated server and I have access to SSH. Any help to resolve this error will be much appreciated!!

 

[pleskpanel]

The first place to start might be to check that the value that you're setting is actually in both places:

[mysql] AND in the [mysqldump] sections.

Then restart the MySQL or MariaDB service and try again.

 

[meymigrou]

The first place to start might be to check that the value that you're setting is actually in both places:

[mysql] AND in the [mysqldump] sections.

Then restart the MySQL or MariaDB service and try again.

Thank you for your reply! I've made sure that value was in both the [MySQL] and [mysqldump] and although now the database backup is a whole lot bigger, it's still not able to backup the whole database.

 

[Sebahat.hadzhi]

I’ve increased the max_allowed_packet in the my.cnf to max_allowed_packet=1G and made sure it has been placed below the [mysqld].

If I am not mistaken max_allowed_packet does not accept shorthands like 1G. (Please correct me if I am under the wrong impression.)


If you have already set the value of max_allowed_packet to 1024 M / 1073741824 under both [mysqldump] and [mysql] I can only think of my.cnf being ignored due to the use of the --no_defaults parameter during the export. However, as far as I understand you already tried exporting the database manually without success. Would you mind giving it another try without specifying max_allowed_packet:

mysqldump -u dbuser -p dbname > dumpfile.sql

and let us know what's the exact error you get, if any.