Bug #98962 InnoDB: Assertion failure in thread 139789969819392 in file page0cur.c line 928
Submitted: 16 Mar 2020 11:56 Modified: 16 Mar 2020 12:46
Reporter: Krzysztof Szortyka Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Errors Severity:S1 (Critical)
Version: OS:Ubuntu
Assigned to: CPU Architecture:Any
Tags: innodb, MySQL

[16 Mar 2020 11:56] Krzysztof Szortyka
Description:
I have problem with start mysql. I get error:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

I changed in my.cnf
innodb_force_recovery = 4

and I get it in logs:

InnoDB: Log scan progressed past the checkpoint lsn 1817344809866
200316 12:40:00  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1817346456946
200316 12:40:00  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
 47 200316 12:40:01  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 0:1367238, should be 0:1367750!
200316 12:40:01  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 0:1367239, should be 0:1367751!
200316 12:40:01  InnoDB: Assertion failure in thread 139789969819392 in file page0cur.c line 928
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

How to repeat:
I have no idea

Suggested fix:
I changed in my.cnf
innodb_force_recovery = 6
and mysql theoretically started.
mysql>

but I get in logs:
Version: '5.5.37-0ubuntu0.12.10.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
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.
[16 Mar 2020 12:46] MySQL Verification Team
Thank you for the bug report. Version 5.5 is EOL please upgrade to newer version.

https://endoflife.software/applications/databases/mysql