• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

migration error

Y

yuvallbr

Guest
I'm trying to migrate from confixx2.0 on Suse8.1
to plesk 7.5 on Fedora 2
The first step succeeds, I get the page with the information about the source server, and the "select objects" or "dump all" .
I do "Next >>" and it fails with the message:
Failed to upload the migration agent
Cannot transfer agent to the remote host
Fatal migration error

on the source server I looked at the sshd log and I see "Accepted password for root from.."
7 times befre I get the error message in plesk. so the problem is not the root login or password .
Thanks, Yuval.
 
Originally posted by yuvallbr
I'm trying to migrate from confixx2.0 on Suse8.1
to plesk 7.5 on Fedora 2
The first step succeeds, I get the page with the information about the source server, and the "select objects" or "dump all" .
I do "Next >>" and it fails with the message:
Failed to upload the migration agent
Cannot transfer agent to the remote host
Fatal migration error

Logs (in the /usr/local/psa/PMM/var) may be helpful to investigate problem.
 
migration.error

this is the migration.errors file,
I really cant make any sense from it:

<?xml version="1.0"?>
<messages><message code="CantTransferAgentException" severity="error"><context>virtual void plesk::DeployAgentAction::execute()</context><file>launchpad/actions.cpp</file><line>235</line><text>Cannot transfer agent to the remote host</text><message code="SshUnknownException" severity="error"><context>void plesk::SshTransfer::wait()</context><file>launchpad/SshTransfer.cpp</file><line>541</line><text>Fatal migration error</text></message></message></messages>
 
Re: migration.error

Originally posted by yuvallbr
this is the migration.errors file,
I really cant make any sense from it:

There is migration.log, which sometimes contains valuable information.
 
MySQL error

now I made some progress!
I get a MySQL error in the migration.log:


[02:07:57 31.01.2006 | pid 17049]:5; readResponse|poll |waiting 2 handles beginning from 0
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|poll |1 handles have data
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|handle 1|(14) read 5 bytes
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|handle 1|(14) data[ERROR]
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|poll |waiting 2 handles beginning from 0
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|poll |1 handles have data
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|handle 1|(14) read 202 bytes
[02:08:00 31.01.2006 | pid 17049]:5; readResponse|handle 1|(14) data[ 1054 at line 1: Unknown column 'hostname' in 'field list'
ERROR 2005: Unknown MySQL Server Host '-B' (1)
Error: Can not connect to Confixx database (unable to execute sql: select hostname from admin)



I checked the database, and indeed the table admin exists, but without the column hostname.
 
Re: MySQL error

Originally posted by yuvallbr
Error: Can not connect to Confixx database (unable to execute sql: select hostname from admin)

I checked the database, and indeed the table admin exists, but without the column hostname.

Seems to be bug in PMM, not your fault. Try to contact support stressing the fact it is an bugreport, not the usual support request.
 
Back
Top