Cannot install or clone WordPress instance: database does not exist

Created:

2017-03-28 09:40:20 UTC

Modified:

2017-08-18 15:09:09 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Cannot install or clone WordPress instance: database does not exist

Applicable to:

  • Plesk Onyx for Linux

Note: This article has the reference to the issues with the fixes available:

  • #EXTWPTOOLK-456 "A WordPress site could not be cloned if proc_open was disabled in PHP settings of the source or destination domain."
    Fixed in:
  • #EXTWPTOOLK-471 "Manually removing a WordPress database without using Plesk could result in inability to install or clone WordPress instances."
    Fixed in:
Please consider updating your server:

Symptoms

Cannot create a clone, the following error is received:

Cloning Failed, database does not exist

The cloned instances are created but are shown with a warning:

Unable to read WordPress configuration file

The following error can be found in /var/log/plesk/panel.log :

ERR [1] '/usr/local/psa/admin/bin/filemng' 'db_user' 'exec' '/var/www/vhosts/example.com' '/usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/bin/wp' '--path=/var/www/vhosts/example.com/test.example.com' 'config-settings' 'get' '--params=DB_NAME,DB_USER,DB_HOST,DOMAIN_CURRENT_SITE,PATH_CURRENT_SITE,MULTISITE,SUBDOMAIN_INSTALL,WP_AUTO_UPDATE_CORE,WP_DEBUG,WP_DEBUG_LOG,WP_DEBUG_DISPLAY,SCRIPT_DEBUG,SAVEQUERIES,WP_AUTO_UPDATE_CORE' '--format=json' failed with code 81.


Plesk database is inconsistent, as the command plesk repair db -n shows:

Inconsistency in the table 'db_users' for the column db_id: No rows

Cause

Plesk database is not consistent.

This is WordPress Toolkit bug with ID #EXTWPTOOLK-471 that will be fixed in one of the updates.

Resolution

As a workaround:

1. Remove all broken cloned instances

2. Fix the database inconsistencies:

# plesk repair db

Have more questions? Submit a request
Please sign in to leave a comment.