Cloning fails in Plesk WP Toolkit: WP Toolkit was not able to finish running an operation on this site in 1800 seconds

Symptoms

• WordPress cloning fails after 1800 seconds (30 minutes) with the following error message:

  PLESK_ERROR: WP Toolkit was not able to finish running an operation on this site in 1800 seconds, so the operation was terminated. This could mean that your WordPress installation might be infected with malware. Check the wp-config.php file of the installation for potential malware code or run an anti-virus scan. If you cannot find any traces of malware, try running the operation again later."

• The process itself is active during the cloning. This can be checked with the command:

  # ps -e f ww | grep wordpress

• Database tables of this WordPress website have lots of records with site URL (around ~150 000).

Cause

During the WordPress cloning process, website URLs are replaced in all the tables with a new URL. WP Toolkit replaces them one by one, as a result, if there are many records to update, it takes longer than 1800 seconds (30 minutes). The speed will be improved in future WordPress versions in scope of EXTWPTOOLK-2856.

Resolution

Increase the wpCliTimeoutHeavy value in the Plesk configuration file panel.ini:

1. Log in to Plesk.

2. Install the Panel.ini Editor extension for Plesk.

3. Open the extension and switch to the Editor tab.

4. Add the following lines:

   CONFIG_TEXT: [ext-wp-toolkit]
   wpCliTimeoutHeavy = 7200

5. Save the changes.