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

Mariadb 10.11.2 crashes sporadically with Fatal glibc error: malloc.c:3617 (_mid_memalign): assertion failed: !p || chunk_is_mmapped (mem2chunk (p)) || ar_ptr == arena_for_chunk (mem2chunk (p))

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.11.2
    • N/A
    • Platform SUSE
    • OpenSUSE 15.4
      glibc 2.37.9000.233.g16439f419b-lp154.3626.1

    Description

      Hi there,

      After successfully using Mariadb for years, sometime after the last round of updates from 10.9 to 10.10 and 10.11, we're now experiencing almost daily crashes. I'm including the details below.

      It's possible this is related to glibc and nor Mariadb, but I don't have enough expertise to determine that. Also, we updated glibc to the latest version, but the crashes still keep happening.

      https://forums.factorio.com/viewtopic.php?f=7&p=583557 is suspiciously familiar, and one of the comments says a glibc fix was released, but I am not sure in which version, or if that's true at all.

      Fatal glibc error: malloc.c:3617 (_mid_memalign): assertion failed: !p || chunk_is_mmapped (mem2chunk (p)) || ar_ptr == arena_for_chunk (mem2chunk (p))
      230421  5:00:20 [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.11.2-MariaDB-log source revision: cafba8761af55ae16cc69c9b53a341340a845b36
      key_buffer_size=536870912
      read_buffer_size=262144
      max_used_connections=304
      max_threads=2050
      thread_count=195
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5301674 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f76c001acb8
      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 = 0x7f76f8968d28 thread_stack 0x49000
      ??:0(my_print_stacktrace)[0x55f5c6895bdd]
      ??:0(handle_fatal_signal)[0x55f5c6394065]
      ??:0(__restore_rt)[0x7f76f96570a0]
      ??:0(__pthread_kill_implementation)[0x7f76f96a7cec]
      ??:0(__GI_raise)[0x7f76f9656fe2]
      ??:0(__GI_abort)[0x7f76f963f34f]
      ??:0(_IO_peekc_locked.cold)[0x7f76f96400c9]
      ??:0(__libc_assert_fail)[0x7f76f964f183]
      ??:0(_mid_memalign.isra.0)[0x7f76f96b72a2]
      ??:0(std::unique_lock<std::mutex>::unlock())[0x55f5c669f5b9]
      ??:0(std::thread::thread<void (&)()>(void (&)()))[0x55f5c67dc011]
      ??:0(std::thread::thread<void (&)()>(void (&)()))[0x55f5c67ae679]
      ??:0(std::unique_lock<std::mutex>::unlock())[0x55f5c66c7076]
      ??:0(std::unique_lock<std::mutex>::unlock())[0x55f5c66f6aad]
      ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55f5c664e840]
      ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55f5c664eb7b]
      ??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55f5c664f8a0]
      ??:0(Sql_cmd_truncate_table::handler_truncate(THD*, TABLE_LIST*, bool))[0x55f5c628377a]
      ??:0(Sql_cmd_truncate_table::truncate_table(THD*, TABLE_LIST*))[0x55f5c6284360]
      ??:0(Sql_cmd_truncate_table::execute(THD*))[0x55f5c62845de]
      ??:0(mysql_execute_command(THD*, bool))[0x55f5c615bc41]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55f5c6162fae]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55f5c6157fb5]
      ??:0(do_command(THD*, bool))[0x55f5c6156a67]
      ??:0(do_handle_one_connection(CONNECT*, bool))[0x55f5c6267a0f]
      ??:0(handle_one_connection)[0x55f5c6267da4]
      ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55f5c659697d]
      ??:0(start_thread)[0x7f76f96a5eb4]
      ??:0(__clone3)[0x7f76f972d1c8]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f76c000c7c0): truncate table wp_wfKnownFileList
       
      Connection ID (thread ID): 4669297
      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.
      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        unlimited            unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             128319               128319               processes
      Max open files            1048576              1048576              files
      Max locked memory         8388608              8388608              bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       128319               128319               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: |/bin/false
       
      Kernel version: Linux version 6.0.10-x86_64-linode158 (maker@build.linode.com) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1 SMP PREEMPT_DYNAMIC Thu Dec 1 13:16:43 EST 2022
      

      Attachments

        Activity

          People

            serg Sergei Golubchik
            archon810 Artem Russakovskii
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.