Description:
InnoDB: End of page dump
2023-10-31T07:34:53.603893Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 605723794, calculated checksums for field1: crc32 1862675323/1715019590, innodb 3017047818, none 3735928559, stored checksum in field2 1359156322, calculated checksums for field2: crc32 1862675323/1715019590, innodb 1935580650, none 3735928559, page LSN 2552588239 1064823489, low 4 bytes of LSN at page end 1951679811, page number (if stored to page already) 1837485677, space id (if created with >= MySQL-4.1.1 and stored already) 821414241
2023-10-31T07:34:53.603901Z 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 http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-10-31T07:34:53.603905Z 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.
2023-10-31 13:04:53 0x7f3e71cee700 InnoDB: Assertion failure in thread 139906174084864 in file ut0ut.cc line 921
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:34:53 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x55b94bbedbab]
/usr/sbin/mysqld(handle_fatal_signal+0x377)[0x55b94b478937]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f3e8b355420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f3e8ae4400b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f3e8ae23859]
/usr/sbin/mysqld(+0x6adadc)[0x55b94b44eadc]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x55b94bf9e4d6]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x2f6)[0x55b94bfdac16]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x12f)[0x55b94c04fc4f]
/usr/sbin/mysqld(io_handler_thread+0xa8)[0x55b94bf3d3a8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f3e8b349609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f3e8af20133]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
How to repeat:
InnoDB: End of page dump
2023-10-31T07:34:53.603893Z 0 [Note] InnoDB: Uncompressed page, stored checksum in field1 605723794, calculated checksums for field1: crc32 1862675323/1715019590, innodb 3017047818, none 3735928559, stored checksum in field2 1359156322, calculated checksums for field2: crc32 1862675323/1715019590, innodb 1935580650, none 3735928559, page LSN 2552588239 1064823489, low 4 bytes of LSN at page end 1951679811, page number (if stored to page already) 1837485677, space id (if created with >= MySQL-4.1.1 and stored already) 821414241
2023-10-31T07:34:53.603901Z 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 http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2023-10-31T07:34:53.603905Z 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.
2023-10-31 13:04:53 0x7f3e71cee700 InnoDB: Assertion failure in thread 139906174084864 in file ut0ut.cc line 921
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:34:53 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68199 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x55b94bbedbab]
/usr/sbin/mysqld(handle_fatal_signal+0x377)[0x55b94b478937]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420)[0x7f3e8b355420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f3e8ae4400b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f3e8ae23859]
/usr/sbin/mysqld(+0x6adadc)[0x55b94b44eadc]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x55b94bf9e4d6]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x2f6)[0x55b94bfdac16]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x12f)[0x55b94c04fc4f]
/usr/sbin/mysqld(io_handler_thread+0xa8)[0x55b94bf3d3a8]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f3e8b349609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f3e8af20133]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
