Database cloning stuck

[OysteinB]

I was using Plesk panel 10.3 on Centos 6.
Cloning of database is stuck.
Message: "Cloning the database xxx to the database xxxx. You will be notified of the progress by e-mail ([email protected])."
This message has been there for over a week. Server hard-restarted, Apace restarted, even upgraded to Plesk 11.
Nothing changes, and I cannot seem to abort the cloning in any way.
I cannot start cloning of another database either.

All ideas are most welcome.

Oystein

 

[SvetlanaS]

Is your plesk upgraded from previous version?
Did you try to clone mySQL locally or on another server?
Which version of microupdate (MU) is installed?
And please, specify the steps that lead you to such a result.

 

[ØysteinB]

I read about the exact same problem here:
http://forum.parallels.com/showthread.php?t=246252
Several people had this problem and I could not see any solution in this thread, except upgrading Plesk.
So I tried upgrading from Plesk 10.3 to 11. That did not solve the problem.
Database = mysql

The problem could have appeared when a cloning took very long time.
I might have deleted the target database before the cloning process was finished.
Database dump size is normally around 50MB.

Although the message says so I don't think that the cloning process is running.
I guess that the problem is just a process indicator flag somewhere to prevent new actions to be started.

 

[abdi]

Did you try to clone mySQL locally or on another server?

If to another server, make sure you have port 3306 or the MySQL port opened in your firewall or also ensure the destination server allows remote database access ...

 

[ØysteinB]

I tried cloning on the local server.
Cloning has never been a problem before.

This is clearly a Plesk bug and all I need help to is to abort the stalled cloning process.

 

[SvetlanaS]

I read about the exact same problem here:
http://forum.parallels.com/showthread.php?t=246252
Several people had this problem and I could not see any solution in this thread, except upgrading Plesk.
So I tried upgrading from Plesk 10.3 to 11. That did not solve the problem.
Database = mysql

The problem could have appeared when a cloning took very long time.
I might have deleted the target database before the cloning process was finished.
Database dump size is normally around 50MB.

Although the message says so I don't think that the cloning process is running.
I guess that the problem is just a process indicator flag somewhere to prevent new actions to be started.

I've upgraded my Plesk from 10.3->11 too. And create MySQL DB with size=56M. This DB was cloned successfully on local server to existing DB and to newly created. Did you installed all MU's (I mean MU#13) for 10.3 (with fix of this issue)?

Also look for logs. What kind of errors apeared after failed cloning?