Applicable to:
- Plesk for Linux
Symptoms
-
Plesk Migrator migration from DirectAdmin server with End of Life OS (like CloudLinux or Centos 6 and 7) towards a server that has a supported OS and a latest version of Plesk fails with an error that is similar to the following:
PLESK_ERROR: Failed to deploy Python on source server
Cause: Command execution failed on the source server 'directadmin' (203.0.113.2) with non-zero exit code.
command: yum install -y -q plesk-py3
exit code: 1
stdout:
stderr: Error: Nothing to do
That is a critical error, migration was stopped
Cause
No plesk-py3 package is available for operating systems that have reached their End of Life (EOL).
PPS related to the case: [PPS-16532] Migration from DirectAdmin servers with EoL OS fails: Failed to deploy Python on source server - Jira.
The general internal fix from the PPS involves extension files adjustment and is the following:
1. Download the build of the Plesk Migrator extension that is used on the destination server
2. Unzip it
3. Open the meta.xml file
4. Find row <plesk_max_version>18.0.59</plesk_max_version> and remove it
5. Create a new zip with the adjusted contents and provide that one to the customer for installation
Resolution
1. Download the custom Plesk Migrator build file that is attached to this article.
2. Upload it to your Plesk destination server
3. Log into the destination server via SSH
4. Install the custom Plesk Migrator build that you have placed on your destination server by navigating to the directory in which the file was placed and executing the following command:
# plesk bin extension -i panel-migrator-2.25.6-1356-custom.zip
Retry the migration attempt afterwards.
Comments
Please sign in to leave a comment.