Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.2.36
-
CentOS Linux release 7.9.2009 (Core), CWP panel
Description
Hi,
The mysql server is getting down and recovering on our server. This is happening day by day, but not frequently. The log information regarding stack trace is provided here.
Please have a look.
2021-09-29 15:44:39 0x7f0d4a7fc700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.2.36/storage/in
|
nobase/btr/btr0sea.cc line 1409
|
InnoDB: Failing assertion: index->id == btr_page_get_index_id(page)
|
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.
|
210929 15:44:39 [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.2.36-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=17
|
max_threads=153
|
thread_count=22
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467243 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
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c9c55b584e]
|
/usr/sbin/mysqld(handle_fatal_signal+0x30d)[0x55c9c504d8ad]
|
sigaction.c:0(__restore_rt)[0x7f0d825fb630]
|
:0(__GI_raise)[0x7f0d808cb387]
|
:0(__GI_abort)[0x7f0d808cca78]
|
/usr/sbin/mysqld(+0x44918e)[0x55c9c4df318e]
|
/usr/sbin/mysqld(+0x9cb627)[0x55c9c5375627]
|
/usr/sbin/mysqld(+0x9bac95)[0x55c9c5364c95]
|
/usr/sbin/mysqld(+0x8f2d67)[0x55c9c529cd67]
|
/usr/sbin/mysqld(+0x8f49db)[0x55c9c529e9db]
|
/usr/sbin/mysqld(+0x8f5047)[0x55c9c529f047]
|
/usr/sbin/mysqld(+0x8d5461)[0x55c9c527f461]
|
/usr/sbin/mysqld(+0x8d5e44)[0x55c9c527fe44]
|
/usr/sbin/mysqld(+0xa2ec6c)[0x55c9c53d8c6c]
|
/usr/sbin/mysqld(+0xa36f45)[0x55c9c53e0f45]
|
/usr/sbin/mysqld(+0xa38bea)[0x55c9c53e2bea]
|
/usr/sbin/mysqld(+0xa3c168)[0x55c9c53e6168]
|
pthread_create.c:0(start_thread)[0x7f0d825f3ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f0d8099398d]
|
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 15075 15075 processes
|
Max open files 16384 16384 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 15075 15075 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
|
|
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Uses event mutexes
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Compressed tables use zlib 1.2.7
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Using Linux native AIO
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Number of pools: 1
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Using SSE2 crc32 instructions
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Completed initialization of buffer pool
|
2021-09-29 15:44:44 140050944157440 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setprio
|
rity().
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Highest supported file format is Barracuda.
|
2021-09-29 15:44:44 140051504097472 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2736731826
|