- Plesk for Linux
WordPress installation with Smart Update enabled cannot be updated.
The following entries are found in
CONFIG_TEXT: ERR [extension/wp-toolkit] The cloning of instance WordPress instance #53 ('https://example.com') was failed: 'Cannot create a database. You must have reached the maximum number of databases allowed by the subscription settings.'
ERR [extension/wp-toolkit] Unable to process auto updates for WordPress instance #53 ('https://example.com'): Smart Update could not be completed automatically. Please try running the update manually. Details: Failed to clone the installation: 'Cannot create a database. You must have reached the maximum number of databases allowed by the subscription settings.'
Subscription databases count (C) multiplied by 2 is greater than the limit (L) set for the subscription under Subscriptions > example.com > [Customize] > Resources tab.
For example, the limit (L) is 2 with 2 databases already existing in the subscription (C):
Databases can be removed during the execution of WordPress Scheduled task (Tools & Settings > Scheduled Tasks >
/usr/local/psa/admin/bin/php -dauto_prepend_file=sdk.php '/usr/local/psa/admin/plib/modules/wp-toolkit/scripts/instances-auto-update.php')
#EXTWPTOOLK-3312 " Smart Update failure no longer has a slim chance to accidentally remove the database of the source website under certain rare circumstances. "
- WordPress Toolkit 4.3.0 04 September 2019
If update is not possible for some reason you may try the following
Until the bug is fixed, use one of the following workarounds:
- Disable the Smart Update feature:
Go to WordPress and choose the installation for which you want to disable Smart Update.
On the installation card, click View next to Updates and toggle off Smart Update.
- Increase the database number limit for the subscription:
Navigate to Subscriptions > example.com > [Customize] > Resources tab
Set the double limit for subscription's databases number compared to the current number of databases present in the subscription. For example, if there are 3 databases currently registered on the subscription, set the limit to 6.
Warning: After resource limits are changed for the subscription, it becomes locked and is no longer synchronized with the service plan. To avoid that, change the respective limit on the service plan level at Service Plans > <Service plan name> > Resources tab.