[MDEV-12891] Server Crash 0xe06d7363 Created: 2017-05-24  Updated: 2020-12-08  Resolved: 2017-10-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.1.23
Fix Version/s: 10.1.24, 10.0.31, 10.2.7, 10.3.1

Type: Bug Priority: Critical
Reporter: David Appelman Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: crash
Environment:

Windows Server 2012 R2, Intel Xeon E5-2630 v3, 128GB RAM, Raid 10 SSD

Issue Links:
Relates
relates to MDEV-12444 [Draft] InnoDB: Failing assertion: to... Closed
relates to MDEV-13733 Server Crash - mysqld got exception 0... Closed

 Description   

My server is crashing periodically (every other day?) and I'm getting this report: Could possibly be a memory thing, but I'm not sure. I don't believe this was an issue in 10.0.20, which I recently upgraded from.

mysqld got exception 0xe06d7363 ;
 
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.1.23-MariaDB
 
key_buffer_size=134217728
 
read_buffer_size=131072
 
max_used_connections=86
 
max_threads=1001
 
thread_count=86
 
It is possible that mysqld could use up to
 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
KERNELBASE.dll!RaiseException()
 
mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
KERNEL32.DLL!BaseThreadInitThunk()
 
ntdll.dll!RtlUserThreadStart()
 
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.

Here's my config file:

[mysqld]
 
 
 
datadir=C:/Program Files/MariaDB 10.0/data
 
port=3306
 
 
 
character-set-server=latin1
 
default_storage_engine=innodb
 
 
 
sql_mode="NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
 
 
 
innodb_file_per_table
 
innodb_buffer_pool_size=80G
 
innodb_buffer_pool_instances=16
 
innodb_log_file_size=4G
 
innodb_flush_log_at_trx_commit=2
 
innodb_flush_neighbors=0
 
innodb_thread_concurrency=0
 
 
 
aria_pagecache_buffer_size=2G
 
 
 
query_cache_type = 1
 
query_cache_limit = 256K
 
query_cache_min_res_unit = 2k
 
query_cache_size = 80M
 
 
 
max_connections=10000
 
 
 
skip-name-resolve
 
 
 
tmp_table_size=256M
 
max_heap_table_size=256M
 
 
 
max_allowed_packet=16M
 
 
 
table_open_cache = 2000
 
table-definition-cache = 2000
 
open_files_limit = 14000
 
innodb_open_files = 6000
 
 
 
thread_pool_max_threads = 1000
 
 
 
[client]
 
 
 
port=3306



 Comments   
Comment by Elena Stepanova [ 2017-05-24 ]

Is it the very end of the error log after a crash, or is there anything else?
Better still, could you please attach the whole error log from server startup till the next restart after the crash?
Thanks.

Comment by David Appelman [ 2017-05-24 ]

Actually, this error was spit out a few times in a few minutes, sorry, I should have included everything, but I didn't notice this right away:

Timestamp, Thread, Type, Details
 
2017-05-24 4:48:27, , [ERROR], mysqld got exception 0xe06d7363 ;
 
, , , 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.1.23-MariaDB
 
, , , key_buffer_size=134217728
 
, , , read_buffer_size=131072
 
, , , max_used_connections=858
 
, , , max_threads=1001
 
, , , thread_count=617
 
, , , It is possible that mysqld could use up to
 
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
, , , KERNELBASE.dll!RaiseException()
 
, , , mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
, , , mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
, , , mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
, , , mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
, , , mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
, , , mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
, , , mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
, , , mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
, , , KERNEL32.DLL!BaseThreadInitThunk()
 
, , , ntdll.dll!RtlUserThreadStart()
 
, , , 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.
 
2017-05-24  4:50:05, 5304, Note, InnoDB: Using mutexes to ref count buffer pool pages
 
2017-05-24  4:50:05, 5304, Note, InnoDB: The InnoDB memory heap is disabled
 
2017-05-24  4:50:05, 5304, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-24  4:50:05, 5304, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
 
2017-05-24  4:50:05, 5304, Note, InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-24  4:50:05, 5304, Note, InnoDB: Using generic crc32 instructions
 
2017-05-24  4:50:05, 5304, Note, InnoDB: Initializing buffer pool, size = 80.0G
 
2017-05-24  4:50:08, 5304, Note, InnoDB: Completed initialization of buffer pool
 
