Unable to install wordpress: Got error -1 from storage engine

Created:

2016-11-16 12:42:10 UTC

Modified:

2017-08-16 16:14:01 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Unable to install wordpress: Got error -1 from storage engine

Applicable to:

  • Plesk 11.x for Windows
  • Plesk 12.0 for Windows
  • Plesk 12.5 for Windows

Symptoms

Unable to install APS application (Wordpress, Joomla, etc.), the following error appears:

Error stream: 'Unable to execute SQL statement ( INSERT INTO `wp_comments` (`comment_ID`, `comment_post_ID`, `comment_author`, `comment_author_email`, `comment_author_url`, `comment_author_IP`, `comment_date`, `comment_date_gmt`, `comment_content`, `comment_karma`, `comment_approved`, `comment_agent`, `comment_type`, `comment_parent`, `user_id`) VALUES (1,1,'Mr WordPress','','https://wordpress.org/','',now(),now(),'Hi, this is a comment.\

To delete a comment, just log in and view the post's comments. There you will have the option to edit or delete them.',0,'1','','',0,0)): Got error -1 from storage engine at (SiteApplicationManager::fsaExecuteScript line 503) at execute console command --run-application-script(vconsoleapp::start line 97) at execute "C:\Program Files (x86)\Parallels\Plesk\admin\bin\sappmng.exe" --run-application-script "--script-filename=configure" "--script-name=install" "--user-name=user" "--application-full-name=file:///C:\Program Files (x86)\Parallels\Plesk\var\apspackages\aps7CDE.tmp.zipe382b37d-ae78-a8e1-5b\cache" "--fsa-xml-file=C:/Program Files (x86)/Parallels/Plesk/PrivateTemp/fsaCE79.tmp"(vconsoleapp::run line 107) (Error code 1)'.

The following errors can be found in MySQL log %plesk_dir%Databases\\MySQL\\data\\<server_name>.err :

InnoDB: A new raw disk partition was initialized or
InnoDB: innodb_force_recovery is on: we do not allow
InnoDB: database modifications by the user. Shut down
InnoDB: mysqld and edit my.cnf so that newraw is replaced
InnoDB: with raw, and innodb_force_... is removed.

Cause

MySQL is running with innodb_force_recovery option enabled in %plesk_dir%Databases\\MySQL\\data\\my.ini .

Resolution

Comment out innodb_force_recovery option in %plesk_dir%Databases\\MySQL\\data\\my.ini and restart MySQL service under Start - Services - MySQL Server .

If the service does not start without " innodb_force_recovery " option, refer to How to fix InnoDB corruption cases for the MySQL database KB article.

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