【发布时间】：2020-04-29 18:44:17
【问题描述】：
错误信息如下所示。
Using server version 10.4.8-MariaDB-log
mariabackup based on MariaDB server 10.4.11-MariaDB Linux (x86_64)
[00] 2020-01-11 11:05:41 uses posix_fadvise().
[00] 2020-01-11 11:05:41 cd to /home/data/mysql/
[00] 2020-01-11 11:05:41 open files limit requested 0, set to 1024
[00] 2020-01-11 11:05:41 mariabackup: using the following InnoDB
configuration:[00] 2020-01-11 11:05:41 innodb_data_home_dir =[00] 2020-01-11 11:05:41 innodb_data_file_path = ibdata1:12M:autoextend
[00] 2020-01-11 11:05:41 innodb_log_group_home_dir = ./
[00] 2020-01-11 11:05:41 InnoDB: Using Linux native AIO
2020-01-11 11:05:42 0 [Note] InnoDB: Number of pools: 1
[00] 2020-01-11 11:05:42 mariabackup: Generating a list of tablespaces
2020-01-11 11:05:42 0 [Warning] InnoDB: Allocated tablespace ID 28 for UYeG_Cloud/HisItemCurrRMinute, old maximum was 0
2020-01-11 11:05:44 0 [ERROR] InnoDB: Operating system error number 24 in a file operation.
2020-01-11 11:05:44 0 [ERROR] InnoDB: Error number 24 means 'Too many open files'
2020-01-11 11:05:44 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2020-01-11 11:05:44 0 [ERROR] InnoDB: File ./UYeG_Cloud/HisAvg#P#p731.ibd: 'open' returned OS error 224.
2020-01-11 11:05:44 0x7fd75730d8c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.11/storage/innobase/fil/fil0fil.cc line 576
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.
200111 11:05:44 [ERROR] mysqld got signal 6 ; '
这可能是因为您遇到了错误。这个二进制文件也有可能
或者它所链接的库之一已损坏，构建不当，
或配置错误。此错误也可能是由硬件故障引起的。 `
`要报告此错误，请参阅https://mariadb.com/kb/en/reporting-bugs
我们会尽力收集一些希望对您有所帮助的信息 诊断问题，但由于我们已经崩溃了， 肯定有问题，这可能会失败。 `
Server version: 10.4.11-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 = 5919 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
mariabackup(my_print_stacktrace+0x2e)[0x55c966dcf37e]
mariabackup(handle_fatal_signal+0x30f)[0x55c9668cbb5f]
/lib64/libpthread.so.0(+0xf5f0)[0x7fd756ef95f0]
/lib64/libc.so.6(gsignal+0x37)[0x7fd7551ca337]
/lib64/libc.so.6(abort+0x148)[0x7fd7551cba28]
mariabackup(+0x5b0574)[0x55c966537574]
mariabackup(+0xad4c41)[0x55c966a5bc41]
mariabackup(+0xad9eb7)[0x55c966a60eb7]
mariabackup(+0x5e40c5)[0x55c96656b0c5]
mariabackup(+0x5e33ad)[0x55c96656a3ad]
mariabackup(+0x5e3849)[0x55c96656a849]
mariabackup(+0x5e63ec)[0x55c96656d3ec]
mariabackup(main+0x185)[0x55c96653a7d5]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd7551b6505]
mariabackup(+0x5dc554)[0x55c966563554]
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 /home/data/mysql
중지됨
------------------------------------------------------------------------
What are the causes and measures?
【问题讨论】：
-
您是否尝试在配置文件中增加 open_files_limit ？
-
当前。 open_file_limit 是 4555。我应该如何修改它的值？
-
能否分享
ulimit -a和find /yourdatadir -name "*.ibd" | wc -l的输出？
标签： memory mariadb database-backups mariasql mariadb-10.3