Migration from Plesk 11.0.9 (or 11.5.30) to 12.5.30 fails. The following errors can be found in
/usr/local/psa/PMM/logs/sessions/<timestamp>/debug.log debug migration log:
=|2016-05-25_22:11:35,312|D|MT|parallels|||MigrationError: Failed to perform action: Fetch information from target servers =|2016-05-25_22:11:35,312|D|MT|parallels|||Cause: not well-formed (invalid token): line 83, column 35 =|2016-05-25_22:11:35,312|D|MT|parallels|||That is a critical error, migration was stopped.
The following error can be found in
/usr/local/psa/PMM/logs/sessions/<timestamp>/info.log migration log:
[2016-05-27 19:31:04][ERROR] Failed to perform action: Fetch information from target servers Cause: not well-formed (invalid token): line 83, column 35 That is a critical error, migration was stopped.
Passwords decryption tool used by Plesk Dump Agent places non-UTF symbols into dumps. As a result, Plesk Migrator is unable to parse such dumps. This is Plesk Migrator internal issue with ID #PMT-2631, which is planned to be fixed in future Plesk Migrator updates.
Find users with password that contain non-UTF symbols:
# cd /usr/local/psa/PMM/logs/sessions/ && cd `ls -1t | head -n1` && mkdir plesk_backup_source_unpacked && tar -xvf plesk.backup.source.raw.tar -C plesk_backup_source_unpacked/ && grep -B2 '<password' plesk_backup_source_unpacked/backup_info_*.xml | grep -v properties
Strings with passwords that contain non-UTF symbols will look like:
<user is-domain-admin="false" name="email@example.com" is-built-in="false" contact="user" subscription-name="example.com" is-legacy-user="false" email="firstname.lastname@example.org" guid="d11c11f1-4b92-44eb-85f7-9f2a88605c46" cr-date="2014-10-18T18:55:58-06:00"> <password type="plain">▒▒▒▒▒▒▒▒▒▒▒▒▒▒</password>
Change passwords for specific users with non-UTF symbols (use UTF symbols only) on a source server according to instructions here:
129118 [How to] Change the password for a user account
- Re-run migration.