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

MariaDB service startup error in debian stretch

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.5.13
    • Fix Version/s: None
    • Component/s: Server
    • Labels:
    • Environment:
      Debian Stretch

      Description

      We can't start mariadb service in debian stretch, we only have this output:

      2022-01-24 11:33:53 0 [Warning] 'debug' is disabled in this build
      2022-01-24 11:33:53 0 [Note] mariadbd (mysqld 10.5.13-MariaDB-1:10.5.13+maria~stretch) starting as process 58180 ...
      2022-01-24 11:33:53 0 [Note] InnoDB: Uses event mutexes
      2022-01-24 11:33:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
      2022-01-24 11:33:53 0 [Note] InnoDB: Number of pools: 1
      2022-01-24 11:33:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2022-01-24 11:33:53 0 [Note] InnoDB: Using Linux native AIO
      2022-01-24 11:33:53 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
      2022-01-24 11:33:53 0 [Note] InnoDB: Completed initialization of buffer pool
      2022-01-24 11:33:53 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=211998879789,211998879789
      2022-01-24 11:33:53 0 [Note] InnoDB: Starting final batch to recover 387 pages from redo log.
      2022-01-24 11:33:54 0 [Note] InnoDB: 128 rollback segments are active.
      2022-01-24 11:33:54 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2022-01-24 11:33:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2022-01-24 11:33:54 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2022-01-24 11:33:54 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2022-01-24 11:33:54 0 [Note] InnoDB: 10.5.13 started; log sequence number 212029548059; transaction id 89176170
      2022-01-24 11:33:54 0 [Note] Plugin 'FEEDBACK' is disabled.
      2022-01-24 11:33:54 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
      2022-01-24 11:33:54 0 [Note] Server socket created on IP: '127.0.0.1'.
      2022-01-24 11:33:54 0 [ERROR] [FATAL] InnoDB: Rec offset 99, cur1 offset 188, cur2 offset 172
      220124 11:33:54 [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.5.13-MariaDB-1:10.5.13+maria~stretch
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467872 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x563c41305558
      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 = 0x7fe121df7b58 thread_stack 0x49000
      addr2line: 2022-01-24 11:33:54 0 [Note] InnoDB: Buffer pool(s) load completed at 220124 11:33:54
      'mariadbd': No hay tal fichero
      mariadbd(my_print_stacktrace+0x2e)[0x563c3f7dba0e]
      Printing to addr2line failed
      mariadbd(handle_fatal_signal+0x38f)[0x563c3f1f531f]
      ??:0(__restore_rt)[0x7fe149a060e0]
      2022-01-24 11:33:54 0 [Note] Reading of all Master_info entries succeeded
      2022-01-24 11:33:54 0 [Note] Added new Master_info '' to hash table
      2022-01-24 11:33:54 0 [Note] mariadbd: ready for connections.
      Version: '10.5.13-MariaDB-1:10.5.13+maria~stretch'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
      linux/raise.c:51(__GI_raise)[0x7fe148dfefff]
      stdlib/abort.c:91(__GI_abort)[0x7fe148e0042a]
      addr2line: 'mariadbd': No hay tal fichero
      mariadbd(+0xd6ef91)[0x563c3f642f91]
      mariadbd(+0xc8f6fc)[0x563c3f5636fc]
      mariadbd(+0xc9f764)[0x563c3f573764]
      mariadbd(+0xc88bb7)[0x563c3f55cbb7]
      mariadbd(+0xc4c515)[0x563c3f520515]
      mariadbd(+0xc524f0)[0x563c3f5264f0]
      mariadbd(+0xdadbc1)[0x563c3f681bc1]
      mariadbd(+0xdadd82)[0x563c3f681d82]
      mariadbd(+0xd7c9a7)[0x563c3f6509a7]
      mariadbd(+0xd8935a)[0x563c3f65d35a]
      mariadbd(+0xd8dc98)[0x563c3f661c98]
      mariadbd(+0xcfb072)[0x563c3f5cf072]
      mariadbd(+0xcfb1ff)[0x563c3f5cf1ff]
      mariadbd(+0xcf6489)[0x563c3f5ca489]
      mariadbd(+0xcf763a)[0x563c3f5cb63a]
      mariadbd(+0xcf7ad4)[0x563c3f5cbad4]
      mariadbd(+0xcaa1be)[0x563c3f57e1be]
      mariadbd(+0xd19726)[0x563c3f5ed726]
      mariadbd(_ZN5tpool10task_group7executeEPNS_4taskE+0x72)[0x563c3f763e92]
      mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x4f)[0x563c3f762d4f]
      ??:0(std::error_code::default_error_condition() const)[0x7fe149528e6f]
      nptl/pthread_create.c:456(start_thread)[0x7fe1499fc4a4]
      x86_64/clone.S:99(clone)[0x7fe148eb4d0f]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): (null)
      Connection ID (thread ID): 0
      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,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
       
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
       
      We think the query pointer is invalid, but we will try to print it anyway.
      Query:
       
      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             15060                15060                processes
      Max open files            32184                32184                files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       15060                15060                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
      

      What could we do?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            stratei Jose Hernández
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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