Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-22145

Mariadb crash due to unknown cause

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.4.6
    • N/A
    • Server
    • None
    • Debian 9

    Description

      Hello,

      MariaDB crashed on Debian 9 due to unknown scenario. Trace:

      2020-04-01  5:00:29 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
      2020-04-01  5:00:29 0 [Note] InnoDB: Using Linux native AIO
      2020-04-01  5:00:29 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2020-04-01  5:00:29 0 [Note] InnoDB: Uses event mutexes
      2020-04-01  5:00:29 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2020-04-01  5:00:29 0 [Note] InnoDB: Number of pools: 1
      2020-04-01  5:00:29 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2020-04-01  5:00:29 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
      2020-04-01  5:00:29 0 [Note] InnoDB: Initializing buffer pool, total size = 20G, instances = 8, chunk size = 128M
      2020-04-01  5:00:29 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-04-01  5:00:29 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2020-04-01  5:00:29 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1864507380390
      2020-04-01  5:00:29 0 [Note] InnoDB: Starting final batch to recover 1539 pages from redo log.
      2020-04-01  5:00:31 0 [Note] InnoDB: Last binlog file '/var/log/mysql/mysql-bin.005935', position 42387505
      2020-04-01  5:00:31 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
      2020-04-01  5:00:31 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-04-01  5:00:31 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-04-01  5:00:31 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-04-01  5:00:31 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-04-01  5:00:31 0 [Note] InnoDB: 10.4.6 started; log sequence number 1864507382292; transaction id 4047471665
      2020-04-01  5:00:31 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2020-04-01  5:00:31 0 [Note] Plugin 'FEEDBACK' is disabled.
      2020-04-01  5:00:31 0 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
      2020-04-01  5:00:31 0 [Note] Starting crash recovery...
      2020-04-01  5:00:31 0 [Note] Crash recovery finished.
      2020-04-01  5:00:31 0 [Note] Server socket created on IP: '0.0.0.0'.
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Page old data size 8520 new data size 8626, page old max ins size 7687 new max ins size 7581
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Page old data size 7453 new data size 7555, page old max ins size 8759 new max ins size 8657
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2020-04-01  5:00:31 2 [ERROR] InnoDB: Page old data size 10581 new data size 10665, page old max ins size 5608 new max ins size 5524
      2020-04-01  5:00:31 2 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Page old data size 7523 new data size 7630, page old max ins size 8690 new max ins size 8583
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Page old data size 7872 new data size 7981, page old max ins size 8337 new max ins size 8228
      2020-04-01  5:00:31 3 [ERROR] InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      2020-04-01  5:00:31 3 [ERROR] [FATAL] InnoDB: Rec offset 99, cur1 offset 14933, cur2 offset 16078
      200401  5:00:31 [ERROR] 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.
       
      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: 10.4.6-MariaDB-1:10.4.6+maria~stretch-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=1002
      thread_count=7
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2336003 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f5afc0009a8
      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 = 0x7f5b5da53bc8 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5578bd5e884e]
      /usr/sbin/mysqld(handle_fatal_signal+0x3af)[0x5578bd07956f]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x110e0)[0x7f60962310e0]
      2020-04-01  5:00:31 0 [Note] Reading of all Master_info entries succeeded
      2020-04-01  5:00:31 0 [Note] Added new Master_info '' to hash table
      2020-04-01  5:00:31 0 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basenam
      e=#' or '--relay-log=mysqld-relay-bin' to avoid this problem.
      2020-04-01  5:00:31 10 [Note] Slave I/O thread: Start asynchronous replication to master 'nprepl@10.10.0.20:3306' in log 'mysql-bin.001564' at position 459599060
      2020-04-01  5:00:31 0 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.4.6-MariaDB-1:10.4.6+maria~stretch-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      2020-04-01  5:00:31 11 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.001564' at position 459599060, relay log './mysqld-relay-bin.003889' position: 6656746
      2020-04-01  5:00:31 10 [Note] Slave I/O thread: connected to master 'nprepl@10.10.0.20:3306',replication started in log 'mysql-bin.001564' at position 459599060
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f609485ffff]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f609486142a]
      /usr/sbin/mysqld(+0xb4d7a1)[0x5578bd3697a1]
      /usr/sbin/mysqld(+0xa82199)[0x5578bd29e199]
      /usr/sbin/mysqld(+0xa84ba3)[0x5578bd2a0ba3]
      /usr/sbin/mysqld(+0xb5bc08)[0x5578bd377c08]
      /usr/sbin/mysqld(+0xb6a0df)[0x5578bd3860df]
      /usr/sbin/mysqld(+0xb71eb8)[0x5578bd38deb8]
      /usr/sbin/mysqld(+0xade13f)[0x5578bd2fa13f]
      /usr/sbin/mysqld(+0xae0239)[0x5578bd2fc239]
      /usr/sbin/mysqld(+0xae100a)[0x5578bd2fd00a]
      /usr/sbin/mysqld(+0xa9a370)[0x5578bd2b6370]
      /usr/sbin/mysqld(+0xb04c54)[0x5578bd320c54]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x74a4)[0x7f60962274a4]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f6094915d0f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0):
      Connection ID (thread ID): 3
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,deriv
      ed_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,exi
      sts_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
       
      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.
      Writing a core file...
      Working directory at /var/lib/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             128465               128465               processes
      Max open files            16364                16364                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       128465               128465               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: core
      

      The load was normal . Is this a known bug ?

      Thank you.

      Attachments

        Activity

          People

            Unassigned Unassigned
            cata06 Catalin Dumitriu
            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.