Php 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

---

从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

---

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

我不太确定我是否遇到了与您完全相同的问题（我的日志中有一些不同的内容）。但是MySQL（在我的例子中，实际上是MariaDB）无法启动，具有相同的

[ERROR]未知/不受支持的存储引擎：InnoDB

。我通过将这一行添加到配置（在现有的

[mysqld]

节的末尾，或者添加一个带有该标题的新节）解决了这个问题：

---

这似乎解决了我的问题。MySQL现在启动良好…

在我的例子中，问题是MySQL服务器配置的缓冲池太大（在内存太少的虚拟机上运行-只有2GB RAM）

---

在发生这种情况之前，您是否更改了此服务器上的任何内容？你有任何问题吗，比如强制断电或任何类型的碰撞？

default_tmp_storage_engine = InnoDB

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