Cannot start migration: invalid continuation byte

Created:

2016-12-12 03:46:23 UTC

Modified:

2017-08-08 13:21:33 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot start migration: invalid continuation byte

Applicable to:

  • Plesk 12.5 for Linux

Symptoms

  1. Migration pre-check failed with the following error:

    Failed to check Plesk API connection to target Plesk server: Failed to execute local command '/bin/sh -c '/usr/local/psa/bin/secret_key --list'': 'utf8' codec can't decode byte 0xed in position 7: invalid continuation byte
  2. Direct execution of secret_key command on the target server shows output with non-UTF8 symbols:

    # /usr/local/psa/bin/secret_key --list
    Key: γ▒~▒^▒BE▒ו▒▒▒Ib%▒▒ZT▒▒OSwSy5▒▒▒m▒▒#ރc▒▒*▒
    Ip: 10.20.30.40
    Description: For Plesk Migrator extension

Cause

API secret key for Plesk Migrator extension has been generated with non-UTF8 symbols.

Resolution

  1. Finish previous failed migration.
  2. Create backup of the psa database:

    # MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysqldump -u admin psa > psa`date +%F_%H.%M`.sql
  3. Log into Plesk database

    # plesk db
  4. Find Remove invalid secret key in psa database

    mysql> SELECT * FROM secret_keys where description="For Plesk Migrator extension"\\G
    *************************** 1. row ***************************
    key_id: $AES-128-*******************************************
    ip_address: 10.20.30.40
    description: For Plesk Migrator extension
    client_id: 1
    lookup_id: b09e98679adab4f20310680c908e5926
    1 row in set (0.00 sec)
    mysql>
    mysql> delete from secret_keys where lookup_id="b09e98679adab4f20310680c908e5926";
  5. Start migration again.

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