Description:
when windows system not normarl close, then mysql not work now.
i have try setup innodb_force_recovery, but it still cant start.
show log is :
mysql 8.0.15
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.
2019-04-26T08:59:43.952094Z 20 [ERROR] [MY-013183] [InnoDB] Assertion failure: fut0lst.ic:86:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 14200
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2019-04-26T09:00:29.477055Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-26T09:00:29.478984Z 0 [System] [MY-010116] [Server] E:\MYSQL80\bin\mysqld.exe (mysqld 8.0.15) starting as process 10496
2019-04-26T09:00:36.447079Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-04-26T09:00:36.455666Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-04-26T09:00:37.510174Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-04-26T09:00:37.521698Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'host'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521711Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'ipv6'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521721Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'xiaoyu1'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521730Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'host'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521738Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'ipv6'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521747Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'piwik'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521768Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'wmail'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521776Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'xiaoyu1'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521784Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'yessan'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.540000Z 0 [System] [MY-010931] [Server] E:\MYSQL80\bin\mysqld.exe: ready for connections. Version: '8.0.15' socket: '' port: 3306 MySQL Community Server - GPL.
2019-04-26T09:00:37.686686Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2019-04-26T09:00:37.949210Z 8 [ERROR] [MY-013183] [InnoDB] Assertion failure: lob0pages.h:45:type == FIL_PAGE_TYPE_LOB_DATA thread 12300
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:00:37 UTC - 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.
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=8388608
read_buffer_size=65536
max_used_connections=1
max_threads=151
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58027 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1cc114814a0
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...
7ff75f7ec842 mysqld.exe!my_sigabrt_handler()[my_thr_init.cc:372]
7fff34b3e19d ucrtbase.dll!raise()
7fff34b3f071 ucrtbase.dll!abort()
7ff75f9d7b5d mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:92]
7ff75fb1c13b mysqld.exe!lob::read()[lob0impl.cc:1158]
7ff75fa80278 mysqld.exe!lob::btr_copy_externally_stored_field_func()[lob0lob.cc:970]
7ff75fa99437 mysqld.exe!row_sel_store_mysql_field_func()[row0sel.cc:2817]
7ff75fa99a30 mysqld.exe!row_sel_store_mysql_rec()[row0sel.cc:3043]
7ff75fa944c7 mysqld.exe!row_search_mvcc()[row0sel.cc:5541]
7ff75f8bad84 mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9202]
7ff75eaa702d mysqld.exe!handler::index_read_idx_map()[handler.cc:7272]
7ff75eaa256c mysqld.exe!handler::ha_index_read_idx_map()[handler.cc:3125]
7ff75ee51754 mysqld.exe!read_const()[sql_executor.cc:2266]
7ff75ee4f9dd mysqld.exe!join_read_const_table()[sql_executor.cc:2145]
7ff75ecc704f mysqld.exe!JOIN::extract_func_dependent_tables()[sql_optimizer.cc:5226]
7ff75ecc98d5 mysqld.exe!JOIN::make_join_plan()[sql_optimizer.cc:4746]
7ff75eccb48e mysqld.exe!JOIN::optimize()[sql_optimizer.cc:426]
7ff75ed17416 mysqld.exe!SELECT_LEX::optimize()[sql_select.cc:1518]
7ff75ed1407f mysqld.exe!Sql_cmd_dml::execute_inner()[sql_select.cc:684]
7ff75ed13e60 mysqld.exe!Sql_cmd_dml::execute()[sql_select.cc:596]
7ff75ec33a2f mysqld.exe!mysql_execute_command()[sql_parse.cc:4470]
7ff75ec344e7 mysqld.exe!mysql_parse()[sql_parse.cc:5107]
7ff75ec2e034 mysqld.exe!dispatch_command()[sql_parse.cc:1720]
7ff75ec2efc7 mysqld.exe!do_command()[sql_parse.cc:1264]
7ff75ea977a8 mysqld.exe!handle_connection()[connection_handler_per_thread.cc:305]
7ff75fb81967 mysqld.exe!pfs_spawn_thread()[pfs.cc:2839]
7ff75f7ec7dc mysqld.exe!win_thread_start()[my_thread.cc:52]
7fff34af03ba ucrtbase.dll!_o_exp()
7fff357c81f4 KERNEL32.DLL!BaseThreadInitThunk()
7fff37dca251 ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1cc14d43db8): SELECT bytes from ofRRDs where id = 'conversations'
Connection ID (thread ID): 8
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.
How to repeat:
mysql 8.0.16 log
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.
2019-04-26T08:59:43.952094Z 20 [ERROR] [MY-013183] [InnoDB] Assertion failure: fut0lst.ic:86:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA thread 14200
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2019-04-26T09:00:29.477055Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-26T09:00:29.478984Z 0 [System] [MY-010116] [Server] E:\MYSQL80\bin\mysqld.exe (mysqld 8.0.15) starting as process 10496
2019-04-26T09:00:36.447079Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-04-26T09:00:36.455666Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-04-26T09:00:37.510174Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-04-26T09:00:37.521698Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'host'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521711Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'ipv6'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521721Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'xiaoyu1'@'localhost' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521730Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'host'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521738Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'ipv6'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521747Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'piwik'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521768Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'wmail'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521776Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'xiaoyu1'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.521784Z 0 [Warning] [MY-010312] [Server] The plugin 'mysql_old_password' used to authenticate user 'yessan'@'%' is not loaded. Nobody can currently login using this account.
2019-04-26T09:00:37.540000Z 0 [System] [MY-010931] [Server] E:\MYSQL80\bin\mysqld.exe: ready for connections. Version: '8.0.15' socket: '' port: 3306 MySQL Community Server - GPL.
2019-04-26T09:00:37.686686Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2019-04-26T09:00:37.949210Z 8 [ERROR] [MY-013183] [InnoDB] Assertion failure: lob0pages.h:45:type == FIL_PAGE_TYPE_LOB_DATA thread 12300
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:00:37 UTC - 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.
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=8388608
read_buffer_size=65536
max_used_connections=1
max_threads=151
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58027 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1cc114814a0
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...
7ff75f7ec842 mysqld.exe!my_sigabrt_handler()[my_thr_init.cc:372]
7fff34b3e19d ucrtbase.dll!raise()
7fff34b3f071 ucrtbase.dll!abort()
7ff75f9d7b5d mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:92]
7ff75fb1c13b mysqld.exe!lob::read()[lob0impl.cc:1158]
7ff75fa80278 mysqld.exe!lob::btr_copy_externally_stored_field_func()[lob0lob.cc:970]
7ff75fa99437 mysqld.exe!row_sel_store_mysql_field_func()[row0sel.cc:2817]
7ff75fa99a30 mysqld.exe!row_sel_store_mysql_rec()[row0sel.cc:3043]
7ff75fa944c7 mysqld.exe!row_search_mvcc()[row0sel.cc:5541]
7ff75f8bad84 mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:9202]
7ff75eaa702d mysqld.exe!handler::index_read_idx_map()[handler.cc:7272]
7ff75eaa256c mysqld.exe!handler::ha_index_read_idx_map()[handler.cc:3125]
7ff75ee51754 mysqld.exe!read_const()[sql_executor.cc:2266]
7ff75ee4f9dd mysqld.exe!join_read_const_table()[sql_executor.cc:2145]
7ff75ecc704f mysqld.exe!JOIN::extract_func_dependent_tables()[sql_optimizer.cc:5226]
7ff75ecc98d5 mysqld.exe!JOIN::make_join_plan()[sql_optimizer.cc:4746]
7ff75eccb48e mysqld.exe!JOIN::optimize()[sql_optimizer.cc:426]
7ff75ed17416 mysqld.exe!SELECT_LEX::optimize()[sql_select.cc:1518]
7ff75ed1407f mysqld.exe!Sql_cmd_dml::execute_inner()[sql_select.cc:684]
7ff75ed13e60 mysqld.exe!Sql_cmd_dml::execute()[sql_select.cc:596]
7ff75ec33a2f mysqld.exe!mysql_execute_command()[sql_parse.cc:4470]
7ff75ec344e7 mysqld.exe!mysql_parse()[sql_parse.cc:5107]
7ff75ec2e034 mysqld.exe!dispatch_command()[sql_parse.cc:1720]
7ff75ec2efc7 mysqld.exe!do_command()[sql_parse.cc:1264]
7ff75ea977a8 mysqld.exe!handle_connection()[connection_handler_per_thread.cc:305]
7ff75fb81967 mysqld.exe!pfs_spawn_thread()[pfs.cc:2839]
7ff75f7ec7dc mysqld.exe!win_thread_start()[my_thread.cc:52]
7fff34af03ba ucrtbase.dll!_o_exp()
7fff357c81f4 KERNEL32.DLL!BaseThreadInitThunk()
7fff37dca251 ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1cc14d43db8): SELECT bytes from ofRRDs where id = 'conversations'
Connection ID (thread ID): 8
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.
2019-04-26T09:19:32.704709Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2019-04-26T09:19:32.708425Z 0 [System] [MY-010116] [Server] E:\MYSQL80\bin\mysqld.exe (mysqld 8.0.16) starting as process 7600
2019-04-26T09:19:36.953767Z 1 [System] [MY-011090] [Server] Data dictionary upgrading from version '80014' to '80016'.
2019-04-26T09:19:43.190018Z 1 [System] [MY-013413] [Server] Data dictionary upgrade from version '80014' to '80016' completed.
2019-04-26T09:19:44.709894Z 4 [System] [MY-013381] [Server] Server upgrade from '80015' to '80016' started.
2019-04-26T09:19:47.224479Z 4 [ERROR] [MY-013178] [Server] Execution of server-side SQL statement 'EXECUTE stmt;
' failed with error code = 1091, error message = 'Can't DROP 'PRIMARY'; check that column/key exists'.
2019-04-26T09:19:47.228653Z 0 [ERROR] [MY-013380] [Server] Failed to upgrade server.
2019-04-26T09:19:47.229161Z 0 [ERROR] [MY-010119] [Server] Aborting
2019-04-26T09:19:48.757225Z 0 [System] [MY-010910] [Server] E:\MYSQL80\bin\mysqld.exe: Shutdown complete (mysqld 8.0.16) MySQL Community Server - GPL.
