• 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

Stuck migration

MIC

New Pleskian
Hi,
I'm migrating subscriptions from an older Plesk server to a new one.
All the migrations were completed successfully (more or less), so I handed the control over the server to the customer to update their DNS records in their own pace and re-sync the data afterwards.
Most of the subscriptions are already migrated, however, yesterday afternoon they tried to re-sync data for one of the subscriptions and it got stuck.
Since then, the subscription migration/re-syncing is visible in the Migration tool list as running (while it is clearly not):

Overall - Check that specified source servers accounts are built-in Windows administrators
(name of the domain)

No matter how many times I try to click cancel anywhere, the situation does not change.
In the subscription list the domain is listed as:
Migration - Success
Content synced - Queued
Again, clicking Cancel here does nothing.

The server was restarted several times since, does not help either.

I cannot find anything terribly useful in any log file.

Yesterday, the runner.info.log for this session started reporting:
[2018-06-21 15:26:21][INFO] Run task "2018-06-21-15-26-12-1"
[2018-06-21 15:26:21][INFO] Run task command: "C:\Program Files (x86)\Plesk\python\python.exe" "C:\Program Files (x86)\Plesk\admin\plib\modules\panel-migrator\backend\plesk-migrator.py" "C:\Program Files (x86)\Plesk\var\modules\panel-migrator" copy-content "C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20180416084003\config.ini" --migration-list-format=json "--migration-list-file=C:\Program Files (x86)\Plesk\var\modules\panel-migrator\sessions\20180416084003\tasks\2018-06-21-15-26-12-1\migration-list.json" --progress-task-id=2018-06-21-15-26-12-1 --skip-services-checks --skip-license-checks --ignore-migration-list-errors
[2018-06-21 15:27:07][INFO] Another instance of task runner is already running, this instance will be stopped
[2018-06-21 15:28:08][INFO] Another instance of task runner is already running, this instance will be stopped
[2018-06-21 15:29:09][INFO] Another instance of task runner is already running, this instance will be stopped
[2018-06-21 15:30:10][INFO] Another instance of task runner is already running, this instance will be stopped
...
...and so on...
...

and after some meddling, it changed today to
[2018-06-22 09:41:04][INFO] Migration stopped by user request
[2018-06-22 09:41:46][INFO] Migration stopped by user request
[2018-06-22 09:41:57][INFO] Migration stopped by user request
[2018-06-22 09:42:11][INFO] Migration stopped by user request
[2018-06-22 09:42:49][INFO] Migration stopped by user request
[2018-06-22 09:43:13][INFO] Migration stopped by user request
[2018-06-22 09:43:49][INFO] Migration stopped by user request
[2018-06-22 09:44:04][INFO] Migration stopped by user request
....

Any help or advice would be really appreciated.
 
Last edited:
OK, in the end, I managed to solve it myself. I'll write here how, for case someone else also encounters this issue.
I solved it by pressing the "Finish migration" button. I was somewhat hesitant to do that, as - as I expected - all the migration settings and logs etc. are lost now. But along with the stuck domain migration, so the problem is gone.
I then started a completely new migration (with the same settings as the previous one). All the (several hundred) subscriptions now once again display the "Migration not started" status, but at least the already migrated subscriptions were not deleted from Plesk altogether (thank god). As only about thirty subscriptions remained to be migrated and we know which ones, we are now going to migrate these and then cancel the rest of the migrations altogether (or, rather, press the "Finish migration" button again).
 
subscription-status-warning.png
Subscription 'madinatraders.pk' does not exists on source server(s).
Probably it was removed from the source server since migration was started.
Migration of that subscription will be skipped.

This error comes when i am migrating wherease all subscriptions are present on the sourcs server...
 
Back
Top