• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

ERROR: PleskMainDBException: DB query failed: Table 'psa.misc' doesn't exist (db.php:

jcgalvez

Basic Pleskian
Hello,

Today I restarted the server and I cannot login to the plesk panel

I receive the following error:

ERROR: PleskMainDBException: DB query failed: Table 'psa.misc' doesn't exist (db.php:59)
http://kb.parallels.com/plesk-error...+query+failed:+Table+"psa.misc"+doesn"t+exist

On the error I get:


140404 6:23:09 [Note] C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqld.exe: Normal shutdown

140404 6:23:09 [Note] Event Scheduler: Purging the queue. 0 events
140404 6:23:11 [Warning] C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqld.exe: Forcing close of thread 83 user: 'admin'

140404 6:23:11 InnoDB: Starting shutdown...
140404 6:23:11 InnoDB: Shutdown completed; log sequence number 1595675
140404 6:23:11 [Note] C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqld.exe: Shutdown complete

140404 6:24:15 [Note] Plugin 'FEDERATED' is disabled.
140404 6:24:15 InnoDB: The InnoDB memory heap is disabled
140404 6:24:15 InnoDB: Mutexes and rw_locks use Windows interlocked functions
140404 6:24:15 InnoDB: Compressed tables use zlib 1.2.3
140404 6:24:15 InnoDB: Initializing buffer pool, size = 16.0M
140404 6:24:15 InnoDB: Completed initialization of buffer pool
140404 6:24:15 InnoDB: highest supported file format is Barracuda.
140404 6:24:15 InnoDB: Waiting for the background threads to start
140404 6:24:16 InnoDB: 5.5.31 started; log sequence number 1595675
140404 6:24:16 [Note] Server hostname (bind-address): '0.0.0.0'; port: 8306
140404 6:24:16 [Note] - '0.0.0.0' resolves to '0.0.0.0';
140404 6:24:16 [Note] Server socket created on IP: '0.0.0.0'.
140404 6:24:16 [Note] Event Scheduler: Loaded 0 events
140404 6:24:16 [Note] C:\Program Files (x86)\Parallels\Plesk\MySQL\bin\mysqld.exe: ready for connections.
Version: '5.5.31' socket: '' port: 8306 MySQL Community Server (GPL)
140404 6:24:20 [ERROR] Cannot find or open table psa/misc from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

140404 6:26:00 [ERROR] Cannot find or open table psa/cl_param from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

140404 6:26:33 [ERROR] Cannot find or open table psa/ip_addresses from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.

140404 6:27:32 [ERROR] Cannot find or open table psa/misc from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.
 
Back
Top