• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

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