• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Plesk 12 to 12.5 migration failed with cause EOF during negotiation

metalalisa

Basic Pleskian
Code:
/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator generate-migration-list /usr/local/psa/var/modules/panel-migrator/sessions/20160106185107/config.ini --skip-services-checks
[2016-01-06 19:28:11][INFO] Initialize migrator
[2016-01-06 19:28:11][INFO] Load configuration
[2016-01-06 19:28:11][INFO] Target Plesk host: xx.xx.xx.xx
[2016-01-06 19:28:11][INFO] Source Plesk 'source' host: xx.xx.xx.xx
[2016-01-06 19:28:11][INFO] START: Check migrator updates
[2016-01-06 19:28:11][INFO] FINISH: Check migrator updates
[2016-01-06 19:28:11][INFO] START: Check connections
[2016-01-06 19:28:15][INFO] FINISH: Check connections
[2016-01-06 19:28:15][INFO] Check migration compatibility of source and target Plesk versions
[2016-01-06 19:28:15][INFO] START: Fetch basic information about resellers, clients and domains data from source servers
[2016-01-06 19:28:15][INFO] Deploy migration agent to 'xx.xx.xx.xx'
[2016-01-06 19:28:20][ERROR] Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: EOF during negotiation
That is a critical error, migration was stopped.

where can I get some more information about error?

Thanks
 
Yes, I've already found debug.log

There are lines
Code:
+|2016-01-14_08:26:34,547|D|MT|core.run_command||source|Execute remote command: ssh <source_ip> "/usr/bin/test -e /tmp/panel_migrator"
+|2016-01-14_08:26:34,813|D|MT|core.utils.ssh_utils||source|Exit status: 0, stdout: , stderr:
+|2016-01-14_08:26:34,813|D|MT|core.run_command||source|Execute remote command: ssh <source_ip> "/usr/bin/test -e /tmp/panel_migrator/version"
+|2016-01-14_08:26:35,133|D|MT|core.utils.ssh_utils||source|Exit status: 1, stdout: , stderr:
+|2016-01-14_08:26:35,133|D|MT|core.run_command||source|Attempting to run "find /tmp/panel_migrator -maxdepth 1 -type f -printf "%f\0""
+|2016-01-14_08:26:35,133|D|MT|core.run_command||source|Execute remote command: ssh <source_ip> "find /tmp/panel_migrator -maxdepth 1 -type f -printf "%f\0""
+|2016-01-14_08:26:35,372|D|MT|core.utils.ssh_utils||source|Exit status: 0, stdout: , stderr:
+|2016-01-14_08:26:35,372|D|MT|core.run_command||source|Execute remote command: ssh <source_ip> "/usr/bin/test -e /tmp/panel_migrator/version"
+|2016-01-14_08:26:35,615|D|MT|core.utils.ssh_utils||source|Exit status: 1, stdout: , stderr:

Should I send the whole file as private message?
 
Problem solved.

On my source server
Code:
# tail /etc/ssh/sshd_config
Subsystem       sftp    /usr/libexec/openssh/sftp-server

where /usr/libexec/openssh/sftp-server does not exist.

Thanks for help!
 
Back
Top