2017-05-24  4:50:09, 5304, Note, InnoDB: Highest supported file format is Barracuda.
 
2017-05-24  4:50:09, 5304, Note, InnoDB: Starting crash recovery from checkpoint LSN=32922498147900
 
2017-05-24  4:50:10, 5304, Note, InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
2017-05-24  4:50:23, 5304, Note, InnoDB: Read redo log up to LSN=32923502880256
 
2017-05-24  4:50:38, 5304, Note, InnoDB: Read redo log up to LSN=32924741182976
 
2017-05-24  4:50:53, 5304, Note, InnoDB: Read redo log up to LSN=32925550552576
 
2017-05-24  4:51:08, 5304, Note, InnoDB: Read redo log up to LSN=32926193853952
 
, , , InnoDB: 1 transaction(s) which must be rolled back or cleaned up
 
, , , InnoDB: in total 1 row operations to undo
 
, , , InnoDB: Trx id counter is 67176506624
 
2017-05-24  4:51:10, 5304, Note, InnoDB: Starting final batch to recover 75074 pages from redo log
 
2017-05-24  4:51:26, 5304, Note, InnoDB: 128 rollback segment(s) are active.
 
2017-05-24  4:51:26, 5888, Note, InnoDB: Starting in background the rollback of recovered transactions
 
2017-05-24  4:51:26, 5304, Note, InnoDB: Waiting for purge to start
 
, , , 2017-05-24 04:51:26 1700  InnoDB: Rolling back trx with id 67176499227, 1 rows to undo
 
2017-05-24  4:51:26, 5888, Note, InnoDB: Rollback of trx with id 67176499227 completed
 
2017-05-24  4:51:26, 5888, Note, InnoDB: Rollback of non-prepared transactions completed
 
2017-05-24  4:51:26, 5304, Note, InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 32926236583147
 
2017-05-24  4:51:35, 3384, Note, InnoDB: Dumping buffer pool(s) not yet started
 
2017-05-24  4:51:35, 5304, Note, Plugin 'FEEDBACK' is disabled.
 
2017-05-24  4:51:35, 5304, Note, Server socket created on IP: '::'.
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffdb1` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffdb3` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffdb5` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffdb9` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe1b` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe1e` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:35 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe24` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe40` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe4b` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe4f` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe54` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffe56` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffeb7` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffec4` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffee6` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffee9` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_ffef0` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff00` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff2c` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff33` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff39` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff41` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff47` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff4f` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff51` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff65` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff90` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fff9f` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fffbc` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
, , , 2017-05-24 04:51:36 14b8  InnoDB: Error: table `temp`.`#sql1010_7b52e_fffe5` does not exist in the InnoDB internal
 
, , , InnoDB: data dictionary though MySQL is trying to drop it.
 
, , , InnoDB: Have you copied the .frm file of the table to the
 
, , , InnoDB: MySQL database directory from another database?
 
, , , InnoDB: You can look for further help from
 
, , , InnoDB: http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
 
2017-05-24  4:51:36, 5304, Warning, 'user' entry 'root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:51:36, 5304, Warning, 'proxies_priv' entry '@% root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:51:36, 5304, Note, C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
 
, , , Version: '10.1.23-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-24  4:51:36, 660, ERROR, mysqld.exe: Table '.\blogs\wp_posts' is marked as crashed and should be repaired
 
2017-05-24  4:51:36, 660, Warning, Checking table:   '.\blogs\wp_posts'
 
2017-05-24  4:51:36, 5972, ERROR, mysqld.exe: Table '.\ottoneu_leagues\teams' is marked as crashed and should be repaired
 
2017-05-24  4:51:36, 5972, Warning, Checking table:   '.\ottoneu_leagues\teams'
 
2017-05-24 4:51:37, , [ERROR], mysqld got exception 0xe06d7363 ;
 
, , , 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.1.23-MariaDB
 
, , , key_buffer_size=134217728
 
, , , read_buffer_size=131072
 
, , , max_used_connections=86
 
, , , max_threads=1001
 
, , , thread_count=86
 
, , , It is possible that mysqld could use up to
 
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
, , , KERNELBASE.dll!RaiseException()
 
, , , mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
, , , mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
, , , mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
, , , mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
, , , mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
, , , mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
, , , mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
, , , mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
, , , KERNEL32.DLL!BaseThreadInitThunk()
 
