InnoDB: Assertion failure in thread
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
New
|
Undecided
|
Muhammad Irfan |
Bug Description
171204 01:00:02 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!".
171204 01:00:03 version_check Connecting to MySQL server with DSN 'dbi:mysql:
port=3306;
171204 01:00:03 version_check Connected to MySQL server
171204 01:00:03 version_check Executing a version check against the server...
171204 01:00:03 version_check Done
Using server version 5.6.17-log
innobackupex version 2.4.4 based on MySQL server 5.7.13 Linux (x86_64) (revision id: df58cf2)
171204 01:41:22 >> log scanned up to (8141434107856)
171204 01:41:23 >> log scanned up to (8141434275278)
171204 01:41:24 >> log scanned up to (8141434364129)
171204 01:41:25 >> log scanned up to (8141434478794)
171204 01:41:26 >> log scanned up to (8141434503832)
171204 01:41:27 >> log scanned up to (8141434533847)
2017-12-04 01:41:28 0x7f6db9d9f700 InnoDB: Assertion failure in thread 140109246232320 in file mtr0log.cc line 604
InnoDB: Failing assertion: DATA_TRX_ID_LEN == dict_index_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
17:41:28 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might 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/
/lib64/
innobackupex(
innobackupex[
innobackupex[
innobackupex(
innobackupex[
innobackupex[
innobackupex[
/lib64/
/lib64/
Changed in percona-xtrabackup: | |
assignee: | nobody → Muhammad Irfan (muhammad-irfan) |
Changed in percona-xtrabackup: | |
status: | Incomplete → New |
Can you post us exact backup command you used along with configuration options (my.cnf) in place to check further. Thanks.