**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: 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
stack_bottom = 0 thread_stack 0x10000
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'"|