|
The output from mariabackup is as follow when the crash happens:
170817 15:18:42 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: not set
Using server version 10.1.26-MariaDB
Loading encryption plugin
Encryption plugin parameter : '--file_key_management_encryption_algorithm=aes_cbc'
Encryption plugin parameter : '--file_key_management_filekey='
Encryption plugin parameter : '--file_key_management_filename=/var/lib/mysql/keys'
mariabackup based on MariaDB server 10.1.26-MariaDB Linux (x86_64)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql/
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
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 = 2
xtrabackup: innodb_log_file_size = 50331648
170817 15:18:42 >> log scanned up to (51414205)
xtrabackup: Generating a list of tablespaces
InnoDB: Attempted to open a previously opened tablespace. Previous tablespace test/t1_1 uses space ID: 8 at filepath: ./test/t1_1.ibd. Cannot open tablespace test/t1 which uses space ID: 8 at filepath: ./test/t1.ibd
2017-08-17 15:18:42 7f86606da820 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./test/t1.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
170817 15:18:42 [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.1.26-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 = 5309 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 0x48400
addr2line: 'mariabackup': No such file
mariabackup(my_print_stacktrace+0x2b)[0x7f866119fa5b]
mariabackup(handle_fatal_signal+0x4d5)[0x7f8660d02895]
/lib64/libpthread.so.0(+0x31d180f710)[0x7f86602c9710]
/lib64/libc.so.6(gsignal+0x35)[0x7f865e6f6925]
/lib64/libc.so.6(abort+0x175)[0x7f865e6f8105]
mariabackup(+0x881a79)[0x7f8660f7aa79]
mariabackup(+0x3d6951)[0x7f8660acf951]
mariabackup(_Z22xtrabackup_backup_funcv+0xc9a)[0x7f8660ad52ea]
mariabackup(main+0xf77)[0x7f8660ab4f77]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f865e6e2d1d]
mariabackup(+0x3d3b29)[0x7f8660accb29]
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.
|