Applicable to:
- Plesk for Linux
Symptoms
-
Unable to start migration 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
stdout:
stderr: /bin/mkdir: cannot create directory '/root': Permissions denied
That is a critical error, migration was stopped. -
Migration fails with one of the following error messages:
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
Cause
The "root" login is not permitted on the source server.
Resolution
-
Connect to the source Plesk server via SSH.
-
Open the file
/etc/ssh/sshd_config
in a text editor (for example, "vi" editor) and
set thePermitRootLogin
setting to "yes" and remove "#" as shown below:CONFIG_TEXT: PermitRootLogin yes
-
Restart the SSH service:
# service sshd restart
-
Restart migration.
Note: It is possible to migrate with a non-root user. For details, visit Migrating From a Linux Server With Custom Hosting.
Comments
2 comments
If you are migrating and the source server is using Plesk Onyx you might still not be able to do this until you update /etc/ssh/sshd_config with
An easy way to test if your config is going to work before you do the migration is if you ssh into your server as root e.g.
It should ask you for the password.
If it doesn't, it means something is still wrong with your ssh config and migration will not work using username/password method.
@Christopher Gibb
It is not necessary to use password authentication, you may also use SSH keys (as per documentation here).
But the overall idea of "An easy way to test if your config is going to work before you do the migration is if you ssh into your server as root" is absolutely right: if you cannot connect to the source server via SSH using any method of authentication, then something is wrong :)
Please sign in to leave a comment.