Maria 백업 중에 mysqld 오류가 발생하는 이유

Maria 백업 중에 mysqld 오류가 발생하는 이유

오류 메시지는 다음과 같습니다.

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_file_limit을 90160으로 수정합니다.

ulimit - n 90160

마리아 백업은 문제없이 잘 작동할 것입니다.

도와주셔서 감사합니다.

언급URL : https://stackoverflow.com/questions/59710088/why-its-mysqld-error-occurs-during-mariabackup