• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

How to kill database cloning on Plesk.

PolM

New Pleskian
Hello, I have a database Clone process on progress for more than 5 days. The process is locked, and I can't start another clone process while it's on progress. How can I kill that process? I tryed restarting plesk, and restarting the server but doesn't work.
I'm on Plesk 11.0.9 Update #35 on DEBIAN 6.0.5
Thank's for all.
 
Solved

http://blogs.reliablepenguin.com/2012/06/16/plesk-howto-clear-hung-database-copy



Recent versions of Plesk include a Make a Copy feature for databases. Unfortunately, on occasion the copy will fail but the copy task will not be removed. Then youll see a message like this every time you go to the affected database in Plesk.

You can view a list of the current tasks with the following command from a root ssh login:

echo "select * from longtasks" | \
mysql --password=`cat /etc/psa/.psa.shadow` -u admin psa

You can clear the task by running the following command:

echo "delete from longtasks" | \
mysql --password=`cat /etc/psa/.psa.shadow` -u admin psa
 
Back
Top