Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
11.4.2
-
None
-
CentOS Stream 8
Linux version 4.18.0-547.el8.x86_64
Server version: 11.4.2-MariaDB-log source revision: 3fca5ed772fb75e3e57c507edef2985f8eba5b12
key_buffer_size=131072
read_buffer_size=10485760
max_used_connections=26
max_threads=65537
thread_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1342204602 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f3a06211f18
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 = 0x7f4682d05c78 thread_stack 0x49000
Printing to addr2line failed
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55c7a220d88e]
/usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x55c7a1d0c625]
/lib64/libpthread.so.0(+0x12d20)[0x7f468532dd20]
/lib64/libc.so.6(gsignal+0x10f)[0x7f468467852f]
/lib64/libc.so.6(abort+0x127)[0x7f468464be65]
/usr/sbin/mariadbd(+0x6d25de)[0x55c7a194d5de]
/usr/sbin/mariadbd(+0xdc7c90)[0x55c7a2042c90]
/usr/sbin/mariadbd(+0xdb790e)[0x55c7a203290e]
/usr/sbin/mariadbd(+0xe7b5bb)[0x55c7a20f65bb]
/usr/sbin/mariadbd(+0xf17978)[0x55c7a2192978]
/usr/sbin/mariadbd(+0xf18210)[0x55c7a2193210]
/usr/sbin/mariadbd(+0xe22ebc)[0x55c7a209debc]
/usr/sbin/mariadbd(+0xdd3a06)[0x55c7a204ea06]
/usr/sbin/mariadbd(+0xe43113)[0x55c7a20be113]
/usr/sbin/mariadbd(+0xd3f042)[0x55c7a1fba042]
/usr/sbin/mariadbd(_Z17ha_rollback_transP3THDb+0xd8)[0x55c7a1d10e48]
/usr/sbin/mariadbd(_Z19trans_rollback_stmtP3THD+0xa7)[0x55c7a1bdbd27]
/usr/sbin/mariadbd(_ZN14rpl_group_info25slave_close_thread_tablesEP3THD+0x50)[0x55c7a1bc0eb0]
/usr/sbin/mariadbd(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0xfbf)[0x55c7a1e296bf]
/usr/sbin/mariadbd(_ZN9Log_event11apply_eventEP14rpl_group_info+0x77)[0x55c7a1e215c7]
/usr/sbin/mariadbd(+0x77ba00)[0x55c7a19f6a00]
/usr/sbin/mariadbd(handle_slave_sql+0x173a)[0x55c7a1a0053a]
/usr/sbin/mariadbd(+0xc9720e)[0x55c7a1f1220e]
/lib64/libpthread.so.0(+0x81ca)[0x7f46853231ca]
/lib64/libc.so.6(clone+0x43)[0x7f46846638d3]
CentOS Stream 8 Linux version 4.18.0-547.el8.x86_64 Server version: 11.4.2-MariaDB-log source revision: 3fca5ed772fb75e3e57c507edef2985f8eba5b12 key_buffer_size=131072 read_buffer_size=10485760 max_used_connections=26 max_threads=65537 thread_count=9 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1342204602 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f3a06211f18 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 = 0x7f4682d05c78 thread_stack 0x49000 Printing to addr2line failed /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55c7a220d88e] /usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x55c7a1d0c625] /lib64/libpthread.so.0(+0x12d20)[0x7f468532dd20] /lib64/libc.so.6(gsignal+0x10f)[0x7f468467852f] /lib64/libc.so.6(abort+0x127)[0x7f468464be65] /usr/sbin/mariadbd(+0x6d25de)[0x55c7a194d5de] /usr/sbin/mariadbd(+0xdc7c90)[0x55c7a2042c90] /usr/sbin/mariadbd(+0xdb790e)[0x55c7a203290e] /usr/sbin/mariadbd(+0xe7b5bb)[0x55c7a20f65bb] /usr/sbin/mariadbd(+0xf17978)[0x55c7a2192978] /usr/sbin/mariadbd(+0xf18210)[0x55c7a2193210] /usr/sbin/mariadbd(+0xe22ebc)[0x55c7a209debc] /usr/sbin/mariadbd(+0xdd3a06)[0x55c7a204ea06] /usr/sbin/mariadbd(+0xe43113)[0x55c7a20be113] /usr/sbin/mariadbd(+0xd3f042)[0x55c7a1fba042] /usr/sbin/mariadbd(_Z17ha_rollback_transP3THDb+0xd8)[0x55c7a1d10e48] /usr/sbin/mariadbd(_Z19trans_rollback_stmtP3THD+0xa7)[0x55c7a1bdbd27] /usr/sbin/mariadbd(_ZN14rpl_group_info25slave_close_thread_tablesEP3THD+0x50)[0x55c7a1bc0eb0] /usr/sbin/mariadbd(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0xfbf)[0x55c7a1e296bf] /usr/sbin/mariadbd(_ZN9Log_event11apply_eventEP14rpl_group_info+0x77)[0x55c7a1e215c7] /usr/sbin/mariadbd(+0x77ba00)[0x55c7a19f6a00] /usr/sbin/mariadbd(handle_slave_sql+0x173a)[0x55c7a1a0053a] /usr/sbin/mariadbd(+0xc9720e)[0x55c7a1f1220e] /lib64/libpthread.so.0(+0x81ca)[0x7f46853231ca] /lib64/libc.so.6(clone+0x43)[0x7f46846638d3]
Description
2024-07-16 7:32:15 7 [ERROR] InnoDB: We detected index corruption in an InnoDB type table. You have to dump + drop + reimport the table or, in a case of widespread corruption, dump all InnoD
B tables and recreate the whole tablespace. If the mariadbd server crashes after the startup or when you dump the tables. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-mod
es/ for information about forcing recovery.
2024-07-16 7:32:15 7 [ERROR] mariadbd: Index for table 'total_main_log' is corrupt; try to repair it
2024-07-16 7:32:15 7 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table prol2.total_main_log; Index for table 'total_main_log' is corrupt; try to repair it, Error_
code: 1034; handler error HA_ERR_CRASHED; the event's master log mysql-bin.000834, end_log_pos 0, Gtid 0-2-1062387710, Internal MariaDB error code: 1034
2024-07-16 07:32:15 0x7f4682d08700 InnoDB: Assertion failure in file /home/buildbot/amd64-rhel-8-rpm-autobake/build/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/storage/innobase/page/page0
zip.cc line 4291
InnoDB: Failing assertion: slot_rec
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mariadbd startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
240716 7:32:15 [ERROR] mysqld got signal 6 ; Sorry, we probably made a mistake, and this is a bug.
Attachments
Issue Links
- duplicates
-
-
- Closed
-