, , , ntdll.dll!RtlUserThreadStart()
 
, , , 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.
 
2017-05-24  4:51:39, 6272, ERROR, mysqld.exe: Table '.\ottoneu_leagues\players' is marked as crashed and should be repaired
 
2017-05-24  4:51:39, 6272, Warning, Checking table:   '.\ottoneu_leagues\players'
 
2017-05-24  4:52:43, 1144, Note, InnoDB: Using mutexes to ref count buffer pool pages
 
2017-05-24  4:52:43, 1144, Note, InnoDB: The InnoDB memory heap is disabled
 
2017-05-24  4:52:43, 1144, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-24  4:52:43, 1144, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
 
2017-05-24  4:52:43, 1144, Note, InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-24  4:52:43, 1144, Note, InnoDB: Using generic crc32 instructions
 
2017-05-24  4:52:43, 1144, Note, InnoDB: Initializing buffer pool, size = 80.0G
 
2017-05-24  4:52:46, 1144, Note, InnoDB: Completed initialization of buffer pool
 
2017-05-24  4:52:46, 1144, Note, InnoDB: Highest supported file format is Barracuda.
 
2017-05-24  4:52:46, 1144, Note, InnoDB: Starting crash recovery from checkpoint LSN=32926464881699
 
2017-05-24  4:52:48, 1144, Note, InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
, , , InnoDB: 1 transaction(s) which must be rolled back or cleaned up
 
, , , InnoDB: in total 1 row operations to undo
 
, , , InnoDB: Trx id counter is 67176508928
 
2017-05-24  4:52:48, 1144, Note, InnoDB: Starting final batch to recover 161 pages from redo log
 
2017-05-24  4:52:50, 1144, Note, InnoDB: 128 rollback segment(s) are active.
 
2017-05-24  4:52:50, 372, Note, InnoDB: Starting in background the rollback of recovered transactions
 
2017-05-24  4:52:50, 1144, Note, InnoDB: Waiting for purge to start
 
, , , 2017-05-24 04:52:50 174  InnoDB: Rolling back trx with id 67176507969, 1 rows to undo
 
2017-05-24  4:52:50, 372, Note, InnoDB: Rollback of trx with id 67176507969 completed
 
2017-05-24  4:52:50, 372, Note, InnoDB: Rollback of non-prepared transactions completed
 
2017-05-24  4:52:50, 1144, Note, InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 32926465472640
 
2017-05-24  4:52:50, 4424, Note, InnoDB: Dumping buffer pool(s) not yet started
 
2017-05-24  4:52:50, 1144, Note, Plugin 'FEEDBACK' is disabled.
 
2017-05-24  4:52:50, 1144, Note, Server socket created on IP: '::'.
 
2017-05-24  4:52:50, 1144, Warning, 'user' entry 'root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:52:50, 1144, Warning, 'proxies_priv' entry '@% root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:52:50, 1144, Note, C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
 
, , , Version: '10.1.23-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-24 4:52:52, , [ERROR], mysqld got exception 0xe06d7363 ;
 
, , , 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.1.23-MariaDB
 
, , , key_buffer_size=134217728
 
, , , read_buffer_size=131072
 
, , , max_used_connections=65
 
, , , max_threads=1001
 
, , , thread_count=65
 
, , , It is possible that mysqld could use up to
 
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
, , , KERNELBASE.dll!RaiseException()
 
, , , mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
, , , mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
, , , mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
, , , mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
, , , mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
2017-05-24  4:52:53, 6748, ERROR, mysqld.exe: Table '.\ottoneu_football\football_users' is marked as crashed and should be repaired
 
2017-05-24  4:52:53, 6748, Warning, Checking table:   '.\ottoneu_football\football_users'
 
, , , mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
, , , mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
, , , mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
, , , KERNEL32.DLL!BaseThreadInitThunk()
 
, , , ntdll.dll!RtlUserThreadStart()
 
, , , 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.
 
2017-05-24  4:53:56, 5564, Note, InnoDB: Using mutexes to ref count buffer pool pages
 
2017-05-24  4:53:56, 5564, Note, InnoDB: The InnoDB memory heap is disabled
 
2017-05-24  4:53:56, 5564, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-24  4:53:56, 5564, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
 
