How to check migration status

Created:

2016-11-16 13:07:48 UTC

Modified:

2017-06-26 04:36:10 UTC

1

Was this article helpful?


Have more questions?

Submit a request

How to check migration status

Applicable to:

  • Plesk Onyx for Windows
  • Plesk 12.5 for Windows

Question

How to check a migration status?

Answer

To ensure that a migration process is not stuck, check the logs in the migration session directory. The session directory is located within the directory on the target server.

For Windows:

%plesk_dir%var\modules\panel-migrator\sessions\XXXXXXXXXX\

For Linux:

/usr/local/psa/var/modules/panel-migrator/sessions/XXXXXXXXXX/

The most important logs are:

  • info.log - contains almost all necessary information about the migration, in brief

  • debug.log - detailed information about the migration

  • progress - represents the current migration progress in a table view

Migration is performed in several parallel threads (by default, 5), so, it is not correct just to open a log file and check the last entry to get the migration status.

The following steps can be used to check the migration status:

  1. Open progress file. It will contain information like:

     Subscription migration status:
    +-----------------------------------------------+------------------------+--------+
    | Subscription | Status | Action |
    +-----------------------------------------------+------------------------+--------+
    | example.com | In Progress | |
    +-----------------------------------------------+------------------------+--------+
    | example2.com | Finished with warnings | |
    +-----------------------------------------------+------------------------+--------+
    | example3.com | Finished with warnings | |
    +-----------------------------------------------+------------------------+--------+
    |
    example4.com | Finished with warnings | |
    +-----------------------------------------------+------------------------+--------+
  2. Find the task that has the In Progress status and remember the name of subscription it handles.

  3. Open debug.log and find the subscription name from step the step 2. Check the number of thread that is handling the subscription (ST1...ST5). For example:

    =|2016-07-18_04:55:20,456|I|ST1|core.reports.printer|example.com||Subscription 'example.com'
  4. Filter debug.log by the thread number and check the last entry to find out the task status:

    For Windows:
    findstr ST1 debug.log
    For Linux:
    # grep ST1 debug.log

Note: no changes in the aforementioned log files for hours and non-decreasing free disk space can also indirectly indicate that the task is hung.

Have more questions? Submit a request
Please sign in to leave a comment.