[MDEV-23059] Mariabackup crashed during backup, mariadb 10.4.12 Created: 2020-06-30  Updated: 2020-08-04  Resolved: 2020-08-04

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Xesh Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-21323 mariabackup crash Closed
Relates
relates to MDEV-18419 mariabackup fails to backup any datab... Closed

 Description   

Mariabackup crashed when starting a backup, version MariaDB 10.4.12

[00] 2020-06-30 07:00:02 Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set
[00] 2020-06-30 07:00:02 Using server version 10.4.12-MariaDB-log
/bin/mariabackup based on MariaDB server 10.4.12-MariaDB Linux (x86_64)
[00] 2020-06-30 07:00:02 uses posix_fadvise().
[00] 2020-06-30 07:00:02 cd to /var/lib/mysql/
[00] 2020-06-30 07:00:02 open files limit requested 16384, set to 16384
[00] 2020-06-30 07:00:02 InnoDB: The universal page size of the database is set to 65536.
[00] 2020-06-30 07:00:02 mariabackup: using the following InnoDB configuration:
[00] 2020-06-30 07:00:02 innodb_data_home_dir = /var/lib/mysql
[00] 2020-06-30 07:00:02 innodb_data_file_path = ibdata1:50M;ibdata2:50M:autoextend
[00] 2020-06-30 07:00:02 innodb_log_group_home_dir = ./
[00] 2020-06-30 07:00:02 InnoDB: Using Linux native AIO
2020-06-30 7:00:02 0 [Note] InnoDB: Number of pools: 1
2020-06-30 7:00:02 0 [ERROR] InnoDB: mmap(25769803776 bytes) failed; errno 12
2020-06-30 07:00:02 0x7f7f4cefb900 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.12/storage/innobase/include/ut0new.h line 248
InnoDB: Failing assertion: ptr != NULL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
200630 7:00:02 [ERROR] mysqld got signal 6 ;
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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.4.12-MariaDB
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=1
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5932 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 = 0x0 thread_stack 0x49000
/bin/mariabackup(my_print_stacktrace+0x2e)[0x55a62181c3ae]
/bin/mariabackup(handle_fatal_signal+0x54d)[0x55a62137bd8d]
sigaction.c:0(__restore_rt)[0x7f7f4cadcdd0]
:0(__GI_raise)[0x7f7f4aba299f]
:0(__GI_abort)[0x7f7f4ab8ccf5]
/bin/mariabackup(+0x5c3edf)[0x55a620ff1edf]
/bin/mariabackup(+0x5a4599)[0x55a620fd2599]
/bin/mariabackup(+0xb6c715)[0x55a62159a715]
/bin/mariabackup(+0x5f19d3)[0x55a62101f9d3]
/bin/mariabackup(main+0x185)[0x55a620fffa35]
/lib64/libc.so.6(__libc_start_main+0xf3)[0x7f7f4ab8e873]
/bin/mariabackup(_start+0x2e)[0x55a6210184ae]
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.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 381016 381016 processes
Max open files 16384 16384 files
Max locked memory 16777216 16777216 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 381016 381016 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e



 Comments   
Comment by Alice Sherepa [ 2020-07-01 ]

Could you please try to run with a smaller buffer pool (as described in MDEV-18419)?

Comment by Xesh [ 2020-07-01 ]

Lowering the buffer pool from the main /etc/my.cnf.d/mysql.cnf will reduce buffer pool of the MariaDB database after the restart.

Solution for this is to call separate .cnf file:

/bin/mariabackup --defaults-file=/etc/mariabackup.cnf --backup --target-dir=/backupdir --user=root --password=xxx

mariabackup.cnf lines:
[mysqld]
socket=/var/lib/mysql/mysql.sock
innodb_buffer_pool_size=4G
open_files_limit=16384

Thanks

Generated at Thu Feb 08 09:19:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.