Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.4.34
-
None
-
Operating System: CentOS 7
MariaDB Version: 10.4.34
Server Version: 10.4.34-MariaDB-log
Source Revision: 16394f1aa1b4097f897b8ab01ea2064726cca059
key_buffer_size: 134217728
read_buffer_size: 131072
max_used_connections: 0
max_threads: 202
thread_count: 4
Memory Usage: key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 575622 K bytes
Operating System: CentOS 7 MariaDB Version: 10.4.34 Server Version: 10.4.34-MariaDB-log Source Revision: 16394f1aa1b4097f897b8ab01ea2064726cca059 key_buffer_size: 134217728 read_buffer_size: 131072 max_used_connections: 0 max_threads: 202 thread_count: 4 Memory Usage: key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 575622 K bytes
Description
Hello, I am experiencing InnoDB corruption errors that are causing the database to fail on startup. Below is the relevant section from the error log:
Server version: 10.4.34-MariaDB-log
|
source revision: 16394f1aa1b4097f897b8ab01ea2064726cca059
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=202
|
thread_count=4
|
It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads = 575622 K bytes of memory. Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7fedf80009a8
|
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 = 0x7fee2cf0abf0 thread_stack 0x49000
|
/sbin/mysqld(my_print_stacktrace+0x2e)[0x55b065526c4e]
|
/sbin/mysqld(handle_fatal_signal+0x2ff)[0x55b064f79d2f]
|
sigaction.c:0(__restore_rt)[0x7fee97e90630]
|
/lib64/libc.so.6(gsignal+0x37)[0x7fee972db387]
|
/lib64/libc.so.6(abort+0x148)[0x7fee972dca78]
|
/sbin/mysqld(+0x5e6ae0)[0x55b064c72ae0]
|
/sbin/mysqld(+0x5e66d8)[0x55b064c726d8]
|
/sbin/mysqld(+0xce040e)[0x55b06536c40e]
|
/sbin/mysqld(+0xce1257)[0x55b06536d257]
|
/sbin/mysqld(+0xce1aa3)[0x55b06536daa3]
|
/sbin/mysqld(+0xcc6f23)[0x55b065352f23]
|
pthread_create.c:0(start_thread)[0x7fee97e88ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7fee973a3b0d]
|
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x0): (null)
|
Connection ID (thread ID): 2
|
Status: NOT_KILLED
|
We have tried several troubleshooting steps, including adjusting buffer sizes and verifying configuration settings, but the issue persists. Assistance or a point in the correct direction would be highly appreciated.
Console output:
[root@cwp ~]# ps aux | grep mysqld
|
root 28118 0.0 0.0 112812 972 pts/1 S+ 10:10 0:00 grep --color=auto mysqld
|
[root@cwp ~]# sudo tail -n 100 /var/lib/mysql/mysqld.log
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=11852] log sequence number 3235747429 is in the future! Current system log sequence number 3235709973.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=296] log sequence number 3235750030 is in the future! Current system log sequence number 3235709973.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Page [page id: space=0, page number=8348] log sequence number 3235750030 is in the future! Current system log sequence number 3235709973.
|
2024-07-22 10:08:52 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
|
2024-07-22 10:08:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
|
2024-07-22 10:08:53 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
|
2024-07-22 10:08:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
|
2024-07-22 10:08:53 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
|
2024-07-22 10:08:53 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
|
2024-07-22 10:08:53 0 [Note] InnoDB: Waiting for purge to start
|
2024-07-22 10:08:53 0x7fee2cf0b700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.34/storage/innobase/include/fut0lst.inl line 67
|
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
|
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.
|
240722 10:08:53 [ERROR] mysqld got signal 6 ;
|
Sorry, we probably made a mistake, and this is a bug.
|
|
|
Your assistance in bug reporting will enable us to fix this for the next release.
|
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.4.34-MariaDB-log source revision: 16394f1aa1b4097f897b8ab01ea2064726cca059
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=202
|
thread_count=4
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 575622 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7fedf80009a8
|
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 = 0x7fee2cf0abf0 thread_stack 0x49000
|
//sbin/mysqld(my_print_stacktrace+0x2e)[0x55b065526c4e]
|
//sbin/mysqld(handle_fatal_signal+0x2ff)[0x55b064f79d2f]
|
sigaction.c:0(__restore_rt)[0x7fee97e90630]
|
/lib64/libc.so.6(gsignal+0x37)[0x7fee972db387]
|
/lib64/libc.so.6(abort+0x148)[0x7fee972dca78]
|
//sbin/mysqld(+0x5e6ae0)[0x55b064c72ae0]
|
//sbin/mysqld(+0x5e66d8)[0x55b064c726d8]
|
//sbin/mysqld(+0xce040e)[0x55b06536c40e]
|
//sbin/mysqld(+0xce1257)[0x55b06536d257]
|
//sbin/mysqld(+0xce1aa3)[0x55b06536daa3]
|
//sbin/mysqld(+0xcc6f23)[0x55b065352f23]
|
pthread_create.c:0(start_thread)[0x7fee97e88ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7fee973a3b0d]
|
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x0): (null)
|
Connection ID (thread ID): 2
|
Status: NOT_KILLED
|
|
|
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on
|
|
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
|
information that should help you find out what is causing the crash.
|
|
|
We think the query pointer is invalid, but we will try to print it anyway.
|
Query:
|
|
|
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 unlimited unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes 23137 23137 processes
|
Max open files 32235 32235 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 23137 23137 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: |/usr/lib/systemd/systemd-coredump
|
|
|
Kernel version: Linux version 3.10.0-1160.119.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Jun 4 14:43:51 UTC 2024
|
|
|
240722 10:08:53 mysqld_safe mysqld from pid file /var/lib/mysql/cwp.buyorganicsa.co.za.pid ended
|
[root@cwp ~]#
|