• 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.

Issue with Migration Manager

sandeeps85

New Pleskian
Hi,

I have an old plesk server which is running version 11.5. I have now moved to another dedicated server (more powerful) and installed Plesk+License. So I was doing the migration (Both source and destination are running v11.5) from source to destination.

I started the migration manager on the destination but when I fill all the relevant information and click next. I am getting this error on the page


Error: launchpad error (Error code = 2):
== STDERR ====================
Invalid handle passed
==============================




###############################

Here are the debug logs from migration_handler.log


[2013-12-10 05:59:28.116|2371] DEBUG: --> <migration_handler.MigrationGetObjectsListAction object at 0x1595810>
[2013-12-10 05:59:28.116|2371] INFO: parameters: ['20131210055927534']
[2013-12-10 05:59:28.116|2371] INFO: stdin: PleskX
[2013-12-10 05:59:28.120|2371] DEBUG: <migration_handler.MigrationHandlerActionRunner object at 0x7f78e8180e50>: doActivity
[2013-12-10 05:59:28.128|2371] DEBUG: MLOG: init 'migration-backup' (with session=True)
[2013-12-10 05:59:28.128|2371] DEBUG: MLOG: log dir /usr/local/psa/PMM/logs/migration-2013-12-10-05-59-27-162
[2013-12-10 05:59:28.128|2371] DEBUG: MLOG: custom log /usr/local/psa/PMM/logs/migration-2013-12-10-05-59-27-162/backup.log
[2013-12-10 05:59:28.128|2371] WARNING: Session data value file '/usr/local/psa/PMM/msessions/20131210055927534/agent_name' does not exist
[2013-12-10 05:59:28.130|2371] DEBUG: Platform selected: 'PleskX'
[2013-12-10 05:59:28.130|2371] DEBUG: Platform detected: 'Plesk 11.5.30', agent: 'PleskX'
[2013-12-10 05:59:28.135|2371] DEBUG: add '2372' to session worker processes
[2013-12-10 05:59:28.136|2371] INFO: Executing <subprocess[2372] '/usr/local/psa/admin/bin/launchpad --deploy-agent --host=192.168.1.1 --port=22 --login=root --session-path=/usr/local/psa/PMM/msessions/20131210055927534 --agent-name=PleskX --agent-dir=/var/cache/20131210055927534'>
[2013-12-10 05:59:28.559|2371] INFO: Subprocess raised ExecuteException: Subprocess <subprocess[2372] '/usr/local/psa/admin/bin/launchpad --deploy-agent --host=192.168.1.1 --port=22 --login=root --session-path=/usr/local/psa/PMM/msessions/20131210055927534 --agent-name=PleskX --agent-dir=/var/cache/20131210055927534'> was finished with exit code 2
== STDOUT ====================

== STDERR ====================
Invalid handle passed
[2013-12-10 05:59:28.560|2371] ERROR: Launchpad could not deploy agent: Subprocess <subprocess[2372] '/usr/local/psa/admin/bin/launchpad --deploy-agent --host=192.168.1.1 --port=22 --login=root --session-path=/usr/local/psa/PMM/msessions/20131210055927534 --agent-name=PleskX --agent-dir=/var/cache/20131210055927534'> was finished with exit code 2
== STDOUT ====================

== STDERR ====================
Invalid handle passed
[2013-12-10 05:59:28.560|2371] DEBUG: <migration_handler.MigrationGetObjectsListAction object at 0x1595810>: response
[2013-12-10 05:59:28.563|2371] INFO: Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?>
<response>
<errcode>1000</errcode>
<errmsg>launchpad error (Error code = 2):
== STDERR ====================
Invalid handle passed
==============================
</errmsg>
</response>
 
Well. There is error after execution this command:

/usr/local/psa/admin/bin/launchpad --deploy-agent --host=192.168.1.1 --port=22 --login=root --session-path=/usr/local/psa/PMM/msessions/20131210055927534 --agent-name=PleskX --agent-dir=/var/cache/20131210055927534

First of all you need to check that host 192.168.1.1 is accessible on port 22 as root user. Then check that you have enough free disk space on / and /var partitions. Check that /var/cache directory has correct permissions. Try to run this command manually with increased debug level and check output.
 
Did you provide a correct root password for your source server (192.168.1.1) ?
You need also to ensure that you can SSH the source server from your destination server ...(in otherwards, ensure that all SSH connections are fine)
 
I did supplied the correct root password, I have verified this by supplying an incorrect password and i can clearly see the error at that time was related to access.

I have also verified that the there is enough space in / and /var to hold the backups. /var has free space in TeraBytes.
 
What error do you get when you execute
Code:
/usr/local/psa/admin/bin/launchpad --deploy-agent --host=192.168.1.1 --port=22 --login=root --session-path=/usr/local/psa/PMM/msessions/20131210055927534 --agent-name=PleskX --agent-dir=/var/cache/20131210055927534
directly from SHELL?
 
I am getting the below message when i run this command from command line:

Unable to parse command line: password is required unless --help or -h requested
 
This seems to be an error in the SSHD on the source system. Possible solutions would be:

1. A manual migration, described using the Migration Manager like this:

http://kb.parallels.com/en/1152/

2. A downgrade to the original version of SSHD (not updated) on the source server. The package can be found on SUSE 10.0, for example, but this package has known bugs, it should be used only temporarily and are restricted (eg by firewall) access. You can do this by importing

Code:
rpm-Uvh - force restart

If restarting the sshd fail, restart the VPS please.

Otherwise, Igor can advice on a better and more proficient solution!
 
Thanks Abdi,

I was trying manual migration and tried the steps mentioned in kb.

But there seems to be problem too, After i run ./PleskX.pl --dump-all the file dump.xml as mentioned in the article is not created.

And without dump.xml the migration manager on destination server does not work.
 
Am so sorry for the challenges you are facing: (At this point it's really hard to tell the cause without hands on ..)
Anyhow, please check and ensure that in your /etc/my.cnf you have (higher values) for (eg)

Code:
wait_timeout=500
connect_timeout=100

Also, how many domain names are you migrating? If less than 10 domains then you can actually do "real" manual data transfer and it would take minutes to get you done (depending on the data sizes and distances of both servers).how:

1. You re-create the hosting accounts on the destination server and
2. From the source you do copy ALL data (/var/qmail/mailnames/* + /var/www/vhosts/domains.com/httpdocs/*) to your destination server.
3. For MySQL, you just dump the respective domain's dbs and move them too ...(alternatively you can run a single dump of all dbs and move them to the new server and then restore them too...)

The above steps are really in basic explanation ..
Trouble shooting plesk migration can be time consuming especially if you are not upto the task!
 
Hi Abdi,

I've approx 100 domains to move with db and configuration. And there are also some domains that are redirected on the server. So manual migration will be tedious and very time consuming in this case.

I don't know now what to do, because the error is just staying there for ever.
 
Back
Top