00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003e80c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000204b21fffbd5f00000040000000801fffbd5f00000040000000806a5073aa0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007b00ec3f50a829e; asc I e _ @ _ @ jPs ;
InnoDB: End of page dump
InnoDB: Page may be a transaction system page
2023-11-01T06:46:41.507239Z 1 [ERROR] [MY-011899] [InnoDB] [FATAL] Unable to read page [page id: space=0, page number=5] into the buffer pool after 100 attempts. The most probable cause of this error may be that the table has been corrupted. Or, the table was compressed with with an algorithm that is not supported by this instance. If it is not a decompress failure, you can try to fix this problem by using innodb_force_recovery. Please see http://dev.mysql.com/doc/refman/8.0/en/ for more details. Aborting...
2023-11-01T06:46:41.508179Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:555 thread 23005621483264
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:46:41 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x564d08b8a700
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 = 14ec69e56d20 thread_stack 0x60000
/www/server/mysql/bin/mysqld(my_print_stacktrace(unsigned char const, unsigned long)+0x41) [0x564d038dd601]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x313) [0x564d02732083]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x14ec95c85420]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb) [0x14ec9536f00b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b) [0x14ec9534e859]
/www/server/mysql/bin/mysqld(+0xea3700) [0x564d0245c700]
/www/server/mysql/bin/mysqld(ib::fatal::fatal()+0xd0) [0x564d03bffed0]
/www/server/mysql/bin/mysqld(Buf_fetch<Buf_fetch_normal>::read_page()+0x1a6) [0x564d03c65fe6]
/www/server/mysql/bin/mysqld(Buf_fetch_normal::get(buf_block_t&)+0x170) [0x564d03c6e140]
/www/server/mysql/bin/mysqld(Buf_fetch<Buf_fetch_normal>::single_page()+0x59) [0x564d03c6e229]
/www/server/mysql/bin/mysqld(buf_page_get_gen(page_id_t const&, page_size_t const&, unsigned long, buf_block_t, Page_fetch, char const, unsigned long, mtr_t, bool)+0x1d6) [0x564d03c6f256]
/www/server/mysql/bin/mysqld(Double_write::get(mtr_t)+0x56) [0x564d03c77666]
/www/server/mysql/bin/mysqld(Double_write::init_v1(unsigned int&, unsigned int&)+0x141) [0x564d03c77c51]
/www/server/mysql/bin/mysqld(dblwr::v1::init()+0x1b) [0x564d03c7808b]
/www/server/mysql/bin/mysqld(srv_start(bool)+0x1b5b) [0x564d03ba2c4b]
/www/server/mysql/bin/mysqld(+0x242470e) [0x564d039dd70e]
/www/server/mysql/bin/mysqld(dd::bootstrap:😃DSE_dict_init(THD, dict_init_mode_t, unsigned int)+0x9e) [0x564d0366c19e]
/www/server/mysql/bin/mysqld(dd::upgrade_57::do_pre_checks_and_initialize_dd(THD)+0x1a9) [0x564d038b0889]
/www/server/mysql/bin/mysqld(+0x1233d46) [0x564d027ecd46]
/www/server/mysql/bin/mysqld(+0x28dad52) [0x564d03e93d52]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x14ec95c79609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x14ec9544b133]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED
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.