0

我一直在寻找解决这个问题的方法。我的 MySql 给了我以下读数:

121231 20:41:05 [Note] Plugin 'FEDERATED' is disabled.
121231 20:41:05 InnoDB: The InnoDB memory heap is disabled
121231 20:41:05 InnoDB: Mutexes and rw_locks use Windows interlocked functions
121231 20:41:05 InnoDB: Compressed tables use zlib 1.2.3
121231 20:41:05 InnoDB: Initializing buffer pool, size = 512.0M
121231 20:41:05 InnoDB: Completed initialization of buffer pool
121231 20:41:05 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121231 20:41:05  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
121231 20:41:06  InnoDB: Waiting for the background threads to start
121231 20:41:07 InnoDB: 1.1.8 started; log sequence number 124716458
121231 20:41:07 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121231 20:41:07 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121231 20:41:07 [Note] Server socket created on IP: '0.0.0.0'.
121231 20:41:09 [Note] Event Scheduler: Loaded 0 events
121231 20:41:09 [Note] c:\xampp\mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.27'  socket: ''  port: 3306  MySQL Community Server (GPL)

每次开始。我试过删除文件,删除数据库,运行 Magento 的修复数据库工具,从一个新数据库重新开始,但不管我得到这个错误是什么。

这让我感到不舒服,因为我不确定某些东西可能会损坏或损坏。我正在使用 Windows Vista 和 Xampp,但我也在使用 nginX 并显示相同的内容。

我刚刚重新创建了一个全新的数据库,现在关闭后(有时我必须这样做)错误再次出现!这是正常现象还是有什么问题?

谢谢

4

1 回答 1

2

从日志中可以看到 InnoDB 开始崩溃恢复:

InnoDB: Starting crash recovery.

原因是 MySQL 关闭不干净。为什么?可能是 MySQL 退出时间过长,操作系统终止了进程(如果您重新启动服务器)。或者 MySQL 因错误而崩溃。

于 2014-02-10T21:42:45.467 回答