Preparing backup failed - Assertion failure in thread 139778822076192 in file dict0dict.cc line 1940

[Mihai Onofrei]

I try to prepare the backup with:

innobackupex --defaults-file=/varsoft/mysql/PPFS04R0/backup/Full/backup/backup-my.cnf --apply-log --use-memory=256M /varsoft/mysql/PPFS04R0/backup/Full/backup

and is failed with:

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved.

This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:
http://www.percona.com/xb/p

170804 11:03:49 innobackupex: Starting the apply-log operation

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

170804 11:03:50 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/varsoft/mysql/PPFS04R0/backup/Full/backup/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/varsoft/mysql/PPFS04R0/backup/Full/backup --use-memory=256M

xtrabackup version 2.2.9 based on MySQL server 5.6.22 Linux (x86_64) (revision id: )
xtrabackup: cd to /varsoft/mysql/PPFS04R0/backup/Full/backup
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(9178053773713)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = shared_PPFS04P0.idb:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = ./
xtrabackup: innodb_data_file_path = shared_PPFS04P0.idb:10M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 268435456 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.3
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 256.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: The log sequence numbers 6305471647362 and 6305471647362 in ibdata files do not match the log sequence number 9178053773713 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages
InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 316361151, file name logbin_PPFS04P0.002017
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004452_000000000000335a_DOC_ID'.
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004452_ADDED'.
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004452_STOPWORDS'.
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004d35_00000000000060a0_DOC_ID'.
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004d35_ADDED'.
InnoDB: Dropped obsolete aux table 'FACTURATION_FTTH/FTS_0000000000004d35_STOPWORDS'.
InnoDB: 128 rollback segment(s) are active.
InnoDB: Waiting for purge to start
InnoDB: 5.6.22 started; log sequence number 9178053773713

[notice (again)]
  If you use binary log and don't use any hack of group commit,
  the binary log position seems to be:
InnoDB: Last MySQL binlog file position 0 316361151, file name logbin_PPFS04P0.002017

xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
2017-08-04 11:04:03 7f20cb097720 InnoDB: Assertion failure in thread 139778822076192 in file dict0dict.cc line 1940
InnoDB: Failing assertion: table->n_ref_count == 0
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.
09:04:03 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: 0x2b41eb0
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 = 2b42ed0 thread_stack 0x10000
xtrabackup(my_print_stacktrace+0x2e) [0x916d0e]
xtrabackup(handle_fatal_signal+0x235) [0x81d4a5]
/lib64/libpthread.so.0() [0x350380f710]
/lib64/libc.so.6(gsignal+0x35) [0x3e74432925]
/lib64/libc.so.6(abort+0x175) [0x3e74434105]
xtrabackup() [0x663f19]
xtrabackup(dict_close()+0x5d) [0x66827d]
xtrabackup(innobase_shutdown_for_mysql()+0x1fb) [0x6e1c7b]
xtrabackup() [0x57587f]
xtrabackup(main+0x87b) [0x5774bb]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x3e7441ed1d]
xtrabackup(__gxx_personality_v0+0x339) [0x56be49]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
innobackupex: got a fatal error with the following stacktrace: at /product/mysql/admin/tools/percona-xtrabackup-2.2.9-Linux-x86_64/bin/innobackupex line 2642
        main::apply_log() called at /product/mysql/admin/tools/percona-xtrabackup-2.2.9-Linux-x86_64/bin/innobackupex line 1570
innobackupex: Error:
innobackupex: ibbackup failed at /product/mysql/admin/tools/percona-xtrabackup-2.2.9-Linux-x86_64/bin/innobackupex line 2642.

Could you help me, please ?

Regards

[Sergei Glushchenko (sergei.glushchenko)]

I see that version you are using is 2.2.9. Can you please try recent version?

https://www.percona.com/doc/percona-xtrabackup/2.3/installation/apt_repo.html

or

https://www.percona.com/doc/percona-xtrabackup/LATEST/installation/apt_repo.html

[Mihai Onofrei (mo.)]

Thank you Sergei,

I will try a recent version!

Best regards,
Mihai

[Launchpad Janitor (janitor)]

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1464