Uploaded image for project: 'Percona XtraBackup'
  1. Percona XtraBackup
  2. PXB-473

LP #1568009: Assertion failure in xtrabackup.cc: lsn_chosen == 1

    XMLWordPrintable

    Details

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

      Description

      **Reported in Launchpad by Ceri WIlliams last update 22-11-2016 16:24:23

      Repeated, but intermittent assertion failures have been seen on a box running Debian 8 with PXB 2.3.3-1.jessie. This was also noticed in 2.2.3-2.1:

      /usr/bin/innobackupex version 2.3.2 - line 2494
      /usr/bin/innobackupex version 2.3.3 - line 2503

      The stracktrace shows as:
      ---------------------------------------

      2016-04-08 04:21:45 7fb1bbff9740 InnoDB: Assertion failure in thread 140401340028736 in file xtrabackup.cc line 2503
      InnoDB: Failing assertion: lsn_chosen == 1
      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.
      02:21:45 UTC - xtrabackup got signal 6 ;
      This could be because you hit a bug or data is corrupted.
      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.

      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 0x10000
      /usr/bin/innobackupex(my_print_stacktrace+0x2e) [0x88857e]
      /usr/bin/innobackupex(handle_fatal_signal+0x261) [0x7d99c1]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7fb1bbbde8d0]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fb1ba2eb067]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fb1ba2ec448]
      /usr/bin/innobackupex() [0x58976d]
      /usr/bin/innobackupex(xtrabackup_backup_func()+0x127f) [0x59125f]
      /usr/bin/innobackupex(main+0xa4b) [0x577fcb]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fb1ba2d7b45]
      /usr/bin/innobackupex() [0x588afa]

      Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
      ---------------------------------------

      The error has been observed in both full and incremental backups, both of which were streaming via SSH:

      ssh -t -o PasswordAuthentication=no -o StrictHostKeyChecking=no server.a "
      sudo /usr/bin/innobackupex xtrabackup_tmpdir \
      --slave-info --kill-long-queries-timeout=10 \
      --kill-long-query-type=select --incremental-lsn=xxxxx \
      --incremental --compress --stream=xbstream \

      ssh -o PasswordAuthentication=no -o StrictHostKeyChecking=no server.b 'xbstream -x -C xtrabackup_tmpdir'"

        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: