MySQL错误InnoDB：警告

为什么会发生此错误？MySQL错误InnoDB：警告

2017-06-15 05:54:42 1848 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. 
2017-06-15 5:54:42 6216 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB. 

2017-06-15 5:54:42 6216 [Note] InnoDB: Using mutexes to ref count buffer pool pages 
2017-06-15 5:54:42 6216 [Note] InnoDB: The InnoDB memory heap is disabled 
2017-06-15 5:54:42 6216 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
2017-06-15 5:54:42 6216 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 
2017-06-15 5:54:42 6216 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2017-06-15 5:54:42 6216 [Note] InnoDB: Using generic crc32 instructions 
2017-06-15 5:54:42 6216 [Note] InnoDB: Initializing buffer pool, size = 16.0M 
2017-06-15 5:54:42 6216 [Note] InnoDB: Completed initialization of buffer pool 
2017-06-15 5:54:42 6216 [Note] InnoDB: Restoring page 0 of tablespace 0 
2017-06-15 5:54:42 6216 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0 
2017-06-15 5:54:42 6216 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1 
2017-06-15 5:54:42 6216 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! 
2017-06-15 5:54:42 6216 [ERROR] Plugin 'InnoDB' init function returned error. 
2017-06-15 5:54:42 6216 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 
2017-06-15 5:54:42 6216 [Note] Plugin 'FEEDBACK' is disabled. 
2017-06-15 5:54:42 6216 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded 
2017-06-15 5:54:42 6216 [ERROR] Unknown/unsupported storage engine: InnoDB 
2017-06-15 5:54:42 6216 [ERROR] Aborting

来源

2017-06-15 xwally

在这开始发生之前，你在这个服务器上有什么改变吗？您是否遇到过任何问题，如强制关闭电源或任何类型的故障？ –

我从mySql切换到MariaDB后出现类似的问题，并且输出中列出的一些错误是相同的。我希望我的解决方案也与你相关（因为你没有给出关于这个问题的很多背景）。

我的问题是，我没有用下面的命令初始化数据库用户：

$ mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql

运行在此之后，我解决了这个错误

[ERROR] Could not open mysql.plugin table. Some plugins may be not loaded

，当我再次启动数据库，它工作得很好。

来源

2017-06-17 21:45:34 FedericoCapaldo

我不太清楚，如果我和你有完全相同的问题（我的日志里有一些不同的东西）。但MySQL（实际上是MariaDB）无法启动，使用相同的[ERROR] Unknown/unsupported storage engine: InnoDB。我解决它添加这一行到配置（无论是在现有[mysqld]节结束，或者添加与标头的新章节）：

default_tmp_storage_engine = InnoDB

而且似乎解决这个问题对我来说。 MySQL现在开始很好...

来源

2017-12-11 02:36:59

MySQL错误InnoDB：警告

回答

相关问题