blocks|key|4431800|text|在通过mysqld+--install安装之后。试试这个mysqld+--initialize。我们遇到了同样的问题，但现在它起作用了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4431801|entityMap^0|3|G|S|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

After installing it by <code>mysqld --install</code>. Try this <code>mysqld --initialize</code>. We got the same problem but it's now working.

blocks|key|4431556|text|在我的例子中，我尝试打开DOS提示符，转到MySQL+bin\目录，然后发出以下命令：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4431557|mysqld+--defaults-file="C:\Program+Files\MySQL\MySQL+Server+5.0\my.ini"+--standalone+--console|code-block|syntax|javascript|4431558|它显示我缺少"C:\Program+Files\MySQL\MySQL+Server+5.0\Uploads"文件夹；我构建了一个文件夹并解决了问题。|4431559|entityMap^0|R|4|0|0|6|1D|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

In my case, I tried to open a DOS prompt and
go to the MySQL <code>bin\</code> directory and issue the below command:

<pre><code>mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" --standalone --console
</code></pre>

And it shows me I was missing the <code>"C:\Program Files\MySQL\MySQL Server 5.0\Uploads"</code> folder; I built one and problem solved.

blocks|key|4431903|text|在我的例子中，mysqld的启动和停止都没有错误消息。我需要使用“以管理员身份运行”打开命令提示符，然后运行mysqld。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431904|我这样做只是为了暂时的开发。在任何情况下，我都不建议以管理员身份运行MySQL。|4431905|这是上述故障排除之后的最后一步。|4431906|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In my case, mysqld was starting and stopping with no error message. I needed to open command prompt using "Run as Administrator", and then run mysqld.

I am only doing this for temporary development. I would not recommend running MySQL as an administrator in any case.

This was the final step after the above troubleshooting.

blocks|key|4431928|text|mysqld+--初始化|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431929|在install命令之后运行上面的命令。然后尝试启动该服务--这应该是可行的。|4431930|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

mysqld --initialize

Run the above after the install command.
Then try to start the service - that should work.

blocks|key|4431703|text|搜索services.msc并查找正在运行的服务，如果已经运行的mysql服务不是您想要运行的服务(可以是xampp或wamp)，或者使用与mysql相同的端口的另一个服务(例如Skype)，则停止该服务，以便您可以运行mysql服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431704|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Search for services.msc and look up through your services that are running if there is a mysql service running already other than the one you want to run (it could be xampp or wamp) or another service (for example Skype) using the same port as mysql and stop the service so you can run your mysql service.

blocks|key|4431994|text|在我的数据库运行良好很长一段时间后，我遇到了这个问题。事实证明这是一些数据损坏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431995|在错误日志中，我有：|4431996|2017-02-07T10:11:42.270567Z+0+[ERROR]+InnoDB:+Ignoring+the+redo+log+due+to+missing+MLOG_CHECKPOINT+between+the+checkpoint+44002250712+and+the+end+44002250240.
2017-02-07T10:11:42.270606Z+0+[ERROR]+InnoDB:+Plugin+initialization+aborted+with+error+Generic+error
2017-02-07T10:11:42.577436Z+0+[ERROR]+Plugin+'InnoDB'+init+function+returned+error.
2017-02-07T10:11:42.577470Z+0+[ERROR]+Plugin+'InnoDB'+registration+as+a+STORAGE+ENGINE+failed.
2017-02-07T10:11:42.577484Z+0+[ERROR]+Failed+to+initialize+plugins.
2017-02-07T10:11:42.577488Z+0+[ERROR]+Aborting|code-block|syntax|javascript|4431997|然后我不得不删除这两个ib_logfile*文件，然后它又重新启动了。|4431998|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had this issue after my database was working fine for long time. It turned out it was some data corruption.

In the error log I had:

<pre><code>2017-02-07T10:11:42.270567Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 44002250712 and the end 44002250240.
2017-02-07T10:11:42.270606Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2017-02-07T10:11:42.577436Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2017-02-07T10:11:42.577470Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-02-07T10:11:42.577484Z 0 [ERROR] Failed to initialize plugins.
2017-02-07T10:11:42.577488Z 0 [ERROR] Aborting
</code></pre>

