- Plesk Onyx for Windows
MySQL on Windows is crashing with the following error:
CONFIG_TEXT: Faulting application name: mysqld.exe, version: 220.127.116.11, time stamp: 0x58ccdb65
Faulting module name: mysqld.exe, version: 18.104.22.168, time stamp: 0x58ccdb65
Exception code: 0x80000003
Fault offset: 0x00000000002bb162
Faulting process id: 0x1764
Faulting application start time: 0x01d4639065120bae
Faulting application path: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Faulting module path: C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld.exe
Report Id: f33b3065-14ac-4735-b77c-3653d732bef3
Plesk SQL server cannot be started with the following error:
CONFIG_TEXT: Incorrect function (Error code 1) at Start service PleskSQLServer at (service::startStopService line 997)
The following can be observed in
CONFIG_TEXT: InnoDB: Page directory corruption: infimum not pointed to
InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 00.....000; asc ;
InnoDB: End of page dump
CONFIG_TEXT: [ERROR] InnoDB: Page [page id: space=0, page number=237] log sequence number 1737623713 is in the future! Current system log sequence number 1704662866.
[ERROR] 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.
In case it is PleskSQL service, Plesk is inaccessible with:
CONFIG_TEXT: ERROR 500
SQLSTATE[HY000]  No connection could be made because the target machine actively refused it.
In Event Viewer > Windows Logs > Application, the following messages are found:
CONFIG_TEXT: InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 252683671 and the end 252687827.For more information, see Help and Support Center at http://www.mysql.com.
InnoDB: Plugin initialization aborted with error Generic errorFor more information, see Help and Support Center at http://www.mysql.com.
Plugin 'InnoDB' init function returned error.For more information, see Help and Support Center at http://www.mysql.com.
Plugin 'InnoDB' registration as a STORAGE ENGINE failed.For more information, see Help and Support Center at http://www.mysql.com.
Most InnoDB corruptions are hardware-related. Corrupted page writes can be caused by power failures or bad memory. The issue also can be caused by using network attached storage (NAS) and allocating InnoDB databases on it.
Plesk has two MySQL servers on a Windows platform:
- One is for Plesk-related databases on port 8306: [Windows] Local MySQL server for Plesk-related databases (psa, apsc, horde)
- Another is for client's MySQL databases on port 3306: [Windows] Local MySQL server for customers' databases
Note: To start/stop/restart PleskSQLserver/MySQL, it is recommended to use Plesk Services Monitor.
Click on a section to expand
For Linux, refer to the following article: How to fix InnoDB corruption cases for the MySQL database?