MariaDB 10.4.34 Crashing Frequently on CentOS 7: Core Dump Analysis and Upgrade Assistance Needed
by mzansipronk from LinuxQuestions.org on (#6PCWJ)
Hello everyone,
I'm facing a critical issue with MariaDB 10.4.34 running on CentOS 7. The database server crashes frequently, approximately every 20 minutes. I'm reaching out for help to understand the core dump analysis and guidance on upgrading to the latest stable version to resolve these crashes.
System Details:
MariaDB Version: 10.4.34
Operating System: CentOS 7 (x86_64)
Memory: 6 GB RAM
Disk Space: 400 GB SSD
Issue Description:
MariaDB server crashes frequently with the following signal:
vbnet
Copy code
Core was generated by `/usr/sbin/mysqld'.
Program terminated with signal 6, Aborted.
#0 0x00007fef2d2c0aa1 in pthread_kill ()
from /lib64/libpthread.so.0
I attempted to analyze the core dump using gdb and got the following backtrace:
Code:
(gdb) bt
#0 0x00007fef2d2c0aa1 in pthread_kill ()
from /lib64/libpthread.so.0
#1 0x00005600d0a2adae in handle_fatal_signal ()
#2 <signal handler called>
#3 0x00007fef2c70e387 in raise ()
from /lib64/libc.so.6
#4 0x00007fef2c70fa78 in abort ()
from /lib64/libc.so.6
#5 0x00005600d0723ae0 in ut_dbg_assertion_failed(char const*, char const*, unsigned int) ()
#6 0x00005600d07236d8 in flst_read_addr(unsigned char const*, mtr_t*) [clone .isra.9] [clone .part.10]
()
#7 0x00005600d0e1d40e in trx_purge_rseg_get_next_history_log(unsigned long*) ()
#8 0x00005600d0e1e257 in trx_purge_get_next_rec(unsigned long*, mem_block_info_t*) ()
#9 0x00005600d0e1eaa3 in trx_purge(unsigned long, bool) ()
#10 0x00005600d0e03f23 in srv_purge_coordinator_thread ()
#11 0x00007fef2d2bbea5 in start_thread ()
from /lib64/libpthread.so.0
#12 0x00007fef2c7d6b0d in clone ()
from /lib64/libc.so.6
Steps Taken
Analyzed Core Dump:
Used gdb to generate the backtrace.
Identified the signal causing the crash (signal 6, Aborted).
Checked Logs:
No relevant error logs found in /var/log/mysql/error.log or /var/log/mariadb/mariadb.log.
Reviewed System Resources:
Memory seems adequate with 4.2 GB available out of 6 GB.
Disk space utilization is at 16% of 400 GB.
Tried Basic Fixes:
Ensured all packages are up to date.
Restarted MariaDB service multiple times.
Attempted to Apply Debugging Info:
Encountered issues with debuginfo-install command while in gdb:
Core Dump Analysis:
Could someone help interpret the backtrace and suggest specific causes or fixes for the frequent crashes?
Upgrading MariaDB:
Detailed guidance on how to upgrade MariaDB to the latest stable version on CentOS 7.
Any precautions or steps to ensure a smooth upgrade process without data loss.
-Any additional logs or diagnostics that I should collect?
-Recommendations for configuring MariaDB to avoid such crashes in the future.
Your assistance is greatly appreciated as this issue is impacting our production environment. Thank you in advance for your time and help
I'm facing a critical issue with MariaDB 10.4.34 running on CentOS 7. The database server crashes frequently, approximately every 20 minutes. I'm reaching out for help to understand the core dump analysis and guidance on upgrading to the latest stable version to resolve these crashes.
System Details:
MariaDB Version: 10.4.34
Operating System: CentOS 7 (x86_64)
Memory: 6 GB RAM
Disk Space: 400 GB SSD
Issue Description:
MariaDB server crashes frequently with the following signal:
vbnet
Copy code
Core was generated by `/usr/sbin/mysqld'.
Program terminated with signal 6, Aborted.
#0 0x00007fef2d2c0aa1 in pthread_kill ()
from /lib64/libpthread.so.0
I attempted to analyze the core dump using gdb and got the following backtrace:
Code:
(gdb) bt
#0 0x00007fef2d2c0aa1 in pthread_kill ()
from /lib64/libpthread.so.0
#1 0x00005600d0a2adae in handle_fatal_signal ()
#2 <signal handler called>
#3 0x00007fef2c70e387 in raise ()
from /lib64/libc.so.6
#4 0x00007fef2c70fa78 in abort ()
from /lib64/libc.so.6
#5 0x00005600d0723ae0 in ut_dbg_assertion_failed(char const*, char const*, unsigned int) ()
#6 0x00005600d07236d8 in flst_read_addr(unsigned char const*, mtr_t*) [clone .isra.9] [clone .part.10]
()
#7 0x00005600d0e1d40e in trx_purge_rseg_get_next_history_log(unsigned long*) ()
#8 0x00005600d0e1e257 in trx_purge_get_next_rec(unsigned long*, mem_block_info_t*) ()
#9 0x00005600d0e1eaa3 in trx_purge(unsigned long, bool) ()
#10 0x00005600d0e03f23 in srv_purge_coordinator_thread ()
#11 0x00007fef2d2bbea5 in start_thread ()
from /lib64/libpthread.so.0
#12 0x00007fef2c7d6b0d in clone ()
from /lib64/libc.so.6
Steps Taken
Analyzed Core Dump:
Used gdb to generate the backtrace.
Identified the signal causing the crash (signal 6, Aborted).
Checked Logs:
No relevant error logs found in /var/log/mysql/error.log or /var/log/mariadb/mariadb.log.
Reviewed System Resources:
Memory seems adequate with 4.2 GB available out of 6 GB.
Disk space utilization is at 16% of 400 GB.
Tried Basic Fixes:
Ensured all packages are up to date.
Restarted MariaDB service multiple times.
Attempted to Apply Debugging Info:
Encountered issues with debuginfo-install command while in gdb:
Core Dump Analysis:
Could someone help interpret the backtrace and suggest specific causes or fixes for the frequent crashes?
Upgrading MariaDB:
Detailed guidance on how to upgrade MariaDB to the latest stable version on CentOS 7.
Any precautions or steps to ensure a smooth upgrade process without data loss.
-Any additional logs or diagnostics that I should collect?
-Recommendations for configuring MariaDB to avoid such crashes in the future.
Your assistance is greatly appreciated as this issue is impacting our production environment. Thank you in advance for your time and help