Then I had to delete the 2 ib_logfile* files, and it restarted again.

blocks|key|4431770|text|如果使用版本8并编辑my.ini，我发现记事本在my.ini文件的开头放置了3个十六进制字符。EF、BB、BF。在十六进制编辑器中删除文件开头的3个字符可以解决此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431771|在版本8中，它们意外地将Unicode字符放入ini文件中。这会导致记事本使用字节顺序标记字符保存文件。|4431772|文件中的以下行是罪魁祸首"The+line+#+range+from+1+to+2%5E32−1.“唯一”意味着每个ID必须不同。“包含3个Unicode字符。这会导致记事本将字节顺序标记附加到文本文件。|4431773|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If using version 8 and you edit the my.ini I found that Notepad is putting 3 hex characters at the beginning of the my.ini file. EF BB BF. Deleting the 3 characters from the beginning of the file in a hex editor fixes the problem.

In version 8 they are accidentally putting Unicode characters in the ini file. This is causing Notepad to save the file with Byte order mark characters.

The following line in the file is the culprit "The line # range from 1 to 2^32 − 1. “Unique” means that each ID must be different." has 3 Unicode characters. This is causing notepad to append the byte order mark to the text file.

blocks|key|4432069|text|这个错误发生在我的案例中，当secure-file-priv指向不存在的文件夹时，请确保它存在并且可读。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432070|My.ini中的代码行示例：secure-file-priv="D:/MySQL/uploads"|offset|length|style|CODE|4432071|entityMap^0|0|E|Z|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

This error happened in my case when secure-file-priv was pointing to unexistent folder, make sure it exists and readable.

The line of code example in my.ini:
<code>secure-file-priv="D:/MySQL/uploads"</code>

blocks|key|4431823|text|如果已将数据目录(my.ini中数据库根目录的路径)更改为外部硬盘，请确保硬盘已连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4431824|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have changed data directory (the path to the database root in my.ini) to an external hard drive, make sure that the hard drive is connected.

blocks|key|4431862|text|您也可能意外地在my.ini文件中添加了一些错误的文本。确保文件开头没有添加无效字符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4431863|entityMap^0|8|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You also might have accidentally added some wrong text in <code>my.ini</code> file. Make sure no invalid character is added at the beginning of the file.

blocks|key|4431956|text|我什么都不能用，但后来我检查了here。我运行了命令qc+sc+mysql57并从其中复制了BINARY_PATH_NAME的值。之后，我检查了this，并在my.ini文件中将lower_case_table_names的值从0改为2。然后在命令提示符下，我运行了这个命令-+<<+BINARY_PATH_NAME+>>+--install-manual。在那之后，我启动了MySQL57服务，它起作用了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4431957|entityMap|0|LINK|mutability|MUTABLE|url|https://dba.stackexchange.com/questions/121936/not-able-to-start-mysqld-as-windows-service-as-well-as-from-command-line-in-wind|1|https://stackoverflow.com/questions/52728319/cant-set-lower-case-table-names-in-mysql-8-x-on-windows-10?rq=1^0|Q|D|1A|G|27|6|2H|M|3V|13|F|4|0|20|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]|$9|13|A|14|1|15]]|E|$]]|$1|F|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

Nothing was working for me but then I checked <a href="https://dba.stackexchange.com/questions/121936/not-able-to-start-mysqld-as-windows-service-as-well-as-from-command-line-in-wind">here</a>. I ran that command <code>qc sc mysql57</code> and copied the value of <code>BINARY_PATH_NAME</code> from it. After that I checked <a href="https://stackoverflow.com/questions/52728319/cant-set-lower-case-table-names-in-mysql-8-x-on-windows-10?rq=1">this</a> and changed the value of <code>lower_case_table_names</code> from 0 to 2 in <code>my.ini</code> file. Then in the command prompt, I ran this command - <code>&lt;&lt; BINARY_PATH_NAME &gt;&gt; --install-manual</code>. After that, I started the MySQL57 service and it worked.

