• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

8.6 to 8.6 single client migration stuck

M

MikkyX

Guest
Hi,
I am migrating a single client from one Plesk box to another. Both boxes are running Plesk 8.6.0. The migration process has currently taken three hours - to move one client and two domain names? Unacceptable. What's even more unacceptable is that it now appears to be stuck. For at least 45 minutes the Migration tool on the destination server has been refreshing with this content:

Done:
2 domain(s) out of 2
1 client(s) out of 1

Remaining:
0 domain(s)
0 client(s)
If it's finished why doesn't it just set up the domains and quit so I can get on with remapping DNS?

On the source server, this process is running:
29004 ? R 23:19 perl /migration/supervisor.3742/PleskX.pl --dump-accounts=-

There are a couple of other copies of the same Perl script running but they haven't been going for 23+ minutes.

My load average has gone higher than usual as a result. I have the above folder, filled with archival files for the migration manager to use - everything it needs is there.

On the destination server I have this folder: /usr/local/psa/PMM/var/2009-03-11-08.50.04.82503. tailing the migration.log in this folder gives me these lines, repeated over and over again at 5-10 second intervals:

[09:57:51|DEBG: 4274: p.Ssh] Reading data to the file /usr/local/psa/PMM/var/2009-03-11-08.50.04.82503/dumping-status.xml.tmp
[09:57:51|DEBG: 4274: p.Ssh] Reading data from the remote file /migration/supervisor.3742/dumping-status.xml
[09:57:51|DEBG: 4274: p.Ssh] Executing cat /migration/supervisor.3742/dumping-status.xml on the remote host
[09:57:51|DEBG: 4274: p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/supervisor.3742/dumping-status.xml'
[09:58:01|DEBG: 4274: p.Ssh] Execution finished with return code 0
[09:58:01|DEBG: 4274: p.libssh2pp.Channel] Closed

dumping-status.xml contains this content, both on the source server and the remote server:
{?xml version="1.0" encoding="UTF-8"?}
{agent-dump-status}
{account}ACCOUNT NAME{/account}
{domain}DOMAIN NAME{/domain}
{accounts-left}0{/accounts-left}
{domains-left}0{/domains-left}
{/agent-dump-status}

(I've replaced the regular angle brackets with { and } because this forum thinks they're image tags or something....)

Everything says the migration is completed, so why isn't Plesk moving on? Is it just going to sit here stuck until the migration.log fills the server?

What can I do?
 
Last edited by a moderator:
I can help assist you with this migration which is not working properly.

I know how to do the migration by hand if needed and how to also use secondary methods to accomplish this.

Please contact me via PM/etc. Thanks.
 
We are also getting the same issue.
showing the logs
|DEBG:26375:p.libssh2pp.Session] Opening SSH channel for command 'cat /migration/supervisor.26317/dumping-status.xml'
|DEBG:26375:p.Ssh] Execution finished with return code 0
|DEBG:26375:p.libssh2pp.Channel] Closed
|DEBG:26375:p.Ssh] Reading data to the file /usr/local/psa/PMM/var/2011-10-07-07.33.28.891213/dumping-status.xml.tmp

Regards
Mahendra
 
Back
Top