• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Plesk Migrator fails because of mysqldump non-zero exit code

manoaratefy

New Pleskian
Hello,

I'm migrating an old Windows Plesk server to a new server and I have issue during mysqldump of any account. It says that mysqldump got an non-zero exit code. Stderr and stdout reported are empty.
I checked and it seems that Plesk Migrator is using wrong MySQL location : "C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqldump"

By checking running processes on source server, I see two instance of MySQL :
- An MariaDB 10.5 on "C:\Program Files (x86)\Parallels\Plesk\MySQL"
- An MySQL 5 on ""C:\Program Files (x86)\Parallels\Plesk\Databases\MySQL51"

Customer's databases are on the MySQL 5. But Plesk Migrator is using mysqldump on the MariaDB 10.5 and I think this is the reason it doesn't work. Can anyone help me solving this migration issue?

Best regards.
 
Hello,

By adding "--default-character-set=latin1" in C:\Program Files (x86)\Plesk\admin\plib\modules\panel-migrator\backend\lib\python\parallels\core\utils\database_utils.py, the mysqldump binary of MariaDB 10.5 accepts to dump the MySQL 5 database so this solved the issue.
 
Back
Top