Question

我已经搜索了这个问题的解决方案。我的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显示相同的内容。

我刚刚重新创建了一个全新的数据库，现在关机后（我有时必须这样做）错误再次出现！这是正常的事情还是有些错误？

由于

Answer 1

从日志中可以看出InnoDB开始崩溃恢复：

InnoDB: Starting crash recovery.

原因是MySQL关闭不干净。为什么？可能是MySQL已经退出太长时间并且操作系统会终止进程（如果你重新启动服务器）。或者MySQL因崩溃而崩溃。

MySQL ...开始崩溃恢复

1 个答案: