160201 10:19:27 innobackupex: Starting the backup operation

IMPORTANT: Please check that the backup run completes successfully.
           At the end of a successful backup run innobackupex
           prints "completed OK!".

Can't locate Digest/MD5.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at - line 693.
BEGIN failed--compilation aborted at - line 693.
160201 10:19:28 Connecting to MySQL server host: localhost, user: backup_user, password: set, port: 3306, socket: /AZVOL/mysql/tmp/mysql.sock
Using server version 5.6.23
innobackupex version 2.3.3 based on MySQL server 5.6.24 Linux (x86_64) (revision id: 525ca7d)
incremental backup from 6777372280 is enabled.
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /AZVOL/mysql/data
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup:   innodb_data_home_dir = /AZVOL/mysql/data
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 2
xtrabackup:   innodb_log_file_size = 1415577600
160201 10:19:28 >> log scanned up to (6777372510)
xtrabackup: Generating a list of tablespaces
160201 10:19:29 >> log scanned up to (6777372510)
160201 10:19:30 >> log scanned up to (6777372510)
160201 10:19:31 >> log scanned up to (6777372510)
160201 10:19:32 >> log scanned up to (6777372510)
160201 10:19:33 >> log scanned up to (6777372510)
160201 10:19:34 >> log scanned up to (6777372510)
160201 10:19:35 >> log scanned up to (6777372510)
160201 10:19:36 >> log scanned up to (6777372510)
160201 10:19:37 >> log scanned up to (6777372510)
160201 10:19:38 >> log scanned up to (6777372510)
160201 10:19:39 >> log scanned up to (6777372510)
160201 10:19:40 >> log scanned up to (6777372510)
160201 10:19:41 >> log scanned up to (6777372510)
160201 10:19:42 >> log scanned up to (6777372510)
160201 10:19:43 >> log scanned up to (6777372510)
xtrabackup: using the full scan for incremental backup
2016-02-01 10:19:44 7f996b97c700  InnoDB: Assertion failure in thread 140296911832832 in file ut0mem.cc line 105
InnoDB: Failing assertion: ret || !assert_on_error
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.
10:19:44 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...
160201 10:19:44 >> log scanned up to (6777372510)
stack_bottom = 0 thread_stack 0x10000
innobackupex(my_print_stacktrace+0x2e) [0x96c7be]
innobackupex(handle_fatal_signal+0x262) [0x84cbc2]
/lib64/libpthread.so.0(+0xf130) [0x7f99780d3130]
/lib64/libc.so.6(gsignal+0x39) [0x7f99768465c9]
/lib64/libc.so.6(abort+0x148) [0x7f9976847cd8]
innobackupex(ut_malloc_low(unsigned long, unsigned long)+0x13c) [0x72652c]
innobackupex() [0x5a3804]
innobackupex() [0x598ee3]
innobackupex() [0x599198]
/lib64/libpthread.so.0(+0x7df3) [0x7f99780cbdf3]
/lib64/libc.so.6(clone+0x6d) [0x7f99769071ad]

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