Issue Migration tools tried to perform operation in 3 attempts: 'ascii' codec can't decode byte 0x...

[SylvioB]

Hello
I m trying to migrate some subscription from a Plesk 12.5.30 Update #55 installation to a Plesk Onyx 17.0.17 Update #10, both are running on Cent OS 6.8.

I have 2 subscription that give one error on the migration (seems to appear near database migration stage) :

[Migration] Failed to adjust common migrated applications for new environment
Migration tools tried to perform operation in 3 attempts: 'ascii' codec can't decode byte 0xe9 in position 8: ordinal not in range(128)

(on the second the byte value is 0xe0 but I except this is not the problem...)

In the debug logs I see :

=|2016-12-13_06:34:51,829|D|ST1|core.safe|xxxxx.com||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/utils/file_utils.py", line 19, in get_dir_tree
=|2016-12-13_06:34:51,829|D|ST1|core.safe|xxxxx.com||    item_path = os.path.join(path, item)
=|2016-12-13_06:34:51,829|D|ST1|core.safe|xxxxx.com||  File "/opt/plesk/python/2.7/lib64/python2.7/posixpath.py", line 73, in join
=|2016-12-13_06:34:51,829|D|ST1|core.safe|xxxxx.com||    path += '/' + b
=|2016-12-13_06:34:51,829|D|ST1|core.safe|xxxxx.com||UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 16: ordinal not in range(128)
+|2016-12-13_06:34:51,831|E|ST1|core.safe|xxxxx.com||Failed to adjust common migrated applications for new environment. Try to repeat operation once more.
+|2016-12-13_06:35:01,847|D|ST1|plesk.actions.adjust_applications|xxxxx.com||Start adjust database connection settings in configuration files of subscription
+|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||Exception:
=|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||Traceback (most recent call last):
=|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/safe.py", line 191, in try_subscription_with_rerun
=|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||    func()
=|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 431, in <lambda>
=|2016-12-13_06:35:01,882|D|ST1|core.safe|xxxxx.com||    lambda: action.run(self._context, subscription),

Do you have any workaround to try ? it could be changing something on the source server to bypass the error. What I need is to migrate those subscription as soon as possible.

Thanks in advance

 

[IgorG]

Try to use following workaround:

1. Remove account from the destination server, if it exists on it.
2. Remove non-ACSII symbol from login for account in Plesk > Customers > customer_name > Change Login Info on the source server.
3. Start a new migration.

 

[SylvioB]

Hello
It could not be the customer login, as they don't contain non-ASCII charter and, at all, other subrscriptions of those customers were migrated without any errors. The hosting system logins also don't contain any special charter, mysql user as well.

 

[Alina Dmi]

Hello!
Maybe the problem caused by filenames/directories in vhost with non-ASCII symbols, this issue will be fixed in nearest updates of Plesk Migrator, issue number PMT-3334.
Anyway, on target, you should have only one problem - not adjusted configs and you can do nothing on source, just fix connection strings and other settings(contains data from source) in application configs of subscription manually on target(you don`t need to migrate subscription again).

 

[SylvioB]

Hello. Ok thanks, it could be the case as the 2 hex values for the error are é and à that are commonly used char in french. Could you please tell me approximately when the patch of migrator is excepted to be release ?

 

[Alina Dmi]

Most likely, in the nearest update in the end of December.