xtrabackup got signal 11

Description

16:34:27 UTC - xtrabackup got signal 11 ;
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
/usr/bin/innobackupex(my_print_stacktrace+0x2c)[0xd730ec]
/usr/bin/innobackupex(handle_fatal_signal+0x286)[0xa37116]
/lib64/libpthread.so.0(+0xf630)[0x7f3c22111630]
/usr/bin/innobackupex(_Z8log_initv+0x208)[0xbe9518]
/usr/bin/innobackupex(_Z22xtrabackup_backup_funcv+0x3a2)[0x72a062]
/usr/bin/innobackupex(main+0xa94)[0x704c44]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f3c1ff80555]
/usr/bin/innobackupex[0x71ee04]

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

Environment

None

Activity

Show:

Aaditya Dubey January 1, 2025 at 1:38 PM
Edited

Hi

Thank you for the report.
Starting November 2023 Percona XtraBackup 2.4 has reached EOL status. If you have 5.7 databases, we encourage you to upgrade to 8.0 and then install Percona XtraBackup 8.0. Read More

If you still encounter this issue with 8.0 then please create a separate ticket with complete reproducible test case.

Won't Do

Details

Assignee

Reporter

Needs QA

Yes

Affects versions

Priority

Smart Checklist

Created December 2, 2024 at 1:37 AM
Updated January 1, 2025 at 1:40 PM
Resolved January 1, 2025 at 1:40 PM

Flag notifications