blocks|key|4432054|text|同样的问题也发生在我身上，什么都不起作用。我首先通过命令删除了服务(在我的例子中是MySQL80和MySQL)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432055|sc+delete+MySQL80
sc+delete+MySql|code-block|syntax|javascript|4432056|然后重新安装了MySQL。我的是MySQL+8.0。然后一切都恢复正常了。|4432057|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The same problem happened with me also, nothing worked... I first deleted the service (in my case MySQL80 and MySQL) by command:

<pre><code>sc delete MySQL80
sc delete MySql
</code></pre>

and then reinstalled MySQL. Mine was MySQL 8.0. And then everything was back to normal.

blocks|key|4432337|text|从"C:\ProgramData\MySQL\MySQL+Server5.7\Data“中删除或重命名以下2个文件:+ib_logfile0+ib_logfile1|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432338|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Delete or rename the 2 following files from "C:\ProgramData\MySQL\MySQL Server 5.7\Data":
ib_logfile0
ib_logfile1

blocks|key|4432387|text|当我安装MySQL+8.x，编辑my.ini文件中的max_allowed_packet，然后在Windows10机器上重新启动MySQL时，我看到了这个错误。为了避免这个问题，我的建议是在十六进制编辑器(类似于Frhed)中编辑my.ini文件。请勿使用记事本。它会改变.ini文件的十六进制布局。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432388|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I see this error when I install MySQL 8.x, edit the max_allowed_packet in the my.ini file, and then restart mysql on a Windows 10 machine. My recommendation, to avoid this issue, is to edit the my.ini file in a hex editor (something like Frhed). DO NOT USE NOTEPAD. It does something to the hex layout of the .ini file.

blocks|key|4432186|text|本地计算机上的MySQL服务已启动，然后停止|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432187|当您在C:\ProgramData\MySQL\MySQL+Server+8.0\my.ini中不正确地修改my.ini时，会出现此错误。|4432188|您可以搜索my.ini原始配置或检查您的配置，以确保一切正常|4432189|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

the MySQL service on local computer started and then stopped

This Error happen when you modified my.ini in C:\ProgramData\MySQL\MySQL Server 8.0\my.ini not correct.

You can search my.ini original configuration or checking yours to make sure everything is OK

blocks|key|4432518|text|这个问题是非常复杂的，并且依赖于MySQL+Version.My问题发生在MySQL+8.0.2上。当我在记事本上配置了my.ini文件并将其保存后，我接受了@jhersey29解决方案https://stackoverflow.com/a/55519014/1764354，但方法上有一点不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4432519|我的解决方案是通过WorkBench应用程序上的选项文件恢复my.ini文件和编辑配置值。workBench+Menu+Example|4432520|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/55519014/1764354|1|https://i.stack.imgur.com/3EdKH.png^0|2L|18|0|0|19|M|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

This problem is so complicated and depend on MySQL Version.My problem was happened on MySQL 8.0.2. When I've config my.ini file on notepad and save it.I soleved following @jhersey29 solution <a href="https://stackoverflow.com/a/55519014/1764354">https://stackoverflow.com/a/55519014/1764354</a> but little different approch.

my solution is restore my.ini file and edit config value via Option files on WorkBench Application.
<a href="https://i.stack.imgur.com/3EdKH.png" rel="nofollow noreferrer">workBench Menu Example</a>

blocks|key|4432546|text|如果您在Windows10上安装WAMP64时遇到此问题，请检查MySQL文件夹中的数据文件夹是否丢失。我的WAMP+3.2.3版本安装无法创建这样的文件夹。所以wamp图标是橙色的(2个服务中的1个在运行)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432547|一个快速修复方法是从MySQL位置运行此命令。|4432548|C:\wamp64\bin\mysql\mysql5.7.31\bin\
mysqld+--initialize-insecure|code-block|syntax|javascript|4432549|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you came across this while installing WAMP64 on Windows 10. Check if data folder in MySQL folder is missing. My WAMP 3.2.3 version installation failed to create such a folder. So wamp icon was orange (1 of 2 services running).
A quick fix was to run this command from MySQL location.
<pre><code>C:\wamp64\bin\mysql\mysql5.7.31\bin\
mysqld --initialize-insecure
</code></pre>

