XMLWordPrintable

Details

    Description

      Hi team,

      I want to report a bug related with the corrupted index in our database system, we have receive this error log:

      2024-09-05  9:06:33 3649856359 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: .//undo003
      2024-09-05  9:06:33 3649856359 [ERROR] InnoDB: File './/undo003' is corrupted
      2024-09-05  9:06:33 3649856359 [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 InnoDB 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-modes/ for information about forcing recovery.
      2024-09-05  9:06:33 3649856359 [ERROR] mariadbd: Index for table 'trx_game_b2b' is corrupt; try to repair it
      2024-09-05  9:06:33 3649856359 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: .//undo003
      2024-09-05  9:06:33 3649856359 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: .//undo003
      2024-09-05 09:06:33 0x7f1004137700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-11.4.3/storage/innobase/trx/trx0purge.cc line 190
      InnoDB: Failing assertion: undo_page
      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.
      240905  9:06:33 [ERROR] mysqld got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 11.4.3-MariaDB-ubu2004-log source revision: 5ab81ffe0097a22a774957df28c5223cf0201de3
      key_buffer_size=16777216
      read_buffer_size=131072
      max_used_connections=2652
      max_threads=65537
      thread_count=106
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 142758750 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f01c408b138
      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...
      2024-09-05  9:06:33 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown
      stack_bottom = 0x7f1004136c78 thread_stack 0x30000
      /usr/sbin/mariadbd(my_print_stacktrace+0x32)[0x55c76c6bf1c2]
      /usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x55c76c179875]
      sigaction.c:0(__restore_rt)[0x7f101decb420]
      addr2line: DWARF error: section .debug_info is larger than its filesize! (0x93f189 vs 0x530f70)
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f101d9d100b]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f101d9b0859]
      /usr/sbin/mariadbd(+0x6e7b31)[0x55c76bd68b31]
      /usr/sbin/mariadbd(+0x6e43e6)[0x55c76bd653e6]
      /usr/sbin/mariadbd(+0x74726c)[0x55c76bdc826c]
      /usr/sbin/mariadbd(+0xeffc94)[0x55c76c580c94]
      /usr/sbin/mariadbd(+0xeffced)[0x55c76c580ced]
      /usr/sbin/mariadbd(+0xef2e2d)[0x55c76c573e2d]
      /usr/sbin/mariadbd(+0xef1af5)[0x55c76c572af5]
      /usr/sbin/mariadbd(+0xdee04a)[0x55c76c46f04a]
      /usr/sbin/mariadbd(_Z17ha_rollback_transP3THDb+0xe0)[0x55c76c17da50]
      /usr/sbin/mariadbd(_Z14trans_rollbackP3THD+0xab)[0x55c76c03349b]
      /usr/sbin/mariadbd(_Z21mysql_execute_commandP3THDb+0x2b1d)[0x55c76bef2f6d]
      /usr/sbin/mariadbd(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e7)[0x55c76bee0747]
      /usr/sbin/mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjb+0x10cd)[0x55c76beed1ed]
      /usr/sbin/mariadbd(_Z10do_commandP3THDb+0x13e)[0x55c76beef55e]
      /usr/sbin/mariadbd(_Z11tp_callbackP13TP_connection+0x8c)[0x55c76c10010c]
      /usr/sbin/mariadbd(+0xc97a0d)[0x55c76c318a0d]
      /usr/sbin/mariadbd(+0xd413a6)[0x55c76c3c23a6]
      nptl/pthread_create.c:478(start_thread)[0x7f101debf609]
      addr2line: DWARF error: section .debug_info is larger than its filesize! (0x93f189 vs 0x530f70)
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f101daad353]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f01c4241b30): ROLLBACK
       
      Connection ID (thread ID): 3649856359
      Status: KILL_SERVER
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=off,sargable_casefold=on
       
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /mnt/data/mysql
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             257138               257138               processes
      Max open files            32768                32768                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       257138               257138               signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E
       
      Kernel version: Linux version 5.4.0-132-generic (buildd@lcy02-amd64-059) (gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022
      

      It said that Index for table 'trx_game_b2b' is corrupt; try to repair it. After that it was automatically restarted.

      Please kindly help with this issue because it can potentially blocked the transaction flow.

      Thanks in advance!

      Attachments

        Issue Links

          Activity

            People

              debarun Debarun Banerjee
              ritxman Martin Prakasa
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.