• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Failed to copy content of database

Vikelidis Kostas

New Pleskian
Server operating system version
AlmaLinux release 8.9
Plesk version and microupdate number
Plesk Obsidian 18.0.58.2
I am trying to transfer a subscription from one Plesk server (Centos7.9) to another one (AlmaLinux 8.9) and i am getting the following error:

Code:
Failed to copy content of database 'the_database_name_here'
Migration tools tried to perform operation in 3 attempts: Command execution failed on the source server 'source' (xxx.xxx.xxx.xxx) with non-zero exit code.
command: MYSQL_PWD="$(cat)" mysqldump --no-defaults -h localhost -P 3306 -uadmin --quick --quote-names --add-drop-table --default-character-set=utf8mb4 --set-charset --routines --events the_database_name_here > /root/plesk_migrator/plesk_migrator-a6oxhtf9ddrwtvzarn8hklab3898u1ht/db-dumps/the_database_name_here.sql
exit code: 3
stdout:
stderr: mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `cvEpBK7UP_pmxe_exports` at row: 1

I have already increased the max_allowed_packet to 1G in both [mysqld] and [mysqldump] sections of MariaDB config files but the problem remains.

If i run the same command (omitting the --no-defaults option) direct in the command line of the server the dump is created successfully.

The man page of mysqldump states that:
Code:
--no-defaults
          Do not read default options from any option file. This must be given as the first argument.

It seems that the mysqldump utility (or the way that Plesk uses this utility) ignores the variables in the config files of MariaDB.

Is there any solution for this?
 
Same Problem here with Plesk-Migrator from Centos-7 to Almalinux-9

Failed to perform an action on subscription '<domain>': Failed to copy content of database '<dbname>' Exception message: Migration tools tried to perform operation in 3 attempts: Command execution failed on the source server 'source' (<ip>) with non-zero exit code.command: MYSQL_PWD="$(cat)" mysqldump --no-defaults -h localhost -P 3306 -uadmin --quick --quote-names --add-drop-table --default-character-set=utf8mb4 --set-charset --routines --events <dbname> > /root/plesk_migrator/plesk_migrator-nqn2zck9ivj19vidca1k9uy31byp2t4x/db-dumps/nordmedia.sqlexit code: 3stdout: stderr: mysqldump: Error 2020: Got packet bigger than 'max_allowed_packet' bytes when dumping table `binaries` at row: 69961

I changed [mysqldump] sections but because of "--no-defaults" it has no use.

the same line with
mysqldump --no-defaults --max_allowed_packet=1024M ...
works.
Any help?
 
Back
Top