Иногда я сталкиваюсь с ошибкой MySQL, которая приводит к сбою MySQL. Из-за этого также происходит сбой сервера WAMP. Mysql версии 8.0.15
Журналы ошибок выглядят следующим образом.
2021-03-31T09:39:30.820347Z 748247 [ERROR] [MY-012646] [InnoDB] File .\company\invoice.ibd: 'aio read' returned OS error 0. Cannot continue operation
2021-03-31T09:39:30.899632Z 748247 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.
2021-03-31T09:39:31.187481Z 748249 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0buf.cc:700:srv_shutdown_state <= SRV_SHUTDOWN_FLUSH_PHASE thread 13468
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:39:31 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=536870912
read_buffer_size=2097152
max_used_connections=82
max_threads=151
thread_count=7
connection_count=6
It is possible that mysqld could use up to
536870912 + (2097152 + 2,097,152)*151 = 1144299 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x1a95dc89430
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...
2021-03-31T09:39:46.587951Z 748272 [ERROR] [MY-013183] [InnoDB] Assertion failure: log0buf.cc:700:srv_shutdown_state <= SRV_SHUTDOWN_FLUSH_PHASE thread 13228
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.
2021-03-31T10:42:08.204251Z 0 [System] [MY-010116] [Server] c:\wamp\bin\mysql\mysql8.0.15\bin\mysqld.exe (mysqld 8.0.15) starting as process 10748
2021-03-31T10:45:26.373705Z 0 [System] [MY-010931] [Server] c:\wamp\bin\mysql\mysql8.0.15\bin\mysqld.exe: ready for connections. Version: '8.0.15' socket: '' port: 3306 MySQL Community Server - GPL.
Я хочу узнать, почему это происходит, и возможные способы предотвращения этого. Спасибо, ура.!
Обратите внимание, что MySQL 8.0.15 старше двух лет. Вам следует перейти на самую последнюю версию, чтобы получить наибольшее количество исправлений для потенциальных сбоев.
Вы, очевидно, экспериментировали с параметрами mysql, поскольку ни один из них не соответствует состоянию, как при установке WAMPServer, отмените свои изменения
Этот вопрос не имеет ничего общего с программированием, поэтому здесь, на SO, он не по теме. Сайты-партнеры по dba и serverfault предлагают помощь в таких вопросах, как этот.