• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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