gpt4 book ai didi

php - 不当关闭后 WAMP 服务器橙色

转载 作者:行者123 更新时间:2023-11-29 03:28:12 25 4
gpt4 key购买 nike

我的电脑在 wamp 服务器运行时由于断电而关闭,现在当我试图打开服务器时它仍然是橙色的,对服务器的 http 请求正在工作,但是当我尝试登录 MySQl 时我收到以下错误:

#2002 Cannot log in to the MySQL server

我搜索了一下,结果都是卸载重装,还有其他办法吗?我仍然是初学者,所以我实际上不知道我需要向您展示哪些文件才能帮助我,请对我需要展示的任何内容发表评论。

我在 mysql 日志中的最后一次登录尝试:

2015-11-11 11:08:03 8052 [Note] Plugin 'FEDERATED' is disabled.
2015-11-11 11:08:03 8052 [Note] InnoDB: The InnoDB memory heap is disabled
2015-11-11 11:08:03 8052 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-11-11 11:08:03 8052 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-11-11 11:08:03 8052 [Note] InnoDB: Not using CPU crc32 instructions
2015-11-11 11:08:03 8052 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-11-11 11:08:03 8052 [Note] InnoDB: Completed initialization of buffer pool
2015-11-11 11:08:03 8052 [Note] InnoDB: Highest supported file format is Barracuda.
2015-11-11 11:08:03 8052 [Note] InnoDB: The log sequence numbers 2671283 and 2671283 in ibdata files do not match the log sequence number 2671293 in the ib_logfiles!
2015-11-11 11:08:03 8052 [Note] InnoDB: Database was not shutdown normally!
2015-11-11 11:08:03 8052 [Note] InnoDB: Starting crash recovery.
2015-11-11 11:08:03 8052 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-11-11 11:08:03 8052 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace coldatabase/item uses space ID: 3 at filepath: .\coldatabase\item.ibd. Cannot open tablespace mysql/slave_relay_log_info which uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\slave_relay_log_info.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

最佳答案

我遇到了类似的问题,我用两种方法解决了它,我提到的是两种方法中更好的一种。

  1. 将 c:\wamp 文件夹复制到任何其他安全位置
  2. 让原来的 c:\wamp 文件夹留在原处
  3. 使用您之前安装的同一个包安装 wamp 服务器
  4. 启动wamp服务器
  5. 完成...!!!

(将 c:\wamp 文件夹复制到任何其他安全位置只是为了紧急情况,以防出现问题)。

关于php - 不当关闭后 WAMP 服务器橙色,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/33639219/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com