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：警告

回答

相關問題