• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Plesk Migrator error exit code 12

francescokr

New Pleskian
Hi,
I want to migrate from plesk 12 to other server with plesk 12.5, i have started the plesk migrator but take this error (i have replaced in the code ip address with "SOURCE IP ADDRESS"):

Code:
[2016-02-05 14:50:56][INFO] START: Check connections
[2016-02-05 14:50:59][INFO] FINISH: Check connections
[2016-02-05 14:50:59][INFO] Check migration compatibility of source and target Plesk versions
[2016-02-05 14:50:59][INFO] START: Fetch basic information about resellers, clients and domains data from source servers
[2016-02-05 14:50:59][INFO] Deploy migration agent to 'SOURCE IP ADDRESS'
[2016-02-05 14:51:00][ERROR] Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Command '/bin/sh -c 'rsync -rltgo -e '"'"'ssh -i /usr/local/psa/admin/.ssh/id_dsa.1ngsh53X -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_12_5_pmm_shared/ root@SOURCE IP ADDRESS:/tmp/panel_migrator/migration_agent/tmp.MufxwZZQ9Z'' executed locally failed with exit code 12.
stdout:
stderr:Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).

rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6]

That is a critical error, migration was stopped.

Someone know how to resolve?

Thanks
 
Thank you for the reply.
I have tried to execute on both server the command "chattr -i /root/.ssh" but to remove the -i parameter just i execute the command on the shell?

Ask this because then that i execute "chattr -i /root/.ssh" on both server, i have tried the migration but take the same error, so it try to execute the -i on the command.
 
May help you.
This is my destination (new) server:
Destination.PNG
This is my source (actual) server:
SourceServer.PNG

is normal that in the new server i have not the authorized_keys ?

I also see that not exist the directory .ssh in /usr/local/psa/admin/ (in my source server (actual) ) is normal?
 
Last edited:
Hello!

On Unix Plesk Migrator uses rsync over ssh to deploy dump agent (application to perform dump of your source Plesk 12.0) on your source server. Before this it performs configuring of ssh to use keys:

1. Plesk Migrator generates dsa key on your target Plesk 12.5 server and place it in ~/.ssh. Identity name is random according template id_dsa.XXXXXXXX, so full path to generated key should looks like /root/.ssh/id_dsa.hkQj12PH.
2. Then using provided root ssh access Plesk Migrator places just generated public key (content of file /root/.ssh/id_dsa.hkQj12PH.pub) into ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2 on your source Plesk 12 server.
3. Finally Plesk Migrator run rsync and pass path to identity file via ssh -i option.
4. After completing Plesk Migrator perform cleanup: remove generated keys on target and remove public key from authorized_keys files on source. So you can not find noted files/lines on your servers after migration.

Issue which you faced could occurs because specific sshd configuration on your source. I suggest you to perform steps 1-3 manually and check ability to perform simple ssh connection from target to source without password:

1. Generate keys on target using keygen utility
2. Place public key into authorized_keys on your source
3. Try to perform ssh connection from target to source using -i option with path to you private key

I expect, that you will get similar issue in this case. If not, we need to continue investigation.
 
Back
Top