Description:
2023-12-01 09:46:31 - Starting server...
2023-12-01 09:46:31 - Server start done.
FROM STM01.err:
2023-12-01T02:46:29 0 Warning TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-12-01T02:46:29 0 Warning '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.
2023-12-01T02:46:29 0 Note D:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.29-log) starting as process 860 ...
2023-12-01T02:46:29 0 Note InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-12-01T02:46:29 0 Note InnoDB: Uses event mutexes
2023-12-01T02:46:29 0 Note InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2023-12-01T02:46:29 0 Note InnoDB: Compressed tables use zlib 1.2.11
2023-12-01T02:46:29 0 Note InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2023-12-01T02:46:29 0 Note InnoDB: Number of pools: 1
2023-12-01T02:46:29 0 Note InnoDB: Not using CPU crc32 instructions
2023-12-01T02:46:29 0 Note InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2023-12-01T02:46:29 0 Note InnoDB: Completed initialization of buffer pool
2023-12-01T02:46:29 0 Note InnoDB: Highest supported file format is Barracuda.
2023-12-01T02:46:29 0 Note InnoDB: Log scan progressed past the checkpoint lsn 50921198873
2023-12-01T02:46:29 0 Note InnoDB: Doing recovery: scanned up to log sequence number 50921499330
2023-12-01T02:46:29 0 Note InnoDB: Database was not shutdown normally!
2023-12-01T02:46:29 0 Note InnoDB: Starting crash recovery.
2023-12-01T02:46:29 0 Note InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1196 row operations to undo
2023-12-01T02:46:29 0 Note InnoDB: Trx id counter is 190373120
2023-12-01T02:46:29 0 Note InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 2023-12-01 09:46:29 0x161069 InnoDB: Assertion failure in thread 5648 in file page0cur.cc line 1313
70 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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
71 02:46:29 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=62914560
read_buffer_size=65536
max_used_connections=0
max_threads=5000
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1722377 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...
72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 7ff6c78feeb2 mysqld.exe!my_errno()
7ffb5932ec9d MSVCR120.dll!raise()
7ffb59334874 MSVCR120.dll!abort()
7ff6c7a1a744 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c7b7a81c mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c7b7bf9a mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c79f8bc8 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c79f9523 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c7b1d5c9 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c7a3660f mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff6c79cdf94 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ffb84c584d4 KERNEL32.DLL!BaseThreadInitThunk()
7ffb86b9e871 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.
2023-12-01T02:46:32 0 Warning TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2023-12-01T02:46:32 0 Warning '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.
2023-12-01T02:46:32 0 Note D:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.29-log) starting as process 10364 ...
2023-12-01T02:46:32 0 Note InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-12-01T02:46:32 0 Note InnoDB: Uses event mutexes
2023-12-01T02:46:32 0 Note InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2023-12-01T02:46:32 0 Note InnoDB: Compressed tables use zlib 1.2.11
2023-12-01T02:46:32 0 Note InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB
2023-12-01T02:46:32 0 Note InnoDB: Number of pools: 1
2023-12-01T02:46:32 0 Note InnoDB: Not using CPU crc32 instructions
2023-12-01T02:46:32 0 Note InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2023-12-01T02:46:32 0 Note InnoDB: Completed initialization of buffer pool
2023-12-01T02:46:32 0 Note InnoDB: Highest supported file format is Barracuda.
2023-12-01T02:46:32 0 Note InnoDB: Log scan progressed past the checkpoint lsn 50921198873
2023-12-01T02:46:32 0 Note InnoDB: Doing recovery: scanned up to log sequence number 50921499330
2023-12-01T02:46:32 0 Note InnoDB: Database was not shutdown normally!
2023-12-01T02:46:32 0 Note InnoDB: Starting crash recovery.
2023-12-01 09:46:33 - Checking server status...
2023-12-01 09:46:33 - Trying to connect to MySQL...
2023-12-01 09:46:33 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2023-12-01 09:46:33 - Assuming server is not running
2023-12-01 09:46:36 - Checking server status...
2023-12-01 09:46:36 - Trying to connect to MySQL...
2023-12-01 09:46:36 - Can't connect to MySQL server on '127.0.0.1' (10061) (2003)
2023-12-01 09:46:36 - Assuming server is not running
How to repeat:
Current still problem can't solving
Suggested fix:
Please help to fix