Error during migration: 'utf8' codec can't decode byte in position: invalid start byte

Created:

2017-01-11 10:11:39 UTC

Modified:

2017-08-17 15:09:03 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Error during migration: 'utf8' codec can't decode byte in position: invalid start byte

Applicable to:

  • Plesk for Linux

Note: This article has the reference to the issue with the fix available:

Please consider updating your server:

Symptoms

The following error appears during migration:

[2017-01-11 04:11:01][INFO] [example.com] Look up for instances of application 'WordPress' at '/var/www/vhosts/example.com'
[2017-01-11 04:11:01][INFO] [example.com] Found 'WordPress at '/var/www/vhosts/example.com/httpdocs/blog''
[2017-01-11 04:11:01][INFO] [example.com] Found 'WordPress at '/var/www/vhosts/example.com/httpdocs/wordpress''
[2017-01-11 04:11:01][ERROR] [example.com] Failed to adjust 'WordPress at '/var/www/vhosts/example.com/httpdocs/blog'': 'utf8' codec can't decode byte 0xa7 in position 2532: invalid start byte
[2017-01-11 04:11:01][ERROR] [example.com] Failed to adjust 'WordPress at '/var/www/vhosts/example.com/httpdocs/wordpress'': 'utf8' codec can't decode byte 0xfc in position 60: invalid start byte
Adjusted applications
|
`- Subscription 'example.com'
|
|- warning: Failed to adjust 'WordPress at '/var/www/vhosts/example.com/httpdocs/blog'': 'utf8' codec can't decode byte 0xa7 in position 2532: invalid start byte
|
|- warning: Failed to adjust 'WordPress at '/var/www/vhosts/example.com/httpdocs/wordpress'': 'utf8' codec can't decode byte 0xfc in position 60: invalid start byte

Cause

This is Plesk Migrator bug with ID #PMT-3400 which is planned to be fixed in future Plesk Migrator updates.

The bug is related to wrong logging parameters and does not affect migration process.

Resolution

Currently, there is no workaround, error messages can be ignored.

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