2017-05-24  4:53:56, 5564, Note, InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-24  4:53:56, 5564, Note, InnoDB: Using generic crc32 instructions
 
2017-05-24  4:53:56, 5564, Note, InnoDB: Initializing buffer pool, size = 80.0G
 
2017-05-24  4:53:59, 5564, Note, InnoDB: Completed initialization of buffer pool
 
2017-05-24  4:53:59, 5564, Note, InnoDB: Highest supported file format is Barracuda.
 
2017-05-24  4:53:59, 5564, Note, InnoDB: Starting crash recovery from checkpoint LSN=32926465472699
 
2017-05-24  4:54:01, 5564, Note, InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
, , , InnoDB: 1 transaction(s) which must be rolled back or cleaned up
 
, , , InnoDB: in total 1 row operations to undo
 
, , , InnoDB: Trx id counter is 67176514048
 
2017-05-24  4:54:01, 5564, Note, InnoDB: Starting final batch to recover 172 pages from redo log
 
2017-05-24  4:54:03, 5564, Note, InnoDB: 128 rollback segment(s) are active.
 
2017-05-24  4:54:03, 5896, Note, InnoDB: Starting in background the rollback of recovered transactions
 
, , , 2017-05-24 04:54:03 1708  InnoDB: Rolling back trx with id 67176512034, 1 rows to undo
 
2017-05-24  4:54:03, 5564, Note, InnoDB: Waiting for purge to start
 
2017-05-24  4:54:03, 5896, Note, InnoDB: Rollback of trx with id 67176512034 completed
 
2017-05-24  4:54:03, 5896, Note, InnoDB: Rollback of non-prepared transactions completed
 
2017-05-24  4:54:04, 5564, Note, InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 32926466568442
 
2017-05-24  4:54:04, 5128, Note, InnoDB: Dumping buffer pool(s) not yet started
 
2017-05-24  4:54:04, 5564, Note, Plugin 'FEEDBACK' is disabled.
 
2017-05-24  4:54:04, 5564, Note, Server socket created on IP: '::'.
 
2017-05-24  4:54:04, 5564, Warning, 'user' entry 'root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:54:04, 5564, Warning, 'proxies_priv' entry '@% root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:54:04, 5564, Note, C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
 
, , , Version: '10.1.23-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-24  4:54:04, 336, ERROR, mysqld.exe: Table '.\blogs\wp_wc_users_voted' is marked as crashed and should be repaired
 
2017-05-24  4:54:04, 336, Warning, Checking table:   '.\blogs\wp_wc_users_voted'
 
2017-05-24 4:54:05, , [ERROR], mysqld got exception 0xe06d7363 ;
 
, , , 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.1.23-MariaDB
 
, , , key_buffer_size=134217728
 
, , , read_buffer_size=131072
 
, , , max_used_connections=72
 
, , , max_threads=1001
 
, , , thread_count=69
 
, , , It is possible that mysqld could use up to
 
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
, , , KERNELBASE.dll!RaiseException()
 
, , , mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
, , , mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
, , , mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
, , , mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
, , , mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
, , , mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
, , , mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
, , , mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
, , , KERNEL32.DLL!BaseThreadInitThunk()
 
, , , ntdll.dll!RtlUserThreadStart()
 
, , , 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.
 
2017-05-24  4:55:10, 6976, Note, InnoDB: Using mutexes to ref count buffer pool pages
 
2017-05-24  4:55:10, 6976, Note, InnoDB: The InnoDB memory heap is disabled
 
2017-05-24  4:55:10, 6976, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-24  4:55:10, 6976, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
 
2017-05-24  4:55:10, 6976, Note, InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-24  4:55:10, 6976, Note, InnoDB: Using generic crc32 instructions
 
2017-05-24  4:55:10, 6976, Note, InnoDB: Initializing buffer pool, size = 80.0G
 
2017-05-24  4:55:13, 6976, Note, InnoDB: Completed initialization of buffer pool
 
2017-05-24  4:55:14, 6976, Note, InnoDB: Highest supported file format is Barracuda.
 
2017-05-24  4:55:14, 6976, Note, InnoDB: Starting crash recovery from checkpoint LSN=32926466581768
 
2017-05-24  4:55:15, 6976, Note, InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
2017-05-24  4:55:15, 6976, Note, InnoDB: Starting final batch to recover 421 pages from redo log
 
