[::: More Error ::::]
InnoDB: End of page dump
2019-06-26 10:47:42 d40 InnoDB: uncompressed page, stored checksum in field1 2208127222, calculated checksums for field1: crc32 2194063152, innodb 2208127222, none 3735928559, stored checksum in field2 2319515395, calculated checksums for field2: crc32 2194063152, innodb 1671498457, none 3735928559, page LSN 0 21247553, low 4 bytes of LSN at page end 21209856, page number (if stored to page already) 402, space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: page type 2 meaning UNDO LOG
InnoDB: Page may be an update undo log page
2019-06-26 10:47:42 3392 [ERROR] InnoDB: It is also possible that your operatingsystem has corrupted its own file cache.
2019-06-26 10:47:42 3392 [ERROR] InnoDB: and rebooting your computer removes the error.
2019-06-26 10:47:42 3392 [ERROR] InnoDB: If the corrupt page is an index page you can also try to
2019-06-26 10:47:42 3392 [ERROR] InnoDB: fix the corruption by dumping, dropping, and reimporting
2019-06-26 10:47:42 3392 [ERROR] InnoDB: the corrupt table. You can use CHECK
2019-06-26 10:47:42 3392 [ERROR] InnoDB: TABLE to scan your table for corruption.
2019-06-26 10:47:42 3392 [ERROR] InnoDB: See also http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html about forcing recovery.
2019-06-26 10:47:42 3392 [ERROR] InnoDB: Ending processing because of a corrupt database page.
2019-06-26 10:47:42 d40 InnoDB: Assertion failure in thread 3392 in file buf0buf.cc line 4829
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190626 10:47:42 [ERROR] mysqld got exception 0x80000003 ;
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.22-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!my_wildcmp_mb_bin()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?save_in_result_field@Item@@UAEX_N@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!my_wildcmp_mb_bin()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.
