pi@basar3-85:~ $ mariabackup --user=[user-replaced] --password=[pw-replaced] --backup --target-dir=/home/pi/backuptest-export.sql
|
[00] 2021-04-17 12:26:12 Connecting to MySQL server host: localhost, user: [replaced, root access], password: set, port: not set, socket: /var/run/mysqld/mysqld.sock
|
[00] 2021-04-17 12:26:12 Using server version 10.3.27-MariaDB-0+deb10u1
|
mariabackup based on MariaDB server 10.3.27-MariaDB debian-linux-gnueabihf (armv8l)
|
[00] 2021-04-17 12:26:12 uses posix_fadvise().
|
[00] 2021-04-17 12:26:12 cd to /var/lib/mysql/
|
[00] 2021-04-17 12:26:12 open files limit requested 0, set to 1024
|
[00] 2021-04-17 12:26:12 mariabackup: using the following InnoDB configuration:
|
[00] 2021-04-17 12:26:12 innodb_data_home_dir =
|
[00] 2021-04-17 12:26:12 innodb_data_file_path = ibdata1:12M:autoextend
|
[00] 2021-04-17 12:26:12 innodb_log_group_home_dir = ./
|
[00] 2021-04-17 12:26:12 InnoDB: Using Linux native AIO
|
2021-04-17 12:26:12 0 [Note] InnoDB: Number of pools: 1
|
2021-04-17 12:26:12 0 [Warning] InnoDB: Unable to open "./ib_logfile0" to check native AIO read support.
|
2021-04-17 12:26:12 0 [Warning] InnoDB: Linux Native AIO disabled.
|
2021-04-17 12:26:12 0 [ERROR] InnoDB: Operating system error number 13 in a file operation.
|
2021-04-17 12:26:12 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory.
|
2021-04-17 12:26:12 0x76f5d210 InnoDB: Assertion failure in file /build/mariadb-10.3-S9bYSW/mariadb-10.3-10.3.27/storage/innobase/fil/fil0fil.cc line 671
|
InnoDB: Failing assertion: success
|
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.
|
210417 12:26:12 [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.3.27-MariaDB-0+deb10u1
|
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 = 4390 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
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ 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 0 unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes 6873 6873 processes
|
Max open files 1024 1048576 files
|
Max locked memory 67108864 67108864 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 6873 6873 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: core
|
|
Abgebrochen
|
pi@basar3-85:~ $
|