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

server crash InnoDB: Failing assertion: foreign->referenced_table ->n_foreign_key_checks_running > 0

Details

    Description

      Hi,

      Every 2 or 3 days, a server (not always the same) crashes with the error below.
      Please tell me if you need more information.

      Thanks,
      Laurent

      log file :

      2014-10-08 03:10:49 7fffedd97700  InnoDB: Assertion failure in thread 140737183840000 in file row0upd.cc line 442
      InnoDB: Failing assertion: foreign->referenced_table ->n_foreign_key_checks_running > 0
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      141008  3:10:49 [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 http://kb.askmonty.org/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.0.12-MariaDB-wsrep
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=45
      max_threads=1026
      thread_count=27
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2385333 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7fffcea39008
      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 = 0x7fffedd96ce0 thread_stack 0x48000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb914fb]
      /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x743318]
      /lib64/libpthread.so.0[0x368040f500]
      /lib64/libc.so.6(gsignal+0x35)[0x36800328a5]
      /lib64/libc.so.6(abort+0x175)[0x3680034085]
      /usr/sbin/mysqld[0x94c73a]
      /usr/sbin/mysqld[0x94d0d0]
      /usr/sbin/mysqld[0x951322]
      /usr/sbin/mysqld[0x9327b3]
      /usr/sbin/mysqld[0x8996bf]
      /usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x162)[0x74cbe2]
      /usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x11d2)[0x6700c2]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1539)[0x5d9d19]
      /usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x8352ce]
      /usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8b)[0x83a8cb]
      /usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x165)[0x83adc5]
      /usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x6a0)[0x838550]
      /usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x606)[0x839826]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x59db)[0x5de1bb]
      /usr/sbin/mysqld[0x5e0412]
      /usr/sbin/mysqld[0x5e0dcb]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x16d0)[0x5e28a0]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x132)[0x5e3072]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x54b)[0x6a190b]
      /usr/sbin/mysqld(handle_one_connection+0x42)[0x6a1a02]
      /lib64/libpthread.so.0[0x3680407851]
      /lib64/libc.so.6(clone+0x6d)[0x36800e890d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fffe9f580c8): is an invalid pointer
      Connection ID (thread ID): 1276767
      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=off,table_elimination=on,extended_keys=on,exists_to_in=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.
      141008 03:10:49 mysqld_safe Number of processes running now: 0
      141008 03:10:49 mysqld_safe WSREP: not restarting wsrep node automatically
      141008 03:10:49 mysqld_safe mysqld from pid file /var/lib/mysql//ies-ams-att-04.pid ended

      Attachments

        Activity

          laurent_fighiera Laurent Fighiera created issue -
          elenst Elena Stepanova made changes -
          Field Original Value New Value
          Description Hi,

          Every 2 or 3 days, a server (not always the same) crashes with the error below.
          Please tell me if you need more information.

          Thanks,
          Laurent

          log file :
          2014-10-08 03:10:49 7fffedd97700 InnoDB: Assertion failure in thread 140737183840000 in file row0upd.cc line 442
          InnoDB: Failing assertion: foreign->referenced_table ->n_foreign_key_checks_running > 0
          InnoDB: We intentionally generate a memory trap.
          InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
          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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
          InnoDB: about forcing recovery.
          141008 3:10:49 [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 http://kb.askmonty.org/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.0.12-MariaDB-wsrep
          key_buffer_size=134217728
          read_buffer_size=131072
          max_used_connections=45
          max_threads=1026
          thread_count=27
          It is possible that mysqld could use up to
          key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2385333 K bytes of memory
          Hope that's ok; if not, decrease some variables in the equation.

          Thread pointer: 0x0x7fffcea39008
          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 = 0x7fffedd96ce0 thread_stack 0x48000
          /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb914fb]
          /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x743318]
          /lib64/libpthread.so.0[0x368040f500]
          /lib64/libc.so.6(gsignal+0x35)[0x36800328a5]
          /lib64/libc.so.6(abort+0x175)[0x3680034085]
          /usr/sbin/mysqld[0x94c73a]
          /usr/sbin/mysqld[0x94d0d0]
          /usr/sbin/mysqld[0x951322]
          /usr/sbin/mysqld[0x9327b3]
          /usr/sbin/mysqld[0x8996bf]
          /usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x162)[0x74cbe2]
          /usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x11d2)[0x6700c2]
          /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1539)[0x5d9d19]
          /usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x8352ce]
          /usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8b)[0x83a8cb]
          /usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x165)[0x83adc5]
          /usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x6a0)[0x838550]
          /usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x606)[0x839826]
          /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x59db)[0x5de1bb]
          /usr/sbin/mysqld[0x5e0412]
          /usr/sbin/mysqld[0x5e0dcb]
          /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x16d0)[0x5e28a0]
          /usr/sbin/mysqld(_Z10do_commandP3THD+0x132)[0x5e3072]
          /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x54b)[0x6a190b]
          /usr/sbin/mysqld(handle_one_connection+0x42)[0x6a1a02]
          /lib64/libpthread.so.0[0x3680407851]
          /lib64/libc.so.6(clone+0x6d)[0x36800e890d]

          Trying to get some variables.
          Some pointers may be invalid and cause the dump to abort.
          Query (0x7fffe9f580c8): is an invalid pointer
          Connection ID (thread ID): 1276767
          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=off,table_elimination=on,extended_keys=on,exists_to_in=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.
          141008 03:10:49 mysqld_safe Number of processes running now: 0
          141008 03:10:49 mysqld_safe WSREP: not restarting wsrep node automatically
          141008 03:10:49 mysqld_safe mysqld from pid file /var/lib/mysql//ies-ams-att-04.pid ended
          Hi,

          Every 2 or 3 days, a server (not always the same) crashes with the error below.
          Please tell me if you need more information.

          Thanks,
          Laurent

          log file :
          {noformat}
          2014-10-08 03:10:49 7fffedd97700 InnoDB: Assertion failure in thread 140737183840000 in file row0upd.cc line 442
          InnoDB: Failing assertion: foreign->referenced_table ->n_foreign_key_checks_running > 0
          InnoDB: We intentionally generate a memory trap.
          InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
          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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
          InnoDB: about forcing recovery.
          141008 3:10:49 [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 http://kb.askmonty.org/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.0.12-MariaDB-wsrep
          key_buffer_size=134217728
          read_buffer_size=131072
          max_used_connections=45
          max_threads=1026
          thread_count=27
          It is possible that mysqld could use up to
          key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2385333 K bytes of memory
          Hope that's ok; if not, decrease some variables in the equation.

          Thread pointer: 0x0x7fffcea39008
          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 = 0x7fffedd96ce0 thread_stack 0x48000
          /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb914fb]
          /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x743318]
          /lib64/libpthread.so.0[0x368040f500]
          /lib64/libc.so.6(gsignal+0x35)[0x36800328a5]
          /lib64/libc.so.6(abort+0x175)[0x3680034085]
          /usr/sbin/mysqld[0x94c73a]
          /usr/sbin/mysqld[0x94d0d0]
          /usr/sbin/mysqld[0x951322]
          /usr/sbin/mysqld[0x9327b3]
          /usr/sbin/mysqld[0x8996bf]
          /usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhPh+0x162)[0x74cbe2]
          /usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x11d2)[0x6700c2]
          /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1539)[0x5d9d19]
          /usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x8352ce]
          /usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8b)[0x83a8cb]
          /usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x165)[0x83adc5]
          /usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x6a0)[0x838550]
          /usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x606)[0x839826]
          /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x59db)[0x5de1bb]
          /usr/sbin/mysqld[0x5e0412]
          /usr/sbin/mysqld[0x5e0dcb]
          /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x16d0)[0x5e28a0]
          /usr/sbin/mysqld(_Z10do_commandP3THD+0x132)[0x5e3072]
          /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x54b)[0x6a190b]
          /usr/sbin/mysqld(handle_one_connection+0x42)[0x6a1a02]
          /lib64/libpthread.so.0[0x3680407851]
          /lib64/libc.so.6(clone+0x6d)[0x36800e890d]

          Trying to get some variables.
          Some pointers may be invalid and cause the dump to abort.
          Query (0x7fffe9f580c8): is an invalid pointer
          Connection ID (thread ID): 1276767
          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=off,table_elimination=on,extended_keys=on,exists_to_in=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.
          141008 03:10:49 mysqld_safe Number of processes running now: 0
          141008 03:10:49 mysqld_safe WSREP: not restarting wsrep node automatically
          141008 03:10:49 mysqld_safe mysqld from pid file /var/lib/mysql//ies-ams-att-04.pid ended
          {noformat}
          elenst Elena Stepanova made changes -
          Assignee Jan Lindström [ jplindst ]
          serg Sergei Golubchik made changes -
          Fix Version/s 10.0 [ 16000 ]
          jplindst Jan Lindström (Inactive) made changes -
          Assignee Jan Lindström [ jplindst ] Nirbhay Choubey [ nirbhay_c ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Affects Version/s 10.0.12-galera [ 16303 ]
          Affects Version/s 10.0.12 [ 15201 ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Fix Version/s 10.0.15-galera [ 17501 ]
          Fix Version/s 10.0 [ 16000 ]
          nirbhay_c Nirbhay Choubey (Inactive) made changes -
          Fix Version/s 10.0.13-galera [ 16800 ]
          Fix Version/s 10.0.15-galera [ 17501 ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 55510 ] MariaDB v3 [ 64845 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 64845 ] MariaDB v4 [ 148297 ]

          People

            nirbhay_c Nirbhay Choubey (Inactive)
            laurent_fighiera Laurent Fighiera
            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.