blocks|key|4432589|text|上述方法都不起作用，所以删除mysql，重新安装mysql，如果any...enjoy，恢复原样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432590|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

non of the above actually works so delete mysql,reinstall mysql,restore back if any...enjoy

blocks|key|4432653|text|我收到了与问题中显示的完全相同的消息。我尝试了很多建议，但都没什么收获。我正要安装WAMP+(我在Windows上)，正准备先卸载WAMP+8.0，这时我注意到安装中包含了一个程序：'MySQL+Installer+-+Community‘，于是我尝试了一下。使用这个安装程序，我设置了一个新的连接，添加了root密码，添加了另一个用户的密码，为所有日志设置了我选择的位置，并运行了安装。结果是它现在完全起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432654|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the exact same message as displayed in the question. I have tried many suggestions with little luck. I was about to install WAMP (I'm on Windows) and was about to uninstall MySql 8.0 first, when I noticed a program included in the installation: 'MySQL Installer - Community' so I tried that. With this installer I set up a new connection, added password to root, added another user with password, set my choice of locations for all logs and ran the install.
The result was that it now totally works.

blocks|key|4432687|text|这样的问题通常是由配置错误引起的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432688|Vivek+Sethi+mentioned+20th+December+2012可以通过运行以下命令在控制台中获取日志记录：|offset|length|4432689|C:\Windows\system32>"C:\Program+Files\MySQL\MySQL+Server+5.5\bin\mysqld"+--defaults-file="C:\Program+Files\MySQL\MySQL+Server+5.5\my.ini"+--standalone+--console|code-block|syntax|javascript|4432690|在Windows10中右键单击我的服务，我识别出了--defaults-file=参数，并且通过控制台日志记录，我能够看到我的配置中的错误。在我的例子中，到datadir=和secure-file-priv=的路径是错误的。我希望其他人也可以通过能够在控制台中看到日志详细信息来获得支持。祝好运!|style|CODE|4432691|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.mysql.com/bug.php?id=67917^0|0|0|14|0|0|0|P|G|26|8|2F|H|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@$D|13|E|14|M|N]|$D|15|E|16|M|N]|$D|17|E|18|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Such a problem can very often come due to configuration errors.
<a href="https://bugs.mysql.com/bug.php?id=67917" rel="nofollow noreferrer">Vivek Sethi mentioned 20th December 2012</a> that it is possible to get logging in the console by running the following command:
<pre class="lang-sh prettyprint-override"><code>C:\Windows\system32&gt;&quot;C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld&quot; --defaults-file=&quot;C:\Program Files\MySQL\MySQL Server 5.5\my.ini&quot; --standalone --console
</code></pre>
Right-clicking on my service in Windows 10, I recognized the <code>--defaults-file=</code> parameter, and with console logging I was able to see what was wrong in my configuration. In my case the path to <code>datadir=</code> and <code>secure-file-priv=</code> was wrong. I hope others can be empowered as well by being able to see logging details in the console. Good luck!

blocks|key|4432700|text|my.ini文件应另存为(编码)+ANSI，而不是UTF8或其他文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432701|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

my.ini file should save as (Encoding) ANSI not UTF-8 or others files.

blocks|key|4432456|text|同时运行另一个mysql实例，如5.6或8|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432457|预留了80端口|4432458|请转到>>+services>>停止所有其他实例并禁用它们|4432459|在我的案例中，问题解决了，服务也启动了|4432460|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

another instance of mysql like 5.6 or 8 run at the same time
and the 80 port was reserved
please &gt; go to &gt;&gt; services&gt;&gt; stop all another instance &gt;&gt; disable them
in my case problem solved and service started as well

