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

LP #1247305: InnoDB: Assertion failure in thread <nr> in file trx0trx.c line 180

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      **Reported in Launchpad by George Ormond Lorch III last update 25-11-2013 15:43:45

      Testing crash safe slave on PS 5.5.33-29.3

      Configure master-slave with slave having following options:
      innodb_file_format=barracuda
      innodb_file_per_table=1
      innodb_recovery_update_relay_log=1
      innodb_flush_log_at_trx_commit=0
      log-bin=a
      log-slave-updates=TRUE

      Start slave and sync to master position.
      Start mysql < employees.sql in a repeating loop
      kill -9 slave
      Restart slave:
      131101 17:02:14 [Note] Plugin 'FEDERATED' is disabled.
      InnoDB: Warning: innodb_overwrite_relay_log_info is enabled. Updates by other storage engines may not be synchronized.
      InnoDB: relay-log.info is detected.
      InnoDB: relay log: position 13296016, file name ./mysql-relay-bin.000016
      InnoDB: master log: position 99557176, file name a.000003
      131101 17:02:14 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
      131101 17:02:14 InnoDB: The InnoDB memory heap is disabled
      131101 17:02:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
      131101 17:02:14 InnoDB: Compressed tables use zlib 1.2.3
      131101 17:02:14 InnoDB: Using Linux native AIO
      131101 17:02:14 InnoDB: Initializing buffer pool, size = 128.0M
      131101 17:02:14 InnoDB: Completed initialization of buffer pool
      131101 17:02:14 InnoDB: highest supported file format is Barracuda.
      InnoDB: Log scan progressed past the checkpoint lsn 228299464
      131101 17:02:14 InnoDB: Database was not shut down normally!
      InnoDB: Starting crash recovery.
      InnoDB: Reading tablespace information from the .ibd files...
      InnoDB: Restoring possible half-written data pages from the doublewrite
      InnoDB: buffer...
      InnoDB: Doing recovery: scanned up to log sequence number 233542144
      InnoDB: Doing recovery: scanned up to log sequence number 233652541
      InnoDB: 1 transaction(s) which must be rolled back or cleaned up
      InnoDB: in total 0 row operations to undo
      InnoDB: Trx id counter is 1500
      131101 17:02:14 InnoDB: Starting an apply batch of log records to the database...
      InnoDB: Progress in percents: 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
      InnoDB: Apply batch completed
      InnoDB: In a MySQL replication slave the last master binlog file
      InnoDB: position 99557176, file name a.000003
      InnoDB: and relay log file
      InnoDB: position 13296016, file name ./mysql-relay-bin.000016
      InnoDB: Last MySQL binlog file position 0 15339990, file name ./a.000011
      InnoDB: Cleaning up trx with id 130E
      131101 17:02:15 InnoDB: Assertion failure in thread 139889164592928 in file trx0trx.c line 180
      InnoDB: Failing assertion: mutex_own(&(*kernel_mutex_temp))
      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.5/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      00:02:15 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.
      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.
      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=0
      max_threads=153
      thread_count=0
      connection_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 342996 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 = 0 thread_stack 0x40000
      mysqld(my_print_stacktrace+0x35)[0x7ee635]
      mysqld(handle_fatal_signal+0x314)[0x6b55e8]
      /lib64/libpthread.so.0[0x391b00f500]
      /lib64/libc.so.6(gsignal+0x35)[0x391a8328a5]
      /lib64/libc.so.6(abort+0x175)[0x391a834085]
      mysqld[0x8762ce]
      mysqld[0x876497]
      mysqld[0x86cbf5]
      mysqld[0x93bad2]
      mysqld[0x8579cf]
      mysqld[0x80498f]
      mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0xa4)[0x6b8c7e]
      mysqld[0x5acf80]
      mysqld(_Z11plugin_initPiPPci+0xac1)[0x5b07df]
      mysqld[0x51fc9b]
      mysqld(_Z11mysqld_mainiPPc+0x609)[0x520a2c]
      mysqld(main+0x9)[0x515d9d]
      /lib64/libc.so.6(__libc_start_main+0xfd)[0x391a81ecdd]
      mysqld[0x515cd9]
      You may download the Percona Server operations manual by visiting
      http://www.percona.com/software/percona-server/. You may find information
      in the manual which will help you identify the cause of the crash.
      Writing a core file

        Smart Checklist

          Attachments

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: