• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Plesk Migrator - Unable to create subscription

FloAT

New Pleskian
Hi everyone,

I don't figure out how to migrate website from another plesk instance with Plesk Migrator.
I've already migrated 4 subsciption without any problem.

I now have this issue :

subscription-status-error.png
Failed to deploy subscription 'xxx.fr'
Migration for that subscription is considered completely failed. No further actions are performed for it.
Migration tools tried to perform operation in 3 attempts: Unable to create subscription 'xxxfr'.
Subscription already exists on target server: most probably it was created at the previous attempt,
but migration tools are not sure if it was created correctly.
It is recommended to:
1) Resolve the original issue that caused subscription creation to fail,
delete subscription, and then run migration again.
OR
2) Ensure that created subscription is fine, or the original issue is minor,
then simply run migration for that subscription again.

Already tried :
--> I've deleted the subscirption via CLI with /usr/local/psa/bin/subscription -r xxx.fr but still the issue...
--> I've deleted the user (username already existing on the target server)

I have absolutly no idea what is wrong with this one !

Thanks for you help

Florian
 

Attachments

  • Capture d’écran 2021-06-16 à 11.13.51.png
    Capture d’écran 2021-06-16 à 11.13.51.png
    59.2 KB · Views: 3
Perhaps orphaned records are remains in Plesk database after your actions:

--> I've deleted the subscirption via CLI with /usr/local/psa/bin/subscription -r xxx.fr but still the issue...
--> I've deleted the user (username already existing on the target server)

I'в suggest you try to repair it after these actions with

# plesk repair db -y
 
Check that vhost directory is really removed from /var/www/vhosts/
 
In this case I'd suggest you contact Plesk Support Team. They will fix the issue directly on your server.
 
Back
Top