• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 onyx Version 17.8.11 Update #56 migration error

manos

Basic Pleskian
Hi,

Last migrations i did before some months were ok

Today tried migrations from 2 different plesk onyx servers from 2 others (tried all combinations)
Receiving everywhere same error:

Failed to generate migration list file
Cause: 246
That is a critical error, migration was stopped.

any idea?
 
Any additional related details from /usr/local/psa/PMM/logs/migration-<datetime> ?
 
This is the info file

hat is a critical error, migration was stopped.
[2019-06-17 19:27:58][INFO] START: Check connections
[2019-06-17 19:27:59][INFO] FINISH: Check connections
[2019-06-17 19:27:59][INFO] Check migration compatibility of source and target Plesk versions
[2019-06-17 19:27:59][INFO] Check that all required components are installed on source Plesk
[2019-06-17 19:27:59][INFO] START: Fetch basic information about resellers, clients and domains data from source servers
[2019-06-17 19:27:59][INFO] Deploy migration agent to 'x.x.x.x'
[2019-06-17 19:28:01][INFO] Create source shallow dump.
[2019-06-17 19:28:02][INFO] FINISH: Fetch basic information about resellers, clients and domains data from source servers
[2019-06-17 19:28:02][INFO] START: Generate migration list file
[2019-06-17 19:28:04][ERROR] Failed to generate migration list file
Cause: 246
That is a critical error, migration was stopped.
 
This is the debug file
As i wrote tried between 4 plesk servers, all combinations, same result

=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription||| self._get_server_information()
=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription||| File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/thirdparties/pymysql/connections.py", line 1214, in _get_server_information
=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription||| self.server_charset = charset_by_id(lang).name
=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription||| File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/thirdparties/pymysql/charset.py", line 34, in by_id
=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription||| return self._by_id[id]
=|2019-06-17_19:28:02,810|D|MT|core.workflow.runner.by_subscription|||KeyError: 246
+|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription|||Exception:
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription|||Traceback (most recent call last):
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription||| File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 196, in _run_common_action_plain
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription||| run_multi_attempts()
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription||| File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 177, in run_multi_attempts
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription||| raise err
=|2019-06-17_19:28:02,819|D|MT|core.workflow.runner.by_subscription|||KeyError: 246
+|2019-06-17_19:28:02,820|D|MT|core.workflow.runner.by_subscription|||START: Uninstall migration agent files
+|2019-06-17_19:28:02,820|D|MT|core.runners.base|||Execute command on the source server 'source' (x.x.x.x): /bin/rm -rf /root/plesk_migrator/plesk_migrator-4r1oc3tu5z8dbs69bodeh0g5t2dcbupm/pmm_agent
+|2019-06-17_19:28:02,884|D|MT|core.runners.base|||Command execution results:
=|2019-06-17_19:28:02,884|D|MT|core.runners.base|||stdout:
=|2019-06-17_19:28:02,884|D|MT|core.runners.base|||stderr:
=|2019-06-17_19:28:02,884|D|MT|core.runners.base|||exit code: 0
+|2019-06-17_19:28:02,885|D|MT|core.workflow.runner.by_subscription|||FINISH: Uninstall migration agent files
+|2019-06-17_19:28:02,885|D|MT|core.workflow.runner.by_subscription|||START: Remove temporary users and SSH keys that were required to transfer files
+|2019-06-17_19:28:02,885|D|MT|core.workflow.runner.by_subscription|||FINISH: Remove temporary users and SSH keys that were required to transfer files
+|2019-06-17_19:28:02,886|D|MT|core.workflow.runner.by_subscription|||START: Remove temporary SSH keys
+|2019-06-17_19:28:02,886|D|MT|core.utils.ssh_key_pool|||Remove SSH key auth from this server to the source server 'source' (x.x.x.x)
+|2019-06-17_19:28:02,886|D|MT|core.runners.base|||Execute command on the source server 'source' (x.x.x.x): command -v sed
+|2019-06-17_19:28:02,944|D|MT|core.runners.base|||Command execution results:
=|2019-06-17_19:28:02,944|D|MT|core.runners.base|||stdout: /usr/bin/sed
=|2019-06-17_19:28:02,944|D|MT|core.runners.base|||
=|2019-06-17_19:28:02,944|D|MT|core.runners.base|||stderr:
=|2019-06-17_19:28:02,944|D|MT|core.runners.base|||exit code: 0
+|2019-06-17_19:28:02,945|D|MT|core.runners.base|||Execute command on the source server 'source' (x.x.x.x): sed -i -e '\|ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAiu/rIZ4szzxa+LK/JfXyNLB9jVRqTtgQmmauqvG7bUSctYiSUMJN+yhSY4lzE8IrqoQjT9lonbNhGJeErAKEUos2eM9ypGLI/Mok/oIaCGg7aLRQNaMsQ.
 
Last edited:
Could you please show me all the information about charset and collation from the output of 'show variables;' command on both (source and destination) MySQL servers?
Have you applied some kind of customizations for MySQL servers? What is the version of MySQL servers?
 
Hi,
Firstly many thanks for your time

all servers have mariadb 10.2.25
charset is utf8mb4
collation utf8mb4_unicode_520_ci

No real customisation just some tweaks at innodb parameters

thanks!
 
Thank you.
The problem in that our migration libs do not work with this charset and collation. It looks strange, so I'd suggest you contact Plesk Support Team for investigation this issue directly on your server.
 
Thanks again for your time
works with collation utf8mb4_unicode_ci?

the collation utf8mb4_unicode_520_ci is the most modern collation, supported by wordpress
I think is software (plesk) problem, not server problem as tried at 4 plesk servers

today plesk shows a plesk migrator update but when i tried to install it does not go through, any other with same experience?

thanks!


BTW what is the default charset and server collation of mariadb my.cnf file when plesk is installed?
 
Last edited:
changed collation from utf8mb4_unicode_520_ci to utf8mb4_unicode_ci and everything works fine
 
changed collation from utf8mb4_unicode_520_ci to utf8mb4_unicode_ci and everything works fine
Yes, it was good workaround only in the case that your data will not be corrupted after that.
 
Back
Top