[ERROR] InnoDB: Operating system ERROR number 995 in a file operation.
The 2018-07-31 T03:48:42. 168717 z 0 [ERROR] InnoDB: The ERROR means that The I/O operation has had aborted because of either a thread exit or an application request. Retry attempt is made.
The 2018-07-31 11:48:42 0 x150c InnoDB: an Assertion failure thread in 5388 in the file fil0fil. Cc line 5789
InnoDB: Failing an assertion: err==DB_SUCCESS
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated an assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB in tablespace. Both Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:48:42 UTC - mysqld got exception 0 x80000003;
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 under 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
The collection process took fail.
Key_buffer_size=8388608
Read_buffer_size=65536
Max_used_connections=103
Max_threads=151
Thread_count=91
Connection_count=91
It is possible that mysqld could use one
Key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads=58345 K bytes of memory
Hope that 's ok. If not, decrease some variables in the equation.
Thread pointer: 0 x0
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...
13 f815ea2 mysqld. Exe! My_errno ()
13 fbb9919 mysqld. Exe! My_wildcmp_mb ()
13 fbb8810 mysqld. Exe! My_wildcmp_mb ()
13 f915ac8 mysqld. Exe! ? Reserve @? $vector @ EV? @ STD @ @ @ $allocator @ E STD @ @ QEAAX_K @ Z ()
13 f93c49a mysqld. Exe! ? Reserve @? $vector @ EV? @ STD @ @ @ $allocator @ E STD @ @ QEAAX_K @ Z ()
13 f8d4e94 mysqld. Exe! ? Reserve @? $vector @ EV? @ STD @ @ @ $allocator @ E STD @ @ QEAAX_K @ Z ()
7794652 d kernel32. DLL! BaseThreadInitThunk ()
77 cbc521 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.
The 2018-07-31 T04:59:28. 511775 z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Do use - explicit_defaults_for_timestamp server option (see documentation for more details).
The 2018-07-31 T04:59:28. 511775 z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO SQL modes should be 2 with strict mode. They will be merged with strict mode in a future release.
[Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO SQL modes should be 2 with strict mode. They will be merged with strict mode in a future release.
CodePudding user response:
Like a Mysql bug triggered, upgrade the new versionCodePudding user response:
From the point of information, may be a BUG, file corruption or hardware failure, unable to locate