How Long Should It Take To 'Retrieve' Information From Source Server?

[tybross]

Hi good SWSoft folk,
I'm currently trying to migrate from a Plesk 8.0.1 server to a Plesk 8.2.1 server.

I have checked everything on the source server, and all is fine with SSH, port 22 etc.

However, my migration attempts have failed at the "Retrieving information on the host xx.xx.xxx.xxx is in progress" It just keeps reloading the screen and I never manage to get to the point where I can see/select the Migration Objects. It just keeps reloading the 'retrieving' screen for hours.

I have examined the migration-created files in the usr/local/psa/PMM/var on the destination server and can't seem to find anything wrong.

For example, the migration.log shows the following on the destination server:

[06:36:49|INFO: 2459.log] Launchpad started : /usr/local/psa/admin/sbin/launchpad --host=xx.xx.xxx.xxx --login=root --session-path=/usr/local/psa/PMM/var/2007-11-01-06.36.43.446442 --send-scout
[06:36:49|DEBG: 2459.libssh2pp.Socket] Socket created
[06:36:49|DEBG: 2459.libssh2pp.Socket] Connecting to xx.xx.xxx.xxx:22
[06:36:49|DEBG: 2459.libssh2pp.Socket] Resolving xx.xx.xxx.xxx
[06:36:49|DEBG: 2459.libssh2pp.Socket] xx.xx.xxx.xxx was resolved to xx.xx.xxx.xxx
[06:36:49|DEBG: 2459.libssh2pp.Socket] Connected
[06:36:49|DEBG: 2459.libssh2pp.Session] Trying to start SSH session
[06:36:49|DEBG: 2459.libssh2pp.Session] Selected aes256-cbc encryption method
[06:36:49|DEBG: 2459.libssh2pp.Session] SSH session started successfully
[06:36:49|DEBG: 2459.libssh2pp.Session] Requested authorization for user root
[06:36:49|DEBG: 2459.libssh2pp.Session] Getting userauth methods for user 'root'
[06:36:49|DEBG: 2459.libssh2pp.Session] Got the following allowed userauth methods: publickey,gssapi-with-mic,password
[06:36:49|DEBG: 2459.libssh2pp.Session] Trying 'password' authentication
[06:36:49|DEBG: 2459.libssh2pp.Session] Authenticated succesfully
[06:36:49|DEBG: 2459.Ssh] Executing sh -c cd\ \;\ perl on the remote host
[06:36:49|DEBG: 2459.libssh2pp.Session] Opening SSH channel for command 'sh -c cd\ \;\ perl'
[06:36:49|DEBG: 2459.Ssh] remote stdout -> <?xml version="1.0"?><scout-result>

The migration.status file contains the following:

<?xml version="1.0"?>
<migration-status><agent action="deploy"><host>xx.xx.xxx.xxx</host></agent></migration-status>

The supervisor.log just keeps getting bigger as the "Retrieving information on the host xx.xx.xxx.xxx is in progress" keeps reloading itself and causing the same entries in the supervisor.log to be repeated:

2007-11-01 07:08:04,476 INFO Packet succesfully validated.
2007-11-01 07:08:14,337 INFO Incoming packet:
<?xml version="1.0" encoding="UTF-8"?><action><get-status/></action>
2007-11-01 07:08:14,337 INFO Packet succesfully validated.
2007-11-01 07:08:14,340 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?><action-response action-internal-name="SendScoutState">
<working>
<agent action="deploy">
<host>xx.xx.xxx.xxx</host>
</agent>
</working>
</action-response>

I would greatly appreciate it if someone can shed some light on what/why I can't seem to get the migration objects from the source server. Thanks in advance to anyone who can help with this.

 

[Monica@]

Hi.

Make sure there is no firewall restrictions between the source and target server. Also, such problem can be if you have SSH version 1 on the source server, Plesk doesn't work with SSH 1, only with SSH 2.
Probably the following link can give you some hints:
http://kb.swsoft.com/en/2112

Can you ssh from the destination server to the source server? Are you starting migration as root? If not, the user must be in sudoers.

 

[mccool]

I had a similar problem, and it turned out that the files created by the migration manager on the source server had filled the hard drive.

While this is probably not the cause of your problem, I thought I'd mention it in case anyone else falls fowl of this one.

It was a bit annoying that the destination server' migration manager didn't mention it, just kept refreshing on the 'retrieving' screen.

So be sure to check you've plenty of spare disk space on both destination AND source servers.

I guess if I had red point 5 on http://kb.swsoft.com/en/2112 more closely I would have avoided the problem.

Happy migrating!