MySQL Database Cannot Start

Keywords: WordPress + NGINX + SSL - Google Cloud Platform - Technical issue - Services (Apache, MariaDB, MySQL…)

bndiagnostic ID: b7c5f4e6-ba60-c63d-a210-b95472122091

bndiagnostic output:

? Mysql: Found possible issues
? Processes: Found possible issues
? Nginx: Found possible issues
? Connectivity: Found possible issues

bndiagnostic failure reason: The documentation did not make any significant change

Hi all,

MySQL database process is not running and cannot start. I also tried to request access to the logs and it says permission denied. Not sure where to start here to fix this. I’ve increased disk space but no luck.

Hi @eoussetp,

It seems MySQL’s files are corrupt and the server tells you how to recover those files

2022-02-12T16:14:38.522459Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 447864937, calculated checksums for field1: crc32 3044691022/921099872, innodb 3383954853, none 3735928559, stored checksum in      field2 2816245475, calculated checksums for field2: crc32 3044691022/921099872, innodb 3521437860, none 3735928559,  page LSN 0 2870417311, low 4 bytes of LSN at page end 2860674500, page number (if stored to page         already) 511, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be an update undo log page
2022-02-12T16:14:38.522469Z 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can     also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to     recovery.html for information about forcing recovery.
2022-02-12T16:14:38.522473Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or,  there was a failure in tagging the tablespace  as corrupt.
2022-02-12 16:14:38 0x7f11ea1d4740  InnoDB: Assertion failure in thread 139714918958912 in file line 942
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.

you can also take a look at older posts in this forum

We strongly suggest you ask in the official forums of MySQL to recover the database

Note: If you have a backup, it’ll be easier to recover the site

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.