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

Xtrabackup 8.0.5 and MySQL 8.0.16: Unknown error 3613

hackituriahackituria EntrantCurrent User Role Contributor
I'm using Xtrabackup 8.0.5 and MySQL 8.0.16 and when I execute the following codeline:
sudo xtrabackup --prepare --target-dir=/opt/iepa/backup/osoa/

I receive this result:
[email protected]:/opt/iepa/backup# xtrabackup --prepare --target-dir=/opt/iepa/backup/osoa/
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=50331648 --innodb_page_size=16384 --innodb_undo_directory=./ --innodb_undo_tablespaces=2 --server-id=0 --innodb_log_checksums=ON --innodb_redo_log_encrypt=0 --innodb_undo_log_encrypt=0
xtrabackup: recognized client arguments: --prepare=1 --target-dir=/opt/iepa/backup/osoa/
xtrabackup version 8.0.5 based on MySQL server 8.0.14 Linux (x86_64) (revision id: 40ec8a3)
xtrabackup: cd to /opt/iepa/backup/osoa/
xtrabackup: This target seems to be not prepared yet.
Number of pools: 1
Operating system error number 2 in a file operation.
The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
xtrabackup: 'ib_logfile0' seems to be 'xtrabackup_logfile'. will retry.
xtrabackup: xtrabackup_logfile detected: size=9437184, start_lsn=(29315209)
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 = 9437184
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 = 9437184
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
PUNCH HOLE support available
Mutexes and rw_locks use GCC atomic builtins
Uses event mutexes
GCC builtin __atomic_thread_fence() is used for memory barrier
Compressed tables use zlib 1.2.11
Number of pools: 1
Using CPU crc32 instructions
Directories to scan '.;.;.'
Scanning './'
Completed space ID check of 4 files.
Initializing buffer pool, total size = 128.000000M, instances = 1, chunk size =128.000000M
Completed initialization of buffer pool
page_cleaner coordinator priority: -20
page_cleaner worker priority: -20
page_cleaner worker priority: -20
page_cleaner worker priority: -20
The log sequence number 2777969 in the system tablespace does not match the log sequence number 29315209 in the ib_logfiles!
Database was not shutdown normally!
Starting crash recovery.
Starting to parse redo log at lsn = 29315209, whereas checkpoint_lsn = 29315209
Doing recovery: scanned up to log sequence number 29315209
Log background threads are being started...
Applying a batch of 0 redo log records ...
Apply batch completed!
Using undo tablespace './undo_001'.
Using undo tablespace './undo_002'.
Opened 2 existing undo tablespaces.
Removed temporary tablespace data file: "ibtmp1"
Creating shared tablespace for temporary tables
Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
File './ibtmp1' size is now 12 MB.
Scanning temp tablespace dir:'./#innodb_temp/'
Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
8.0.14 started; log sequence number 29315209
Allocated tablespace ID 21 for sys/sys_config, old maximum was 0
xtrabackup: Unknown error 3613
xtrabackup: Unknown error 3613
10:10:15 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 = 1676 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)+0x3d) [0x558b2043622d]
xtrabackup(handle_fatal_signal+0x423) [0x558b1f43b643]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7fb303963890]
xtrabackup(dd::get_dd_client(THD*)+0x1) [0x558b1f92cc31]
xtrabackup(dd_table_open_on_name(THD*, MDL_ticket**, char const*, bool, unsigned long)+0x3dd) [0x558b1f5e770d]
xtrabackup(+0xc1034a) [0x558b1efdc34a]
xtrabackup(+0xc15883) [0x558b1efe1883]
xtrabackup(main+0x742) [0x558b1efa2ae2]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fb301a1ab97]
xtrabackup(_start+0x2a) [0x558b1efcf83a]

Please report a bug at https://jira.percona.com/projects/PXB

How can I solve this problem?

Comments

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.