V
V
Viktor Volkov2018-07-19 08:50:42
MySQL
Viktor Volkov, 2018-07-19 08:50:42

Open Server does not start "Could not start MySQL-5.6", what should I do?

5b50265d86951343906828.png
on the photo is a screenshot of the logs, I tried to turn this
"There was an error while the database was running or the program was simply closed incorrectly. Try Advanced -> Configurations -> My-SQL (which one you have running) -> at the very bottom write "innodb_force_recovery = 3" and restart OpenServer."
but didn't help. Tell me what to do?? this problem is out of place at all ... deadlines are burning, I can’t do anything .... (((

Answer the question

In order to leave comments, you need to log in

6 answer(s)
R
Romusk Sidorenko, 2019-08-28
@Nice_Day

Try changing the Windows language to English, maybe it's an encoding problem. Control Panel - Regional Standards - Format (change to English or Windows interface language) - Advanced tab - Language of programs that do not support Unicode - English (Uncheck the Beta version (if any)). Helped me.

O
OnYourLips, 2018-07-19
@OnYourLips

Tell me what to do??
Find the logs and look for the error in them.

V
Viktor Volkov, 2018-07-19
@VGVolkov

help someone ... they will hang me nafig ... on Saturday to hand over work ... (((

Z
zumgluck, 2018-11-30
@zumgluck

I have the same problem, did you find the answer? thx in advance

M
mrmelhay, 2020-08-02
@mrmelhay

Deleted ib_logfile0 and ib_logfile1 files from c:\ospanel\userdata\MySQL-5.7-x64
Instead of MySQL-5.7-x64 is your muscle version.
It worked for me.

D
Dmitry, 2022-04-12
@good_br

The following helped me find the error and fix it:
1. Turn on the debug mode in Openserve (Settings -> Server -> debug mode)
2. Start the server
3. Look at the errors
In my case, there were the following:

d:\openserver\modules\database\MySQL-5.5>"d:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe" --defaults-file="d:\openserver\modules\database\MySQL-5.5\my.ini" --user=root --standalone --console
""d:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe"" не является внутренней или внешней
командой, исполняемой программой или пакетным файлом.

It turned out that the mysqld.exe module weighed 0 bytes, that is, it was simply empty (I don’t know how and where it disappeared, it used to be), so reinstalling this module helped solve the problem.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question