docker mariadb server won't start after server downtime - mysql
my server was down for a few hours and when the datacenter was back online i couldnt start my database sever, i do not know if i can do anything to recovery any of my databases, and any help would be appreciated. This is the error log i am receiving using docker logs, i tried everything i can think of, please help.
InnoDB: about forcing recovery.
180503 15:09:51 [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.3.4-MariaDB-10.3.4+maria~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759982 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f052c0009a8
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 = 0x7f053bffed78 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x55794acdcafe]
mysqld(handle_fatal_signal+0x347)[0x55794a755a27]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f0593cfd890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0592088067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0592089448]
mysqld(+0x4af752)[0x55794a4a3752]
mysqld(+0xa1bb35)[0x55794aa0fb35]
mysqld(+0xa1cd42)[0x55794aa10d42]
mysqld(+0xa1d8ce)[0x55794aa118ce]
mysqld(+0xa014a0)[0x55794a9f54a0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f0593cf6064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f059213b62d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
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.
Fatal signal 11 while backtracing
2018-05-03 15:10:40 0 [Note] mysqld (mysqld 10.3.4-MariaDB-10.3.4+maria~jessie) starting as process 1 ...
2018-05-03 15:10:40 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-05-03 15:10:40 0 [Note] InnoDB: Uses event mutexes
2018-05-03 15:10:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-05-03 15:10:40 0 [Note] InnoDB: Using Linux native AIO
2018-05-03 15:10:40 0 [Note] InnoDB: Number of pools: 1
2018-05-03 15:10:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
2018-05-03 15:10:40 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2018-05-03 15:10:40 0 [Note] InnoDB: Completed initialization of buffer pool
2018-05-03 15:10:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-05-03 15:10:40 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=60464127549
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=823] log sequence number 60464206926 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=384] log sequence number 60464207004 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=385] log sequence number 60464207757 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=388] log sequence number 60464208763 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=389] log sequence number 60464210321 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=410] log sequence number 60464214175 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 60464214258 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=193] log sequence number 60464214302 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 60464214346 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=195] log sequence number 60464214390 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=196] log sequence number 60464214434 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=197] log sequence number 60464214478 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=198] log sequence number 60464215658 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=199] log sequence number 60464215702 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=200] log sequence number 60464215746 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=401] log sequence number 60464215746 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=201] log sequence number 60464215790 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=202] log sequence number 60464216128 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=203] log sequence number 60464216397 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=204] log sequence number 60464216659 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=205] log sequence number 60464217025 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 60464201860 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=391] log sequence number 60464201904 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=586] log sequence number 60464197776 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=392] log sequence number 60464202212 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=0, page number=821] log sequence number 60464207440 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [Note] InnoDB: Starting final batch to recover 70 pages from redo log.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=607, page number=28013] log sequence number 60464199864 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=607, page number=3] log sequence number 60464199832 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:40 0 [ERROR] InnoDB: Page [page id: space=607, page number=27055] log sequence number 60464199929 is in the future! Current system log sequence number 60464197030.
2018-05-03 15:10:40 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/xtradbinnodb-recovery-modes/ for information about forcing recovery.
2018-05-03 15:10:41 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-05-03 15:10:41 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-05-03 15:10:41 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-05-03 15:10:41 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-05-03 15:10:41 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-05-03 15:10:41 0 [Note] InnoDB: Waiting for purge to start
2018-05-03 15:10:41 0x7f57917fa700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.4/storage/innobase/include/fut0lst.ic line 85
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/xtradbinnodb-recovery-modes/
InnoDB: about forcing recovery.
180503 15:10:41 [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.3.4-MariaDB-10.3.4+maria~jessie
key_buffer_size=134217728
read_buffer_size=2097152
max_used_connections=0
max_threads=102
thread_count=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759982 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f57800009a8
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 = 0x7f57917f9d78 thread_stack 0x49000
mysqld(my_print_stacktrace+0x2e)[0x558c4f0cbafe]
mysqld(handle_fatal_signal+0x347)[0x558c4eb44a27]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f57e1033890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f57df3be067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f57df3bf448]
mysqld(+0x4af752)[0x558c4e892752]
mysqld(+0xa1bb35)[0x558c4edfeb35]
mysqld(+0xa1cd42)[0x558c4edffd42]
mysqld(+0xa1d8ce)[0x558c4ee008ce]
mysqld(+0xa014a0)[0x558c4ede44a0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f57e102c064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f57df47162d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0):
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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
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.
Fatal signal 11 while backtracing
i tried everything but the only solution that worked for me in case someone else needs help is using MySQL Utilities.
first i backed up the var/lib/mysql into /backup/db folder then i run this: mysqlfrm --server=root:ROOTPASS#host DATABASE_NAME:TABLENAME.frm --port=3307 --user=root , the command will return the CREATE TABLE statement .
then in a newly installed database i run the create table.
After that i run ALTER TABLE mydb.mytable DISCARD TABLESPACE;
copy mytable.ibd using cp -ap /home/backup/DATABASE_NAME/ mytable.ibd /var/lib/mysql/DATABASE_NAME
then i run ALTER TABLE mydb.mytable IMPORT TABLESPACE;
you have to repeate the process for each table and it finally worked.
I hope this is helpful
You should use Innodb force recovery mode to start db, backup your data. After backup, you should clean your database file switch db to normal mode (remove innodb_force_recovery) and then restore database
For innodb recovery mode refer https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html .Remember, in recovery mode you can read data only and cannot update, insert or delete so you should backup your database only
Detail step: find your my.ini (on linux my.cnf) add this line to your [mysql]
innodb_force_recovery = 1
Try to increase it from 1 -> 6 until you can start your database server
Related
Lost connect to MySQL server during query
I have an Innodb database which have a big table with many rows. Once I'm trying to access the data or run any query(like "check table_name") against this specific table mysql crashes(restarts) and I'm getting the error: ERROR 2013 (HY000): Lost connection to MySQL server during query I have already tried to increase max_packetsize and the net_timeouts flags. Any help will be appreciated, Thanks! Edit: Crash log: 2022-12-30T16:25:56.676880Z 208 [ERROR] InnoDB: In pages [page id: space=372, pa ge number=11135] and [page id: space=372, page number=11136] of index `GEN_CLUST _INDEX` of table `SHAS_2015_NEW`.`b_media_21_646_0000_11925` InnoDB: broken FIL_PAGE_NEXT or FIL_PAGE_PREV links 2022-12-30T16:25:56.676925Z 208 [ERROR] InnoDB: In pages [page id: space=372, pa ge number=11135] and [page id: space=372, page number=11136] of index `GEN_CLUST _INDEX` of table `SHAS_2015_NEW`.`b_media_21_646_0000_11925` InnoDB: 'compact' flag mismatch 2022-12-30T16:25:56.676936Z 208 [ERROR] InnoDB: Page index id 0 != data dictiona ry index id 577 2022-12-30 18:25:56 0x7fa1384e9700 InnoDB: Assertion failure in thread 14033041 1136768 in file btr0btr.cc line 4710 InnoDB: Failing assertion: !page_is_empty(page) || (level == 0 && page_get_page_ no(page) == dict_index_get_page(index)) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 16:25:56 UTC - 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. Attempting to collect some information that could help diagnose the problem. As this is a crash and something is definitely wrong, the information collection process might fail. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76388 K b ytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fa0f81dd110 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 = 7fa1384e8e70 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe8e68b] /usr/sbin/mysqld(handle_fatal_signal+0x36f)[0x77524f] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fa67f45d390] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7fa67e816438] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7fa67e81803a] /usr/sbin/mysqld[0x74a77c] /usr/sbin/mysqld[0x10dd73d] /usr/sbin/mysqld(_Z18btr_validate_indexP12dict_index_tPK5trx_tb+0x264)[0x10dec34 ] /usr/sbin/mysqld(_ZN11ha_innobase5checkEP3THDP15st_ha_check_opt+0x278)[0xf2a378] /usr/sbin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x7b)[0x7cd71b] /usr/sbin/mysqld[0xdb48f4] /usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0x97)[0xdb5497] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x2160)[0xc42570] /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3dd)[0xc473ad] /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11a 0)[0xc48610] /usr/sbin/mysqld(_Z10do_commandP3THD+0x1c7)[0xc49ae7] /usr/sbin/mysqld(handle_connection+0x290)[0xd0e140] /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeb03e4] /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7fa67f4536ba] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa67e8e851d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7fa0f8072240): check table b_media_21_646_0000_11925 Connection ID (thread ID): 208 Status: NOT_KILLED 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. 2022-12-30T16:25:56.970335Z 0 [Warning] Changed limits: max_open_files: 1024 (re quested 5000) 2022-12-30T16:25:56.970397Z 0 [Warning] Changed limits: table_open_cache: 431 (r equested 2000) 2022-12-30T16:25:57.145883Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see doc umentation for more details). 2022-12-30T16:25:57.148901Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.33-0ubuntu0.16 .04.1-log) starting as process 9454 ... 2022-12-30T16:25:57.153242Z 0 [Note] InnoDB: PUNCH HOLE support available 2022-12-30T16:25:57.153267Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-12-30T16:25:57.153272Z 0 [Note] InnoDB: Uses event mutexes 2022-12-30T16:25:57.153276Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-12-30T16:25:57.153283Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-12-30T16:25:57.153286Z 0 [Note] InnoDB: Using Linux native AIO 2022-12-30T16:25:57.153526Z 0 [Note] InnoDB: Number of pools: 1 2022-12-30T16:25:57.153643Z 0 [Note] InnoDB: Using CPU crc32 instructions 2022-12-30T16:25:57.155093Z 0 [Note] InnoDB: Initializing buffer pool, total siz e = 20G, instances = 8, chunk size = 128M 2022-12-30T16:25:58.482523Z 0 [Note] InnoDB: Completed initialization of buffer pool 2022-12-30T16:25:58.719968Z 0 [Note] InnoDB: If the mysqld execution user is aut horized, page cleaner thread priority can be changed. See the man page of setpri ority(). 2022-12-30T16:25:58.744995Z 0 [Note] InnoDB: Highest supported file format is Ba rracuda. 2022-12-30T16:25:58.915826Z 0 [Note] InnoDB: Log scan progressed past the checkp oint lsn 10408206134578 2022-12-30T16:25:58.915857Z 0 [Note] InnoDB: Doing recovery: scanned up to log s equence number 10408206134587 2022-12-30T16:25:58.915862Z 0 [Note] InnoDB: Database was not shutdown normally! 2022-12-30T16:25:58.915872Z 0 [Note] InnoDB: Starting crash recovery. 2022-12-30T16:25:59.270028Z 0 [Note] InnoDB: Last MySQL binlog file position 0 1 862900, file name mysql-bin.000001 2022-12-30T16:26:00.014203Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2022-12-30T16:26:00.014242Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-12-30T16:26:00.014281Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-12-30T16:26:00.075009Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-12-30T16:26:00.076863Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 2022-12-30T16:26:00.076904Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 2022-12-30T16:26:00.077640Z 0 [Note] InnoDB: Waiting for purge to start 2022-12-30T16:26:00.127880Z 0 [Note] InnoDB: 5.7.33 started; log sequence number 10408206134587 2022-12-30T16:26:00.128095Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2022-12-30T16:26:00.128605Z 0 [Note] Plugin 'FEDERATED' is disabled. 2022-12-30T16:26:00.138272Z 0 [Note] Recovering after a crash using /var/log/mysql/mysql-bin 2022-12-30T16:26:00.138325Z 0 [Note] Starting crash recovery... 2022-12-30T16:26:00.138384Z 0 [Note] Crash recovery finished. If I'm Using select with Limit statement then I can select up to 681,000 rows
How to fix corupted MySQL installation
Due to some issues with the server, a number of InnoDB database folders with ibd, frm and TRN files were deleted (only affects databases not really needed anymore). Currently MySQL service starts only with the following setting: innodb_force_recovery = 5 Then it crashes every few seconds, here's an extract from the log file 2022-10-11 17:38:54 27975 [Note] InnoDB: 1.2.10 started; log sequence number 313646609430 2022-10-11 17:38:54 27975 [Note] InnoDB: !!! innodb_force_recovery is set to 5 !!! 2022-10-11 17:38:54 27975 [Note] Server hostname (bind-address): '*'; port: 3306 2022-10-11 17:38:54 27975 [Note] IPv6 is available. 2022-10-11 17:38:54 27975 [Note] - '::' resolves to '::'; 2022-10-11 17:38:54 27975 [Note] Server socket created on IP: '::'. 2022-10-11 17:38:54 27975 [Note] Event Scheduler: Loaded 0 events 2022-10-11 17:38:54 27975 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.10' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 4087 log sequence number 315137164614 InnoDB: is in the future! Current system log sequence number 313646609430. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 27975 [ERROR] InnoDB: Failed to find tablespace for table '"wp_website"."wp_options"' in the cache. Attempting to load the tablespace with space id 34249. 2022-10-11 17:38:55 27975 [Warning] InnoDB: Allocated tablespace 34249, old maximum was 0 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 252899 log sequence number 471118864984 InnoDB: is in the future! Current system log sequence number 313646609430. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 85552 log sequence number 471118895771 InnoDB: is in the future! Current system log sequence number 313646609430. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 147803 log sequence number 471118895778 InnoDB: is in the future! Current system log sequence number 313646609430. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 4 log sequence number 470722597051 InnoDB: is in the future! Current system log sequence number 313646609440. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 13 log sequence number 315130852444 InnoDB: is in the future! Current system log sequence number 313646609440. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 3 log sequence number 315130852367 InnoDB: is in the future! Current system log sequence number 313646609440. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-10-11 17:38:55 7f1d2c06a700 InnoDB: Error: page 22 log sequence number 315133587106 InnoDB: is in the future! Current system log sequence number 313646609440. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. InnoDB: A new raw disk partition was initialized or InnoDB: innodb_force_recovery is on: we do not allow InnoDB: database modifications by the user. Shut down InnoDB: mysqld and edit my.cnf so that newraw is replaced InnoDB: with raw, and innodb_force_... is removed. 14:38:55 UTC - mysqld got signal 11 ; 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. 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. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=1 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68216 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x1d46900 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 = 7f1d2c069e18 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8bfd45] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x65b074] /lib64/libpthread.so.0[0x34c700f7e0] /usr/sbin/mysqld[0x9a45b2] /usr/sbin/mysqld[0x97e382] /usr/sbin/mysqld[0x943807] /usr/sbin/mysqld[0x9a236d] /usr/sbin/mysqld[0x9a2bfd] /usr/sbin/mysqld[0x8e1729] /usr/sbin/mysqld(_Z15ha_rollback_lowP3THDb+0x87)[0x5a27a7] /usr/sbin/mysqld(_Z17ha_rollback_transP3THDb+0x4c)[0x5a256c] /usr/sbin/mysqld(_Z19trans_rollback_stmtP3THD+0x29)[0x764a19] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x23d)[0x6d2fdd] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x32f)[0x6d7a5f] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xe28)[0x6d8978] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x6a682f] /usr/sbin/mysqld(handle_one_connection+0x47)[0x6a6957] /usr/sbin/mysqld(pfs_spawn_thread+0x139)[0xadc7d9] /lib64/libpthread.so.0[0x34c7007aa1] /lib64/libc.so.6(clone+0x6d)[0x34c6ce8c4d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f1d04004f30): is an invalid pointer Connection ID (thread ID): 1 Status: NOT_KILLED 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. 221011 17:38:55 mysqld_safe Number of processes running now: 0 221011 17:38:55 mysqld_safe mysqld restarted How can I fix the problem? Or at least create the dumps of a few databases I need?
Xampp MySql Error: MySQL shutdown unexpectedly
my Xampp MySql won't start. Elsewhere in this forum was has been advised to change the file name C:\xampp\mysql\data\ibdata1 to ibdata1.bak and turn off the Xampp. But it did not help. Is there a way to fix this? 2020-09-17 17:19:47 2 [ERROR] InnoDB: Page [page id: space=33, page number=1] log sequence number 402782 is in the future! Current system log sequence number 47064. 2020-09-17 17:19:47 2 [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. 2020-09-17 17:19:47 0 [Note] InnoDB: 10.4.11 started; log sequence number 47055; transaction id 347965 2020-09-17 17:19:47 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool 2020-09-17 17:19:47 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-09-17 17:19:47 0 [ERROR] InnoDB: Page [page id: space=0, page number=243] log sequence number 336525986 is in the future! Current system log sequence number 47064. 2020-09-17 17:19:47 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. 2020-09-17 17:19:47 0 [ERROR] InnoDB: Page [page id: space=0, page number=309] log sequence number 332378035 is in the future! Current system log sequence number 47064. 2020-09-17 17:19:47 0 [Note] Server socket created on IP: '::'. 2020-09-17 17:19:47 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespac
Your files (maybe log files) and the time of your PC have conflict! log sequence number 402782 is in the future! check your PC time and sync it with real time! remove all files which have a date-time more than your PC date-time (if possible! if not, create a new one in a proper date). For example your PC date is 2019-xx-xx and your files is 2020-xx-xx.
MySql stops unexpectedly
MySql stops unexpectedly Here is a copy of Error log: 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=305] log sequence number 2834539 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2019-07-03 13:27:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-03 13:27:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB. 2019-07-03 13:27:50 0 [Note] InnoDB: Waiting for purge to start 2019-07-03 13:27:50 0 [Note] InnoDB: 10.3.16 started; log sequence number 1604002; transaction id 1432 2019-07-03 13:27:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 2841120 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=243] log sequence number 2082633 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=0] log sequence number 1608629 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 0 [Note] Plugin 'FEEDBACK' is disabled. 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=1] log sequence number 1604111 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 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. 2019-07-03 13:27:50 0 [Note] Server socket created on IP: '::'. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page What can I do to get my database up and running again? All help is greatly appreciated!
I have faced the same problem. I just followed the below steps Step 1: Moved(cut/paste) all the files in C:\xampp\mysql\data to desired backup location. Step 2: After that copied all the files from C:\xampp\mysql\backup to C:\xampp\mysql\data Step 3: Restarted mysql and checked the phpmyadmin url, it worked. Step 4: After that stopped mysql and copied ibdata1 file from backup location to C:\xampp\mysql\data Step 5: Restarted mysql Step 6: After that copied all database folders and checked all the tables, It worked.
I also faced this issue and searched a lot only one solution worked for me. Just copy all files from C:\xampp\mysql\backup to C:\xampp\mysql\data Make sure to take backup of your data folder to avoid any further problems. If you see any error related to table engine then you can copy file ibdata1 from your backup data folder to current data folder
Seems that there is corruption in MySQL log and/or data files, one way to workaround this problem is to start MySQL in recovery mode. From my.ini in windows (or my.cnf in Linux) add the following line: innodb_force_recovery=1 under [mysqld] section then re-start MySQL service. If the problem persisted, mysqlcheck can help, move to the folder where MySQL binaries exist in your machine, and in Command Line execute ./mysqlcheck.exe --all-databases this will list tables that are corrupted Reference: https://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
Just Unintall XAMPP and the reinstall it , it will resolve all the issue , but make sure to have the backup of your MYSQL database.
If your backup folder doesn't include your latest DB changes and you are stuck with collation of in use, then do this instead: Install another XAMPP instance in new folder; Copy the single folder of: [old_xampp]/mysql/data/[table_name]/ into [new_xampp]/mysql/data/; Copy a file from: [old_xampp]/mysql/data/ibdata1 to: [new_xampp]/mysql/data/ibdata1 and replace it; Stop old XAMPP; Run new XAMPP. DONE! All your new table entries should be brought back.
mysql database and doublewrite buffer corrupt. How to drop table/database?
Is it possible to drop a table/database manually if it is corrupt? How can I clear the ibdata doublewrite buffer? I just restored my server. However mysql is not coming up. The error message recomments to set innodb_force_recovery=6. Which allowed to start mysql. So I identified the defect table. However no matter what I try check / repair / drop the corrupt table / database which always ends up in mysql stopping and throwing the error: ERROR 2013 (HY000): Lost connection to MySQL server during query Here is the mysql error log from starting mysql: 140702 13:40:36 [Note] Plugin 'FEDERATED' is disabled. 140702 13:40:36 [Warning] option 'innodb-buffer-pool-size': signed value 2097152 adjusted to 5242880 140702 13:40:36 [Warning] option 'innodb-additional-mem-pool-size': signed value 512000 adjusted to 524288 140702 13:40:36 InnoDB: The InnoDB memory heap is disabled 140702 13:40:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140702 13:40:36 InnoDB: Compressed tables use zlib 1.2.3.4 140702 13:40:36 InnoDB: Initializing buffer pool, size = 5.0M 140702 13:40:36 InnoDB: Completed initialization of buffer pool 140702 13:40:36 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 140702 13:40:37 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... 140702 13:40:37 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 140702 13:40:37 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Warning: database page corruption or a failed InnoDB: file read of space 0 page 79918. InnoDB: Trying to recover it from the doublewrite buffer. InnoDB: Dump of the page: 140702 13:40:37 InnoDB: Page dump in ascii and hex (16384 bytes): Hexdata InnoDB: End of page dump 140702 13:40:37 InnoDB: Page checksum 3463763561, prior-to-4.0.14-form checksum 3074131693 InnoDB: stored checksum 2986557383, prior-to-4.0.14-form stored checksum 3074131693 InnoDB: Page lsn 3 3511673317, low 4 bytes of lsn at page end 3511673317 InnoDB: Page number (if stored to page already) 79918, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an index page where index id is 5918 InnoDB: Dump of corresponding page in doublewrite buffer: 140702 13:40:37 InnoDB: Page dump in ascii and hex (16384 bytes): Hexdata ... InnoDB: End of page dump 140702 13:40:37 InnoDB: Page checksum 1693035738, prior-to-4.0.14-form checksum 533526999 InnoDB: stored checksum 1060638083, prior-to-4.0.14-form stored checksum 533526999 InnoDB: Page lsn 3 3511586897, low 4 bytes of lsn at page end 3511586897 InnoDB: Page number (if stored to page already) 79918, InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0 InnoDB: Page may be an index page where index id is 5918 InnoDB: Also the page in the doublewrite buffer is corrupt. InnoDB: Cannot continue operation. InnoDB: You can try to recover the database with the my.cnf InnoDB: option: InnoDB: innodb_force_recovery=6 140702 13:40:37 InnoDB: Assertion failure in thread 3064526592 in file trx0sys.c line 604 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. 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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 11:40:37 UTC - 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. 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. key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346063 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 = 0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb72a35c3] /usr/sbin/mysqld(handle_fatal_signal+0x484)[0xb7150004] [0xb6e0c500] 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. Is there any way to drop a database / table while mysql is offline? Is it possible to clear the ibdata doublewrite buffer since this is blogging mysql from starting normally?