Description:
2024-07-04T05:59:45.599550Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 10000 (requested 15000)
2024-07-04T05:59:45.599553Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 3495 (requested 4000)
2024-07-04T05:59:45.790192Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-04T05:59:45.791296Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.0) starting as process 10145
2024-07-04T05:59:45.806950Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-04T05:59:47.164012Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-07-04T05:59:47.503121Z 0 [System] [MY-010229] [Server] Starting XA crash recovery...
2024-07-04T05:59:47.509618Z 0 [System] [MY-010232] [Server] XA crash recovery finished.
2024-07-04T05:59:47.596828Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-07-04T05:59:47.596869Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-07-04T05:59:47.630126Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.4.0' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server - GPL.
2024-07-04T05:59:47.884147Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2024-07-04T05:59:48.537623Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: mtr0log.cc:652:total > (ulint)(log_ptr - log_start) thread 140053774853888
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.4/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2024-07-04T05:59:48Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=81cab89ed2db7c42febe17c8891874ccdf3c420f
Thread pointer: 0x7f60bc0008c0
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 = 7f60cf7fd980 thread_stack 0x100000
#0 0x103fb76 _ZL18print_fatal_signaliP9siginfo_t
#1 0x103ffbf _Z15my_server_abortv
#2 0x21a7429 _Z8my_abortv
#3 0x23e1a66 _Z23ut_dbg_assertion_failedPKcS0_m
#4 0x22e07e7 _ZL20close_and_reopen_logRPhRPKhS3_RP5mtr_tRmS7_.isra.0
#5 0x22e2fe1 _Z25mlog_open_and_write_indexP5mtr_tPKhPK12dict_index_t9mlog_id_tmRPh
#6 0x22ff857 _Z19page_cur_delete_recP10page_cur_tPK12dict_index_tPKmP5mtr_t
#7 0x2420e65 _Z30btr_cur_optimistic_delete_funcP9btr_cur_tP5mtr_t
#8 0x2352c52 _ZL34row_purge_remove_clust_if_poss_lowP12purge_node_tm
#9 0x2356071 _Z14row_purge_stepP9que_thr_t
#10 0x2313657 _Z15que_run_threadsP9que_thr_t
#11 0x23b505f _Z9trx_purgemmb
#12 0x238ecd3 _Z28srv_purge_coordinator_threadv
#13 0x22c8001 _ZN15Detached_threadclIPFvvEJEEEvOT_DpOT0_
#14 0x2bd0363 execute_native_thread_routine
#15 0x7f6124404ea4 start_thread
#16 0x7f61228c5b0c clone
#17 0xffffffffffffffff <unknown>
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
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.
How to repeat:
Status: NOT_KILLED
