MySQL錯誤InnoDB：警告

Question

為什么會出現此錯誤？

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

Answer 1

從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

當我再次啟動數據庫時，它運行得很好。

Answer 2

我不太確定我是否和你有完全相同的問題（我的日志中有一些不同的東西）。 但MySQL（在我的情況下實際上是MariaDB）無法啟動，使用相同的[ERROR] Unknown/unsupported storage engine: InnoDB 。 我通過在配置中添加此行來解決它（在現有[mysqld]部分的末尾，或者添加帶有該標題的新部分）：

default_tmp_storage_engine = InnoDB

而這似乎為我解決了這個問題。 MySQL現在開始很好......

Answer 3

在我的情況下，問題是MySQL服務器配置了太大的緩沖池大小（在內存太少的虛擬機上運行 - 只有2GB RAM）

2018-11-13 17:06:19 7882 [Note] Plugin 'FEDERATED' is disabled.
2018-11-13 17:06:19 7882 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-11-13 17:06:19 7882 [Note] InnoDB: The InnoDB memory heap is disabled
2018-11-13 17:06:19 7882 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-11-13 17:06:19 7882 [Note] InnoDB: Memory barrier is not used
2018-11-13 17:06:19 7882 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-11-13 17:06:19 7882 [Note] InnoDB: Using Linux native AIO
2018-11-13 17:06:19 7882 [Note] InnoDB: Not using CPU crc32 instructions
2018-11-13 17:06:19 7882 [Note] InnoDB: Initializing buffer pool, size = 2.0G
InnoDB: mmap(1117782016 bytes) failed; errno 12
2018-11-13 17:06:19 7882 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
2018-11-13 17:06:19 7882 [ERROR] Plugin 'InnoDB' init function returned error.
2018-11-13 17:06:19 7882 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2018-11-13 17:06:19 7882 [ERROR] Unknown/unsupported storage engine: InnoDB
2018-11-13 17:06:19 7882 [ERROR] Aborting