Plesk migrator failed from 12.0.18 to 12.5 on different Centos servers

[AmaZili Communication]

Hi !
We are currrently running a centos 6 Plesk 12.0.18 update 70 production server.
We want to migrate accounts to a brand new Centos 7 Plesk 12.5 update 9.


Running the plesk migrator from gui interface results in :

Erreur: Looks like migration can not be started. The most common cause: wrong IP address, administrator login or password specified, so please check it first. Refer logs for details: dowload info log, dowload debug log.

For the logs, we replaced our servers addresses centos7/12.5 with YY.YY.YY.YY and centos6/12.0.18 with XX.XX.XX.XX as well as key with key-encryption-1 and password with password...

info log tells us :

[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.TjEoDhO5 -p 22 -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/ XX.XX.XX.XX:/tmp/panel_migrator/migration_agent/tmp.iMbSABsvEO'' executed locally failed with exit code 255.
stdout:
stderr : Permission denied, please try again.

Permission denied, please try again.

debug file file is as provided as attached file


The ssh is working fine, we can do : ssh [email protected] "cat /usr/passwd" successfully
as well as : ssh [email protected] "cat /usr/passwd" on the other server successfully.

We tried to chmod the /tmp/panel_migrator/ to 777 without any success.

What is going wrong ?
Can someone from Odin help ?

Thanks.

Philippe (AmaZili Communication)

 

[AmaZili Communication]

^^ Up ...

 

[Aleksey Filatev]

Hello!

I am sorry for delay.

Unfortunately, we can not detect root cause of this issue according log... looks like automatic configuration of source/target ssh connection with authentication by keys does not work as expected. Could you please try to configure it manually? Goal is to run rsync w/o asking password.

Following article may be useful: http://unix.stackexchange.com/quest...rompt-with-ssh-with-public-key-authentication.

Also you can create support request or provide your target server credentials to me directly. In both cases we can investigate an issue and provide you solution.

 

[Bitpalast]

Have you limited the SSH access on your machines to specific IP addresses? I remember an issue when we were using migration manager that full SSH access was required. You may want to try to enable access for "ALL" by SSH, else migration manager will fail.

 

[AmaZili Communication]

Thanks Aleksey, I tried all the solutions from the link you provided with no success. /usr/sbin/sshd -d gave me no more indications, see hereunder :

/usr/sbin/sshd -d
debug1: sshd version OpenSSH_5.3p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from YY.YY.YY.YY port 51698
debug1: Client protocol version 2.0; client software version paramiko_1.15.2
debug1: no match: paramiko_1.15.2
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: permanently_set_uid: 74/74
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes128-ctr hmac-sha1 none
debug1: kex: server->client aes128-ctr hmac-sha1 none
debug1: expecting SSH2_MSG_KEXDH_INIT
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user root service ssh-connection method password
debug1: attempt 0 failures 0
debug1: PAM: initializing for "root"
debug1: PAM: setting PAM_RHOST to "server.ip-YY.YY.YY.eu"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: PAM: password authentication accepted for root
debug1: do_pam_account: called
Accepted password for root from YY.YY.YY.YY port 51698 ssh2
debug1: monitor_child_preauth: root has been authenticated by privileged process
debug1: temporarily_use_uid: 0/0 (e=0/0)
debug1: ssh_gssapi_storecreds: Not a GSSAPI mechanism
debug1: restore_uid: 0/0
debug1: SELinux support disabled
debug1: PAM: establishing credentials
debug1: temporarily_use_uid: 0/0 (e=0/0)
debug1: ssh_gssapi_storecreds: Not a GSSAPI mechanism
debug1: restore_uid: 0/0
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 2097152 max 32768
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: session_by_channel: session 0 channel 0
debug1: session_close_by_channel: channel 0 child 0
debug1: session_close: session 0 pid 0
debug1: channel 0: free: server-session, nchannels 1
Read error from remote host YY.YY.YY.YY: Connection reset by peer
debug1: do_cleanup
debug1: PAM: cleanup
debug1: PAM: closing session
debug1: PAM: deleting credentials

Thanks Peter for your input, I tried also your solution with no more succes, remember i already tried to to ssh commands from both sides and it worked perfectly.

Still trying to understand what is going wrong here.