Not the answer you need?
Register and ask your own question!

xtrabackup 8.0.5 mysql 8.0.15 prepare failes with xtrabackup: Unknown error 3611

jonssonjnjonssonjn EntrantInactive User Role Contributor
[[email protected] MYSQL8]$ xtrabackup --prepare --target-dir=/opt/mysql/mysqldata/mysqlbackup/MYSQL8/2019-03-05-15-59-full
xtrabackup: recognized server arguments: --innodb_checksum_algorithm=innodb --innodb_log_checksums=1 --innodb_data_file_path=ibdata1:12M:autoextend --innodb_log_files_in_group=2 --innodb_log_file_size=104857600 --innodb_page_size=16384 --innodb_undo_directory=./ --innodb_undo_tablespaces=2 --server-id=6 --innodb_log_checksums=ON --innodb_redo_log_encrypt=0 --innodb_undo_log_encrypt=0
xtrabackup: recognized client arguments: --prepare=1 --target-dir=/opt/mysql/mysqldata/mysqlbackup/MYSQL8/2019-03-05-15-59-full
xtrabackup version 8.0.1 based on MySQL server 8.0.12 Linux (x86_64) (revision id: )
xtrabackup: cd to /opt/mysql/mysqldata/mysqlbackup/MYSQL8/2019-03-05-15-59-full/
xtrabackup: This target seems to be not prepared yet.
InnoDB: Number of pools: 1
xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(99712145519)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 8388608
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 8388608
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: PUNCH HOLE support available
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Number of pools: 1
InnoDB: Using CPU crc32 instructions
InnoDB: Directories to scan '.;.;.'
InnoDB: Scanning './'
InnoDB: Completed space ID check of 70 files.
InnoDB: Initializing buffer pool, total size = 128.000000M, instances = 1, chunk size =128.000000M
InnoDB: Completed initialization of buffer pool
InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
InnoDB: The log sequence number 99712059123 in the system tablespace does not match the log sequence number 99712145519 in the ib_logfiles!
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Starting to parse redo log at lsn = 99712145466, whereas checkpoint_lsn = 99712145519
InnoDB: Doing recovery: scanned up to log sequence number 99712145519
InnoDB: Log background threads are being started...
InnoDB: Applying a batch of 0 redo log records ...
InnoDB: Apply batch completed!
InnoDB: xtrabackup: Last MySQL binlog file position 4714, file name MYSQL8.000014
InnoDB: Opened 2 existing undo tablespaces.
InnoDB: Creating shared tablespace for temporary tables
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
InnoDB: File './ibtmp1' size is now 12 MB.
InnoDB: Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
InnoDB: 8.0.12 started; log sequence number 99712145519
Populating InnoDB table cache.
InnoDB: Allocated tablespace ID 174 for mcdb/customers, old maximum was 0
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
xtrabackup: Unknown error 3611
15:12:57 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. 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.

key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=0
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1662 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 0x46000
xtrabackup(my_print_stacktrace(unsigned char*, unsigned long)+0x2e) [0x1f1c7ce]
xtrabackup(handle_fatal_signal+0x425) [0xfd1e05]
/lib64/libpthread.so.0(+0xf5d0) [0x7f0a5a2265d0]
xtrabackup(dd::get_dd_client(THD*)+0x1) [0x141fbb1]
xtrabackup(dd_table_open_on_name(THD*, MDL_ticket**, char const*, bool, unsigned long)+0x497) [0x1147187]
xtrabackup() [0xb86a53]
xtrabackup(main+0x1920) [0xb494a0]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0a57f07495]
xtrabackup() [0xb79554]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Comments

  • jonssonjnjonssonjn Entrant Inactive User Role Contributor
    Please igone it took 8.0.1 xtrabackup from other installation in path first.
    8.0.5 is working great
  • hackituriahackituria Entrant Current User Role Contributor
    I have the same problem and I am using 8.0.5 version with MYSQL 8.0.16. How can I solve it?
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.