backup fails with history on server enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | ||
2.3 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
After a system update innobackupex start crashing on full backups
xtrabackup got signal 11 ;
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
innobackupex(
innobackupex(
/lib64/
/lib64/
innobackupex(
innobackupex(
innobackupex(
innobackupex(
/lib64/
innobackupex() [0x585e79]
This is how backups are taken
innobackupex --history=
my.cnf
https:/
fuull innobackupex log
https:/
general system information (uname,memory,cpu, etc.):
https:/
yum update history:
https:/
mysql --version
mysql Ver 14.14 Distrib 5.6.26-74.0, for Linux (x86_64) using 6.0
innobackupex --version
innobackupex version 2.3.2 Linux (x86_64) (revision id: 306a2e0)
rpm -qa Percona*
Percona-
Percona-
Percona-
Percona-
rpm -qa percona*
percona-
percona-
percona-
percona-
tags: | added: i62431 |
summary: |
- xtrabackup got signal 11 on full backup + backup fails with history on server enabled |
Downgrading to xtrabackup 2.2.12 solved the issue
yum downgrade percona- xtrabackup- 2.2.12- 1.el6
xtrabackup -v
xtrabackup version 2.2.12 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 8726828)