151126 22:25:50 [00] Writing xtrabackup_info
151126 22:25:50 [00] ...done
22:25:50 UTC - 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(my_print_stacktrace+0x2e) [0x8c502e]
innobackupex(handle_fatal_signal+0x273) [0x736dc3]
/lib64/libpthread.so.0(+0xf790) [0x7f3e62c12790]
/lib64/libc.so.6(+0x81211) [0x7f3e6127d211]
innobackupex(write_xtrabackup_info(st_mysql*)+0x4b2) [0x59e632]
innobackupex(backup_finish()+0x16e) [0x5a10ee]
innobackupex(xtrabackup_backup_func()+0xeba) [0x58e1aa]
innobackupex(main+0xaea) [0x591efa]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f3e6121ad5d]
innobackupex() [0x585e79]
I have confirmed this using xtrabackup 2.3.2 with PS 5.6.27:
mysql> show variables like '%version%'; ------- ------- -----+- ------- ------- ------- ------- ------- ------- ------- ----+ ------- ------- -----+- ------- ------- ------- ------- ------- ------- ------- ----+ conversions | | compile_ machine | x86_64 | ------- ------- -----+- ------- ------- ------- ------- ------- ------- ------- ----+
+------
| Variable_name | Value |
+------
| innodb_version | 5.6.27-75.0 |
| protocol_version | 10 |
| slave_type_
| version | 5.6.27-75.0 |
| version_comment | Percona Server (GPL), Release 75.0, Revision 8bb53b6 |
| version_
| version_compile_os | Linux |
+------
7 rows in set (0.00 sec)
[root@VM-centos67 backups]# xtrabackup --version
xtrabackup version 2.3.2 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 306a2e0)
[root@VM-centos67 backups]# rpm -qa | grep -i percona Server- client- 56-5.6. 27-rel75. 0.el6.x86_ 64 Server- shared- 51-5.1. 73-rel14. 12.625. rhel6.x86_ 64 xtrabackup- debuginfo- 2.3.2-1. el6.x86_ 64 release- 0.1-3.noarch Server- shared- 56-5.6. 27-rel75. 0.el6.x86_ 64 xtrabackup- 2.3.2-1. el6.x86_ 64 Server- server- 56-5.6. 27-rel75. 0.el6.x86_ 64
Percona-
Percona-
percona-
percona-
Percona-
percona-
Percona-
See attached outputs for two runs:
1- innobackupex --parallel=10 --no-timestamp /backups/ full_backup full_backup
2- innobackupex --parallel=10 --history="test" --no-timestamp /backups/
I got the same stack trace from #2:
151126 22:25:50 [00] Writing xtrabackup_info
151126 22:25:50 [00] ...done
22:25:50 UTC - 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 my_print_ stacktrace+ 0x2e) [0x8c502e] handle_ fatal_signal+ 0x273) [0x736dc3] libpthread. so.0(+0xf790) [0x7f3e62c12790] libc.so. 6(+0x81211) [0x7f3e6127d211] write_xtrabacku p_info( st_mysql* )+0x4b2) [0x59e632] backup_ finish( )+0x16e) [0x5a10ee] xtrabackup_ backup_ func()+ 0xeba) [0x58e1aa] main+0xaea) [0x591efa] libc.so. 6(__libc_ start_main+ 0xfd) [0x7f3e6121ad5d]
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]
Please report a bug at https:/ /bugs.launchpad .net/percona- xtrabackup
Setting to confirmed.
Agustín.