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

Failing assertion: my_atomic_load32_explicit(&lock->lock_word, MY_MEMORY_ORDER_RELAXED) == X_LOCK_DECR

    XMLWordPrintable

    Details

      Description

      I started seeing the following crash on August 26th. Since I received 4 of them. I don't have any hardware errors and nothing else suspicious is logged. InnoDB is not complaining about data corruption etc.. I only get this assertion failure and then a crash.

      InnoDB: Failing assertion: my_atomic_load32_explicit(&lock->lock_word, MY_MEMORY_ORDER_RELAXED) == X_LOCK_DECR
      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 mysqld 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.
      200826 19:38:25 [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.3.24-MariaDB
      key_buffer_size=1048576000
      read_buffer_size=33554432
      max_used_connections=101
      max_threads=102
      thread_count=22
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17737955 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f05fdc2ca28
      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 = 0x7f065355ad30 thread_stack 0x49000
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      ======= Backtrace: =========
      /lib64/libc.so.6(__fortify_fail+0x37)[0x7f07589d9577]
      /lib64/libc.so.6(+0x1166f2)[0x7f07589d76f2]
      /lib64/libc.so.6(+0x1184d7)[0x7f07589d94d7]
      /usr/sbin/mysqld(my_addr_resolve+0xda)[0x5629c874e32a]
      /usr/sbin/mysqld(my_print_stacktrace+0x1c2)[0x5629c87376b2]
      /usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x5629c81cca4f]
      /lib64/libpthread.so.0(+0xf630)[0x7f075a627630]
      /lib64/libc.so.6(gsignal+0x37)[0x7f07588f7387]
      /lib64/libc.so.6(abort+0x148)[0x7f07588f8a78]
      /usr/sbin/mysqld(+0x4ed8a0)[0x5629c7f078a0]
      /usr/sbin/mysqld(+0xa657c6)[0x5629c847f7c6]
      /usr/sbin/mysqld(+0xb132a4)[0x5629c852d2a4]
      /usr/sbin/mysqld(+0xb34cbb)[0x5629c854ecbb]
      /usr/sbin/mysqld(+0xad4ddf)[0x5629c84eeddf]
      /usr/sbin/mysqld(+0xb02174)[0x5629c851c174]
      /usr/sbin/mysqld(+0xb03f8b)[0x5629c851df8b]
      /usr/sbin/mysqld(+0xb0480c)[0x5629c851e80c]
      /usr/sbin/mysqld(+0xae0961)[0x5629c84fa961]
      /usr/sbin/mysqld(+0xad16ee)[0x5629c84eb6ee]
      /usr/sbin/mysqld(+0xad6d9c)[0x5629c84f0d9c]
      /usr/sbin/mysqld(+0xac9bf8)[0x5629c84e3bf8]
      /usr/sbin/mysqld(+0xa37fb2)[0x5629c8451fb2]
      /usr/sbin/mysqld(+0xa3b49e)[0x5629c845549e]
      /usr/sbin/mysqld(+0x95be77)[0x5629c8375e77]
      /usr/sbin/mysqld(_ZN7handler18ha_index_next_sameEPhPKhj+0x1c5)[0x5629c81d3225]
      /usr/sbin/mysqld(+0x613fed)[0x5629c802dfed]
      /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x211)[0x5629c8021c21]
      /usr/sbin/mysqld(+0x5fcecc)[0x5629c8016ecc]
      /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x1de)[0x5629c8021bee]
      /usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xa8b)[0x5629c8045b4b]
      /usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x5629c8045d63]
      /usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x11a)[0x5629c804426a]
      /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cc)[0x5629c8044d7c]
      /usr/sbin/mysqld(+0x4daf06)[0x5629c7ef4f06]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x63ba)[0x5629c7fed8ca]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x36d)[0x5629c7ff063d]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xfe1)[0x5629c7ff1ed1]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x11b)[0x5629c7ff416b]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1d6)[0x5629c80caa86]
      /usr/sbin/mysqld(handle_one_connection+0x3d)[0x5629c80cab9d]
      /lib64/libpthread.so.0(+0x7ea5)[0x7f075a61fea5]
      /lib64/libc.so.6(clone+0x6d)[0x7f07589bf8dd]
      ======= Memory map: ========
      

      I now also think that it is data related. I was running 10.3.24 for 2 weeks before getting the first crash. Since then It came once every 2 days. I rolled back to 10.3.23 4 days ago, and I have not had crashes since... it's probably too early to say but it seems like only 10.3.24 is affected. I run a lot of 10.0 and 10.1 versions and they don't crash out with the latest updates.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              thiru Thirunarayanan Balathandayuthapani
              Reporter:
              glucz Geza Lucz
              Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration