Windows 10 Enterprise - MYSQL 意外关闭

时间:2023-05-09
本文介绍了Windows 10 Enterprise - MYSQL 意外关闭的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

限时送ChatGPT账号..

我已经在机器上安装了 Windows 10 Enterprise 64bit 并尝试在我的机器上安装 Apache、PHP 和 MySQL 以用于 Web 开发.简而言之,我一直遇到错误MySQL 意外关闭".我尝试在我的机器上使用 WAMP 和 XAMPP 进行安装,但仍然遇到相同的错误.Apache 连接并在 WAMP 和 XAMPP 上工作,但是我收到相同的 MySQL 错误.

I've installed Windows 10 Enterprise 64bit on machine and attempting to install Apache, PHP and MySQL on my machine to use for web development. In short I keep running into an error "MySQL shutdown unexpectedly". I've attempted to install using WAMP and XAMPP on my machine and still run into the same error. Apache connects and works on both WAMP and XAMPP however I get the same MySQL error.

到目前为止,在我所做的所有研究中,请找到我的情况和我尝试过的解决方案的概要.我认为这与 Windows 10 有关.另外,作为旁注,我在 12 英寸 MacBook 上使用训练营,因此不确定这是否会增加问题,但我不会这么认为.

So far from all the research I've done please find a synopsis of my situation and the solutions I've tried. I'm thinking this is to do with Windows 10. Also as a side note I'm using bootcamp on my MacBook 12 inch so not sure if this adding to the problem but I would not have thought so.

  1. Apache 在端口 80:433 上运行,用于 XAMPP 和 WAMP
  2. WAMP - Mysql -> 服务,启动/恢复服务为绿色.当我点击它时,什么也没有发生.我得到的 XAMP:

  1. Apache running on port 80:433 for both XAMPP and WAMP
  2. WAMP - Mysql -> service, start/resume service is green. When I click on it nothing happens. XAMP I get:

8:50:59 AM [mysql] 错误:MySQL 意外关闭.

8:50:59 AM [mysql] Error: MySQL shutdown unexpectedly.

上午 8:50:59 [mysql] 这可能是由于端口阻塞、缺少依赖项,

8:50:59 AM [mysql] This may be due to a blocked port, missing dependencies,

8:50:59 AM [mysql] 权限不当、崩溃或通过其他方法关闭.

8:50:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.

8:50:59 AM [mysql] 按日志按钮查看错误日志并检查

8:50:59 AM [mysql] Press the Logs button to view error logs and check

8:50:59 AM [mysql] Windows 事件查看器获取更多线索

8:50:59 AM [mysql] the Windows Event Viewer for more clues

8:50:59 AM [mysql] 如果您需要更多帮助,请复制并发布此内容

8:50:59 AM [mysql] If you need more help, copy and post this

8:50:59 AM [mysql] 论坛上的整个日志窗口

8:50:59 AM [mysql] entire log window on the forums

关闭windows防火墙,同样的错误

Turned off windows firewall, same errors

4.我已经检查过Skype,但它实际上没有安装在我的机器上.还检查了控制面板->查看本地服务,Skype不存在,也没有在命令提示符下运行尝试过netstat-b,但我不能查看端口 80 的任何内容.还尝试过 netstat -aon |findstr :80, only TCP 192.168.0.10:49556 23.205.116.42:80 ESTABLISHED 1884. 注意:如果端口是一个问题 Apache 不应该工作

4.I've checked for skype but it is actually not installed on my machine.Also checked control panel -> view local services, skype is not there nor running Tried netstat-b in the command prompt and I can't see anything with port 80. Also tried netstat -aon | findstr :80, only TCP 192.168.0.10:49556 23.205.116.42:80 ESTABLISHED 1884. Note: If the port was an issue Apache should not be working

  1. 我检查了控制面板 -> 查看本地服务,没有万维网发布服务.

  1. I checked the control panel -> view local services there is no World Wide Web Publishing Service.

遵循 Xamp-Mysql Shutdown 中的解决方案,其中包括删除 ib_logfile1、ib_logfile 和ibdata1.以及将 my.ini 附加到 innodb_force_recovery = 1.我得到了一个稍微不同的错误,我把它放在下面.

Followed solution in Xamp-Mysql Shutdown which included deleting ib_logfile1, ib_logfile and ibdata1. As well as appending my.ini with innodb_force_recovery = 1. I get a slightly different error which I put below.

我几乎别无选择,即将接受 MySQL 可能无法在我的 Windows 10 机器上运行的事实.但在我提供任何帮助之前,我们将不胜感激.

I'm pretty much out of options and about to give into the fact that MySQL may not work on my windows 10 machine. But before I do any help would be appreciated.

错误日志:

2015-08-08 08:31:08 7024 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 08:31:08 18ec InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-08-08 08:31:08 7024 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 08:31:08 7024 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 08:31:08 7024 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 08:31:08 7024 [Note] InnoDB: Memory barrier is not used
2015-08-08 08:31:08 7024 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 08:31:08 7024 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 08:31:08 7024 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 08:31:08 7024 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 08:31:08 7024 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-08 08:31:08 18ec  InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 08:31:08 7024 [ERROR] InnoDB: File C:\wamp\mysql\data\ib_logfile0: 'aio read' returned 

错误日志@innodb_force_recovery = 1

Error Log @ innodb_force_recovery = 1

2015-08-08 09:32:05 3804 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 09:32:05 1bf8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-08-08 09:32:05 3804 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 09:32:05 3804 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 09:32:05 3804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 09:32:05 3804 [Note] InnoDB: Memory barrier is not used
2015-08-08 09:32:05 3804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 09:32:05 3804 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 09:32:05 3804 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 09:32:05 3804 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 09:32:05 3804 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Database physically writes the file full: wait...
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2015-08-08 09:32:05 1bf8  InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 09:32:05 3804 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation

推荐答案

这个解决方案对我有用.

This solution worked for me.

  1. 卸载 XAMPP 和 WAMP
  2. 已安装 WAMP 64 位
  3. 在 my.ini 中添加以下行innodb_flush_method=正常
  4. 关闭 WAMP 并重新启动.标志 W 是绿色的,可以正常工作.

感谢:错误 187

这篇关于Windows 10 Enterprise - MYSQL 意外关闭的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持html5模板网!

上一篇:Microsoft SQL Server 2012 安装程序试图执行未经授权的 下一篇:将 windows8.1 升级到 windows 10 后 SQL Server 不工作

相关文章

最新文章