• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Error migrating from cPanel (rsync error code 11)

  • Thread starter Deleted member 260697
  • Start date
D

Deleted member 260697

Guest
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
Plesk Obsidian v18.0.43_build1800220414.18
Hello,

I'm trying to use Plesk Migrator to migrate from our old cPanel server.

However, I'm getting the following error:

Code:
Failed to perform action: Fetch shallow data from source cPanel
Cause: Command execution failed on the local server with non-zero exit code.
command: rsync -r --chmod=Fu=r,Du=rwx,go= --timeout=30 -e 'ssh -i /root/.ssh/id_rsa -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/legacy/extras/plesk_11_5_pmm_shared/ [email protected]:'~/tmp/plesk_migrator/plesk_migrator-sc5wv95kbukf1cnzejg474sf2zk0wqji/pmm_agent'
exit code: 11
stdout:
stderr: rsync: mkdir "/home3/colorwo5/tmp/plesk_migrator/plesk_migrator-sc5wv95kbukf1cnzejg474sf2zk0wqji/pmm_agent" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.2]

That is a critical error, migration was stopped.

From what I researched, the exit code 11 from rsync seems to be because of unavailable disk space in the cPanel server, however, I cannot confirm this.

Please advise. Thank you.
 
Here are the full logs:

Code:
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||Traceback (most recent call last):
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/common_cli.py", line 54, in run
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    options.method(migration.action_runner)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/cli/migration_cli.py", line 352, in <lambda>
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    lambda runner: runner.run_entry_point('generate-migration-list'),
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/base.py", line 67, in run_entry_point
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    self.run(entry_point, handle_stop_mark=self._context.options.is_allow_stop)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 82, in run
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    self._run_common_actions_tree(actions_tree, handle_stop_mark=handle_stop_mark)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 117, in _run_common_actions_tree
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    self._run_common_actions_tree(action, action_path, handle_stop_mark=handle_stop_mark)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 132, in _run_common_actions_tree
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    self._run_common_action_plain(action, action_path)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||  File "/usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/core/workflow/runner/by_subscription.py", line 213, in _run_common_action_plain
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||    raise MigrationError(full_failure_message)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||MigrationError: Failed to perform action: Fetch shallow data from source cPanel
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||Cause: Command execution failed on the local server with non-zero exit code.
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||command: rsync -r --chmod=Fu=r,Du=rwx,go= --timeout=30 -e 'ssh -i /root/.ssh/id_rsa -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' /usr/local/psa/admin/plib/modules/panel-migrator/backend/lib/python/parallels/plesk/source/legacy/extras/plesk_11_5_pmm_shared/ [email protected]:'~/tmp/plesk_migrator/plesk_migrator-sc5wv95kbukf1cnzejg474sf2zk0wqji/pmm_agent'
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||exit code: 11
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||stdout:
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||stderr: rsync: mkdir "/home3/colorwo5/tmp/plesk_migrator/plesk_migrator-sc5wv95kbukf1cnzejg474sf2zk0wqji/pmm_agent" failed: No such file or directory (2)
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||rsync error: error in file IO (code 11) at main.c(656) [Receiver=3.1.2]
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||
=|2022-10-02_11:15:05,448|D|MT|core.cli.common_cli|||That is a critical error, migration was stopped.
 
I also tried matching the rsync versions in both servers, to no avail.

I am hoping I can find a solution to this issue soon, as I am in a time crunch to fully migrate my company from cPanel to Plesk, and Plesk Migrator is the only practical solution for all the dozens of email accounts I have to migrate. Perhaps I can configure it to use something other than rsync?
 
I am disappointed by the lack of response. We couldn't fix this issue for the life of us, so we ended up having to subscribe to another cPanel provider and refund our Plesk license.

Not a great experience.
 
what user are do you use for migration on source server?
it is expected to use root user.

did you inspect /usr/local/psa/var/modules/panel-migrator/sessions/<here_should_be_your_session_id>/config.ini ?
it is strange to see not full path like ~/tmp.


actually, if it is urgent for you I'd recommend to reach Plesk Technical support directly.
because this forum is a community-based, so no any ETA or even answers are guaranteed.
 
Back
Top