• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Plesk Migrator vhost fix Fails

daanse

Regular Pleskian
Hi,
latest Plesk and Migrator on Debian.
I moved 63 Subs btw, seems fine but most of the subs are reporting this fail:

Code:
[Migration] Failed to fix vhost structure for subscription 'xxxxx'
Migration tools tried to perform operation in 3 attempts: 'ascii' codec can't encode character u'\u2018' in position 220: ordinal not in range(128)

What does it mean, what can i do?
 
Today, I've got the same error and it seems that it is a bug in plesk's migrator:
I've got about 40 subscriptions and while migrating them to a new server I got the described error five times. I looked into the debug log file and it seems that
Code:
/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/plesk/actions/content/web/fix_unix_vhost_structure.py
wants to create a hard link to a directory which is not allowed. The result of this try is an error message with the source path of your directory which should be hard linked. The quotes of this error message are unicode chars and not recognized by python. In all my cases it was this directory which should be hard linked:
Code:
/var/www/vhosts/system/SUBSCRIPTION/logs/archives

But why is this directory not present in every subscription? Every time it is present, it comes to this conflict. I've deleted that directory but it seems that the migrator does not detect the new structure so far. I will tell you if I got a solution for it.

In my opinion it is definitely a bug of migrator.

[UPDATE] I forgot to delete the archives directory on the target machine. So when archives was deleted all went fine!
 
Last edited:
Back
Top