Migration manager hangs with no error message

[InternetPower]

I'm having a problem with the 10.0.1 Migration Manager.

I created a dump with PleskX.pl on the source server, copied the data to the destination server, then from the web interface I start a new migration.
Select "Transfer data already processed by the migration agent and located on the local host" and put in the "Migration data file location" the location of the dump file : /tmp/migration/dump.xml then click "Next" and in a few seconds the page refreshes and I'm back to the "Server Tools" with no error message.

How can I solve this problem, is it possible to do the migration from console , or is there some log in my system about the problem ?

 

[IgorG]

Look at this thread http://forum.parallels.com/showthread.php?t=106336
Maybe it will help.

 

[InternetPower]

Yes, I've already read it.
I've a full license, and there is a lot of space on the disk.
The very first time I ran the migration when I clicked next It asked for IPs, and that the original IP will be changed to the destination server shared IPs and so on, the it stopped when it found on the server the same domain to be already present. Then I deleted the domain and re-run the migration but after that very first time every time I run the migration it hangs as i described.

I do not know where to find logs to debug the process, or if there is any log somewhere on the system.

I think it's an important part of Plesk to be able to migrate domains from one system to another, so it's strange that the migration assistant seems - from what I've read in the forums, and from my direct experience - a bit buggy.

 

[lhwparis]

try a migration direct from your old server to the new server without preparing it on the old server? but be aware of the existing bugs in the migration manager like not migrating mail folders and so on...

 

[InternetPower]

Ok, but why it worked the first time, and now it's stuck ?
How can i "un-stuck" the process , and get again the screen that ask for ip address change, and go on?

 

[lhwparis]

there is a temporary-files folder you can specifiy in the first migration step. did you have a look into this folder and delete all data their? eventually some old temp-data cause this problem.