2017-05-24  4:55:18, 6976, Note, InnoDB: 128 rollback segment(s) are active.
 
2017-05-24  4:55:18, 6976, Note, InnoDB: Waiting for purge to start
 
2017-05-24  4:55:18, 6976, Note, InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 32926467443843
 
2017-05-24  4:55:18, 5560, Note, InnoDB: Dumping buffer pool(s) not yet started
 
2017-05-24  4:55:18, 6976, Note, Plugin 'FEEDBACK' is disabled.
 
2017-05-24  4:55:18, 6976, Note, Server socket created on IP: '::'.
 
2017-05-24  4:55:18, 6976, Warning, 'user' entry 'root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:55:18, 6976, Warning, 'proxies_priv' entry '@% root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:55:18, 6976, Note, C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
 
, , , Version: '10.1.23-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-24 4:55:23, , [ERROR], mysqld got exception 0xe06d7363 ;
 
, , , 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.1.23-MariaDB
 
, , , key_buffer_size=134217728
 
, , , read_buffer_size=131072
 
, , , max_used_connections=80
 
, , , max_threads=1001
 
, , , thread_count=80
 
, , , It is possible that mysqld could use up to
 
, , , key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2489266 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...
 
, , , KERNELBASE.dll!RaiseException()
 
, , , mysqld.exe!_CxxThrowException()[throw.cpp:136]
 
, , , mysqld.exe!std::_Xout_of_range()[xthrow.cpp:25]
 
, , , mysqld.exe!dict_stats_analyze_index_for_n_prefix()[dict0stats.cc:1763]
 
, , , mysqld.exe!dict_stats_analyze_index()[dict0stats.cc:2092]
 
, , , mysqld.exe!dict_stats_update_persistent()[dict0stats.cc:2295]
 
, , , mysqld.exe!dict_stats_update()[dict0stats.cc:3298]
 
, , , mysqld.exe!dict_stats_process_entry_from_recalc_pool()[dict0stats_bg.cc:458]
 
, , , mysqld.exe!dict_stats_thread()[dict0stats_bg.cc:551]
 
, , , KERNEL32.DLL!BaseThreadInitThunk()
 
, , , ntdll.dll!RtlUserThreadStart()
 
, , , 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.
 
2017-05-24  4:56:27, 7136, Note, InnoDB: Using mutexes to ref count buffer pool pages
 
2017-05-24  4:56:27, 7136, Note, InnoDB: The InnoDB memory heap is disabled
 
2017-05-24  4:56:27, 7136, Note, InnoDB: Mutexes and rw_locks use Windows interlocked functions
 
2017-05-24  4:56:27, 7136, Note, InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
 
2017-05-24  4:56:27, 7136, Note, InnoDB: Compressed tables use zlib 1.2.3
 
2017-05-24  4:56:27, 7136, Note, InnoDB: Using generic crc32 instructions
 
2017-05-24  4:56:27, 7136, Note, InnoDB: Initializing buffer pool, size = 80.0G
 
2017-05-24  4:56:30, 7136, Note, InnoDB: Completed initialization of buffer pool
 
2017-05-24  4:56:30, 7136, Note, InnoDB: Highest supported file format is Barracuda.
 
2017-05-24  4:56:30, 7136, Note, InnoDB: Starting crash recovery from checkpoint LSN=32926467454025
 
2017-05-24  4:56:32, 7136, Note, InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
 
2017-05-24  4:56:32, 7136, Note, InnoDB: Starting final batch to recover 227 pages from redo log
 
2017-05-24  4:56:34, 7136, Note, InnoDB: 128 rollback segment(s) are active.
 
2017-05-24  4:56:34, 7136, Note, InnoDB: Waiting for purge to start
 
2017-05-24  4:56:35, 7136, Note, InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 32926468298899
 
2017-05-24  4:56:35, 6768, Note, InnoDB: Dumping buffer pool(s) not yet started
 
2017-05-24  4:56:35, 7136, Note, Plugin 'FEEDBACK' is disabled.
 
2017-05-24  4:56:35, 7136, Note, Server socket created on IP: '::'.
 
2017-05-24  4:56:35, 7136, Warning, 'user' entry 'root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:56:35, 7136, Warning, 'proxies_priv' entry '@% root@696159-db4' ignored in --skip-name-resolve mode.
 
2017-05-24  4:56:35, 7136, Note, C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
 