blocks|key|4432729|text|在使用命令mysqld+--initialize之前，请确保您的数据文件夹是完全空的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432730|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

make sure your data folder is fully empty before use command mysqld --initialize

blocks|key|4432482|text|转到"C:\ProgramData\MySQL\MySQL+Server8.0\Data[机器名].err“并检查最后几行-它应该会告诉你失败的原因。在我的例子中，它是在数据库之间复制的表空间id。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4432483|它看起来是这样的：|4432484|2021-09-12T05:19:22.815152Z+0+[Warning]+[MY-010915]+[Server]+'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.
2021-09-12T05:19:22.818357Z+0+[System]+[MY-010116]+[Server]+C:\Program+Files\MySQL\MySQL+Server+8.0\bin\mysqld.exe+(mysqld+8.0.22)+starting+as+process+30664
2021-09-12T05:19:22.866774Z+1+[System]+[MY-013576]+[InnoDB]+InnoDB+initialization+has+started.
2021-09-12T05:19:22.908983Z+1+[ERROR]+[MY-012209]+[InnoDB]+Multiple+files+found+for+the+same+tablespace+ID:
2021-09-12T05:19:22.911667Z+1+[ERROR]+[MY-012202]+[InnoDB]+Tablespace+ID:+124+=+['db1\accounts.ibd',+'db2\accounts.ibd']+
2021-09-12T05:19:22.915514Z+1+[ERROR]+[MY-012930]+[InnoDB]+Plugin+initialization+aborted+with+error+Failed,+retry+may+succeed.
2021-09-12T05:19:22.918627Z+1+[ERROR]+[MY-010334]+[Server]+Failed+to+initialize+DD+Storage+Engine
2021-09-12T05:19:22.927714Z+0+[ERROR]+[MY-010020]+[Server]+Data+Dictionary+initialization+failed.
2021-09-12T05:19:22.930912Z+0+[ERROR]+[MY-010119]+[Server]+Aborting
2021-09-12T05:19:22.934432Z+0+[System]+[MY-010910]+[Server]+C:\Program+Files\MySQL\MySQL+Server+8.0\bin\mysqld.exe:+Shutdown+complete+(mysqld+8.0.22)++MySQL+Community+Server+-+GPL.|code-block|syntax|javascript|4432485|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Go to &quot;C:\ProgramData\MySQL\MySQL Server 8.0\Data\[machine name].err&quot; and check the last rows - it should tell you why it failed. In my case it was duplicated tablespace id between databases.
It looks like this:
<pre><code>2021-09-12T05:19:22.815152Z 0 [Warning] [MY-010915] [Server] '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.
2021-09-12T05:19:22.818357Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.22) starting as process 30664
2021-09-12T05:19:22.866774Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-09-12T05:19:22.908983Z 1 [ERROR] [MY-012209] [InnoDB] Multiple files found for the same tablespace ID:
2021-09-12T05:19:22.911667Z 1 [ERROR] [MY-012202] [InnoDB] Tablespace ID: 124 = ['db1\accounts.ibd', 'db2\accounts.ibd'] 
2021-09-12T05:19:22.915514Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Failed, retry may succeed.
2021-09-12T05:19:22.918627Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2021-09-12T05:19:22.927714Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2021-09-12T05:19:22.930912Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-09-12T05:19:22.934432Z 0 [System] [MY-010910] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe: Shutdown complete (mysqld 8.0.22) MySQL Community Server - GPL.
</code></pre>

the MySQL service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

Can anyone resolve this issue? Thanks.

<img src="https://i.stack.imgur.com/IMfNZ.png" alt="">

the MySQL service on local computer started and then stopped

SQL Server

数据库

Windows

MySQL

本地计算机上的MySQL服务已启动，然后停止。如果某些服务未被其他服务或程序使用，则会自动停止。任何人都能解决这个问题吗？谢谢。​​

问本地计算机上的MySQL服务已启动，然后停止
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问本地计算机上的MySQL服务已启动，然后停止EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问本地计算机上的MySQL服务已启动，然后停止
EN