MySQL Forums
Forum List  »  Install & Repo

Re: MySQL Service Will Not Start / Windows Server 2012
Posted by: Dennis St. John
Date: September 02, 2020 10:47AM


C:\Program Files\MySQL\MySQL Server 5.6\bin>mysqld.exe --console --datadir="C:\P
rogramData\MySQL\MySQL Server 5.6\data"
2020-09-02 10:44:25 0 [Warning] TIMESTAMP with implicit DEFAULT value is depreca
ted. Please use --explicit_defaults_for_timestamp server option (see documentati
on for more details).
2020-09-02 10:44:25 8168 [Note] Plugin 'FEDERATED' is disabled.
2020-09-02 10:44:25 8168 [Note] InnoDB: Using atomics to ref count buffer pool p
2020-09-02 10:44:25 8168 [Note] InnoDB: The InnoDB memory heap is disabled
2020-09-02 10:44:25 8168 [Note] InnoDB: Mutexes and rw_locks use Windows interlo
cked functions
2020-09-02 10:44:25 8168 [Note] InnoDB: Memory barrier is not used
2020-09-02 10:44:25 8168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2020-09-02 10:44:25 8168 [Note] InnoDB: Not using CPU crc32 instructions
2020-09-02 10:44:25 8168 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-09-02 10:44:25 8168 [Note] InnoDB: Completed initialization of buffer pool
2020-09-02 10:44:25 8168 [Note] InnoDB: Highest supported file format is Barracu
2020-09-02 10:44:26 8168 [Note] InnoDB: Log scan progressed past the checkpoint
lsn 21072948491
2020-09-02 10:44:26 8168 [Note] InnoDB: Database was not shutdown normally!
2020-09-02 10:44:26 8168 [Note] InnoDB: Starting crash recovery.
2020-09-02 10:44:26 8168 [Note] InnoDB: Reading tablespace information from the
.ibd files...
2020-09-02 10:44:26 8168 [Note] InnoDB: Restoring possible half-written data pag
2020-09-02 10:44:26 8168 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 21072948501
2020-09-02 10:44:26 8168 [Note] InnoDB: 128 rollback segment(s) are active.
2020-09-02 10:44:26 8168 [Note] InnoDB: Waiting for purge to start
2020-09-02 10:44:26 1c94 InnoDB: Assertion failure in thread 7316 in file fsp0f line 3355
InnoDB: Failing assertion: xdes_mtr_get_bit(descr, XDES_FREE_BIT, header_page %
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
16:44:26 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.
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68083 K b
ytes 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...
7ff6ab4552e2 mysqld.exe!my_thread_name()
7ff6ab6e3c21 mysqld.exe!my_mb_ctype_mb()
7ff6ab6e9340 mysqld.exe!my_mb_ctype_mb()
7ff6ab5679cd mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4d0591 mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4d0a0a mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4d0cba mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4d2bc7 mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4a6bd2 mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ff6ab4a6e52 mysqld.exe!?my_aes_create_key@@YAXPEBEIPEAEW4my_aes_opmode@@@Z()

7ffe3f301412 KERNEL32.DLL!BaseThreadInitThunk()
7ffe3f6654f4 ntdll.dll!RtlUserThreadStart()
The manual page at contains
information that should help you find out what is causing the crash.

C:\Program Files\MySQL\MySQL Server 5.6\bin>

Options: ReplyQuote

Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.