, , , Version: '10.1.23-MariaDB'  socket: ''  port: 3306  mariadb.org binary distribution
 
2017-05-24  4:56:55, 4496, ERROR, mysqld.exe: Table '.\ottoneu_leagues\ownership_percentages' is marked as crashed and should be repaired
 
2017-05-24  4:56:55, 4496, Warning, Checking table:   '.\ottoneu_leagues\ownership_percentages'
 
2017-05-24  4:56:57, 5644, ERROR, mysqld.exe: Table '.\blogs\wp_wc_users_voted' is marked as crashed and should be repaired
 
2017-05-24  4:56:57, 5644, Warning, Checking table:   '.\blogs\wp_wc_users_voted'
 
2017-05-24  4:56:57, 4496, ERROR, mysqld.exe: Table '.\ottoneu_football\football_transactions' is marked as crashed and should be repaired
 
2017-05-24  4:56:57, 4496, Warning, Checking table:   '.\ottoneu_football\football_transactions'
 
2017-05-24  4:57:02, 4064, ERROR, mysqld.exe: Table '.\ottoneu_leagues\team_loans' is marked as crashed and should be repaired
 
2017-05-24  4:57:02, 4064, Warning, Checking table:   '.\ottoneu_leagues\team_loans'
 
2017-05-24  4:57:02, 7128, ERROR, mysqld.exe: Table '.\ottoneu_leagues\league_messages' is marked as crashed and should be repaired
 
2017-05-24  4:57:02, 7128, Warning, Checking table:   '.\ottoneu_leagues\league_messages'
 
2017-05-24  4:57:02, 5644, ERROR, mysqld.exe: Table '.\ottoneu_leagues\team_messages' is marked as crashed and should be repaired
 
2017-05-24  4:57:02, 5644, Warning, Checking table:   '.\ottoneu_leagues\team_messages'
 
2017-05-24  4:59:59, 5284, ERROR, mysqld.exe: Table '.\ottoneu_leagues\last_message_notification' is marked as crashed and should be repaired
 
2017-05-24  4:59:59, 5284, Warning, Checking table:   '.\ottoneu_leagues\last_message_notification'
 
2017-05-24  5:00:12, 6896, ERROR, mysqld.exe: Table '.\users\graph_static_stats' is marked as crashed and should be repaired
 
2017-05-24  5:00:12, 7144, ERROR, mysqld.exe: Table '.\users\graph_static_stats' is marked as crashed and should be repaired
 
2017-05-24  5:00:12, 7144, Warning, Checking table:   '.\users\graph_static_stats'
 
2017-05-24  5:08:29, 4480, ERROR, mysqld.exe: Table '.\ottoneu_football\football_player_meta' is marked as crashed and should be repaired
 
2017-05-24  5:08:29, 4480, Warning, Checking table:   '.\ottoneu_football\football_player_meta'
 
2017-05-24  6:18:42, 4428, ERROR, mysqld.exe: Table '.\ottoneu_leagues\organizer' is marked as crashed and should be repaired
 
2017-05-24  6:18:42, 4428, Warning, Checking table:   '.\ottoneu_leagues\organizer'

Comment by Elena Stepanova [ 2017-06-29 ]

Would you be able to provide a schema dump (only structures, no data)?
If it is big or you don't want to make it public, you can upload it to ftp.askmonty.org/private.
Thanks.

Comment by Elena Stepanova [ 2017-07-31 ]

We don't have much here, but jplindst, marko, maybe you have any thoughts on this?

Comment by Elena Stepanova [ 2017-09-07 ]

dkappelman,

As our InnoDB expert marko has found out, it is most likely a duplicate of MySQL bug which was fixed here:

commit 29acdaaaeef9afe32b42785f1da3d79d56ed7e59
 
Author: Thirunarayanan Balathandayuthapani <thirunarayanan.balathandayuth@oracle.com>
 
Date:   Wed Feb 8 12:00:52 2017 +0530
 
 
 
    Bug #24585978       INNODB: ASSERTION TOTAL_RECS > 0 FAILURE
 
                            IN FILE DICT0STATS.CC

This bugfix should be in versions 10.0.31, 10.1.24, 10.2.7, 10.3.1. You have 10.1.23, so please try to upgrade to the latest 10.1 and see if it helps.

Generated at Thu Feb 08 08:01:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.