- Plesk for Linux
When using a non-root system user, migration fails to start with one of the following error messages:
PLESK_ERROR: SSH connection to the source server can not be used: there is unexpected output when executing commands. Clean output is required by migrator to execute commands and consume their output, and to run "rsync" tool (for file transfer) which uses SSH connection as transport and does not work if there is any unexpected output.
PLESK_ERROR: Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Command execution failed on the local server with non-zero exit code.
command: /bin/mkdir -p /root/plesk_migrator
exit code: 1
stderr: /bin/mkdir: cannot create directory '/root': Permissions denied
That is a critical error, migration was stopped.
PLESK_ERROR: SSH connection to the source server 'source' (203.0.113.2) can not be used: command "bin/true" executed by SSH returned non-zero exit code. Check that the user used to connect to the server has "/bin/sh" or "/bin/bash" as its shell.
PLESK_ERROR: Error message or request description : Error: launchpad error (Error code = 2): == STDERR ==================== Cannot request remote agent status using command line /var/cache/2013100110274185/PleskX.pl: Died at AgentConfig.pm line 23. at AgentConfig.pm line 23 AgentConfig::AUTOLOAD() called at /var/cache/2013100110274185/PleskX.pl line 298 main::writeMigrationResult() called at /var/cache/2013100110274185/PleskX.pl line 304
PLESK_ERROR: Cannot request remote agent status using command line /var/cache/20150318093912860/PleskX.pl: which: no ruby in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin)
Can't open perl script "/var/cache/20150318093912860/PleskX.pl": No such file or directory
For Plesk migration, the 'root' system user must be used for Root login.
Specify the 'root' user in the Root login field. Specify its password or choose to authenticate via SSH keys. For details, refer to Authentication by SSH (Linux).
If the article did not help, check root user authentication configuration on the source server as per this article.
Note: It is possible to migrate with a non-root user in case of Migrating From a Linux Server With Custom Hosting.