Symptoms
-
The following error is shown in Plesk:
PLESK_INFO: ERROR: PleskMainDBException
MySQL query failed: Incorrect information in file: ‘./psa/misc.frm’
PLESK_INFO: ERROR: PleskDBException: Unable to connect to database: mysql_connect(): No such file or directory /var/run/mysqld/mysqld.sock (Error code: 2002). Please check that database server is started and accessible. (Abstract.php:69)
PLESK_INFO: ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] No such file or directory
PLESK_INFO: ERROR: Zend_Db_Adapter_Exception: SQLSTATE[HY000] [2002] Connection refused:
0: /usr/local/psa/admin/externals/Zend/Db/Adapter/Pdo/Abstract.php:144 -
Domain overview page on Domains > example.com is not accessible:
500 Server Error
Type SB_Facade_Exception_Generic
Message
File generic.php
Line 33 -
Opening WordPress Toolkit results in the following error:
PLESK_INFO: Server Error 500 Zend_Db_Adapter_Exception
Type Zend_Db_Adapter_Exception
Message SQLSTATE[HY000] [2002]
No such file or directory
File Abstract.php Line 144 -
Plesk upgrade fails with the following error:
PLESK_INFO: DATABASE ERROR!!!
Database psa database found, but version undefined -
A table cannot be properly queried with the
SELECTstatement:MYSQL_LIN: select * from db_example.misc;
ERROR 1033 (HY000): Incorrect information in file: ‘./db_example/misc.frm’ -
The following information can be found in the MySQL log file
/var/log/mysql/error.log,/var/log/mysqld.log, or/var/log/mariadb/mariadb.log:150704 19:09:27 InnoDB: Waiting for the background threads to start
150704 19:09:28 InnoDB: Error: tablespace size stored in header is 3712 pages, but
150704 19:09:28 InnoDB: the sum of data file sizes is only 3072 pages
150704 19:09:28 InnoDB: Cannot start InnoDB. The tail of the system tablespace is
150704 19:09:28 InnoDB: missing. Have you edited innodb_data_file_path in my.cnf in an
150704 19:09:28 InnoDB: inappropriate way, removing ibdata files from there?
150704 19:09:28 InnoDB: You can set innodb_force_recovery=1 in my.cnf to force
150704 19:09:28 InnoDB: a startup if you are trying to recover a badly corrupt database.
InnoDB: Assertion failure in thread 3876 in file ha_innodb.cc line 17352
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Assertion failure in thread 140154354255616 in file trx0purge.c line 848
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery
[ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace database/table uses space ID: 882 at filepath
[Note] InnoDB: Starting crash recovery.
[ERROR] InnoDB: Tablespace 11904 was not found at ./example_db/example1.ibd…
