• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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