Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-3620

LP #1652698: Assertion failure in file trx0trx.ic line 213

    XMLWordPrintable

    Details

      Description

      **Reported in Launchpad by Alex Ilievski last update 27-12-2016 07:17:07

      We are getting repeated crashes with the following assertion failure. A crash is occurring every 4-5 days.

      mysqld Ver 5.7.16-10 for Linux on x86_64 (Percona Server (GPL), Release 10, Revision a0c7d0d)

      2016-12-27 03:59:23 0x7fee3bf7d700 InnoDB: Assertion failure in thread 140661185042176 in file trx0trx.ic line 213
      InnoDB: Failing assertion: !trx->has_search_latch
      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.7/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      16:59:23 UTC - 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.
      Attempting to collect some information that could help diagnose the problem.
      As this is a crash and something is definitely wrong, the information
      collection process might fail.
      Please help us make Percona Server better by reporting any
      bugs at http://bugs.percona.com/

      key_buffer_size=8388608
      read_buffer_size=131072
      max_used_connections=144
      max_threads=1025
      thread_count=24
      connection_count=24
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 415798 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7fee545e2000
      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 = 7fee3bf7cd00 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xec814c]
      /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x79e231]
      /lib64/libpthread.so.0[0x3c2be0f7e0]
      /lib64/libc.so.6(gsignal+0x35)[0x3c2ba325e5]
      /lib64/libc.so.6(abort+0x175)[0x3c2ba33dc5]
      /usr/sbin/mysqld[0x76ccf8]
      /usr/sbin/mysqld[0x76270e]
      /usr/sbin/mysqld[0xfb1635]
      /usr/sbin/mysqld(_Z18close_thread_tableP3THDPP5TABLE+0x27a)[0xc48e0a]
      /usr/sbin/mysqld(_Z19close_thread_tablesP3THD+0x33b)[0xc494ab]
      /usr/sbin/mysqld[0xd0546b]
      /usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x1e6)[0xd05786]
      /usr/sbin/mysqld[0xceef9c]
      /usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x1e1)[0xd01ba1]
      /usr/sbin/mysqld(_ZN4JOIN14prepare_resultEv+0x6d)[0xce4ddd]
      /usr/sbin/mysqld(_ZN4JOIN4execEv+0x80)[0xc764e0]
      /usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x17d)[0xce570d]
      /usr/sbin/mysqld[0x75d927]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x4375)[0xca84f5]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x5d5)[0xcab9a5]
      /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x92f)[0xcac35f]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xcadcf7]
      /usr/sbin/mysqld(handle_connection+0x2a0)[0xd70e60]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xedf604]
      /lib64/libpthread.so.0[0x3c2be07aa1]
      /lib64/libc.so.6(clone+0x6d)[0x3c2bae8aad]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (7fee5443b030): DESC ******
      Connection ID (thread ID): 1339223
      Status: NOT_KILLED

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  lpjirasync lpjirasync (Inactive)
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: