简体   繁体   English

Mysql 崩溃并且无法在 xampp 中启动

[英]Mysql crashed and not starting in xampp

Here my log files in mysql这是我在 mysql 中的日志文件

2019-12-10 15:10:18 1428 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. 2019-12-10 15:10:18 1428 InnoDB:警告:不推荐使用 innodb_additional_mem_pool_size。 This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.此选项可能会在未来版本中与选项 innodb_use_sys_malloc 和 InnoDB 的内部内存分配器一起删除。 2019-12-10 15:10:18 5160 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. 2019-12-10 15:10:18 5160 [注意] InnoDB:innodb_empty_free_list_algorithm 由于缓冲池大小较小,已更改为旧版。 In order to use backoff, increase buffer pool at least up to 20MB.为了使用退避,将缓冲池至少增加到 20MB。

2019-12-10 15:10:18 5160 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-12-10 15:10:18 5160 [Note] InnoDB: The InnoDB memory heap is disabled
2019-12-10 15:10:18 5160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-12-10 15:10:18 5160 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2019-12-10 15:10:18 5160 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-12-10 15:10:18 5160 [Note] InnoDB: Using generic crc32 instructions
2019-12-10 15:10:18 5160 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2019-12-10 15:10:18 5160 [Note] InnoDB: Completed initialization of buffer pool
2019-12-10 15:10:18 5160 [Note] InnoDB: Highest supported file format is Barracuda.
2019-12-10 15:10:18 5160 [Note] InnoDB: Starting crash recovery from checkpoint LSN=7472761787
2019-12-10 15:10:19 5160 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 2850 row operations to undo
InnoDB: Trx id counter is 1963520
2019-12-10 15:10:19 5160 [Note] InnoDB: Starting final batch to recover 307 pages from redo log

从 c:xampp\\mysql\\data 目录中删除 ibdata1 文件、ib_logfile1、ib_logfile1 后,它开始工作

Warning: Using innodb_additional_mem_pool_size is DEPRECATED.警告:不推荐使用 innodb_additional_mem_pool_size。 This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.此选项可能会在未来版本中与选项 innodb_use_sys_malloc 和 InnoDB 的内部内存分配器一起删除。

According to https://blogs.oracle.com/supportingmysql/entry/remove_on_sight_thread_concurrency , MySQL 5.6 will deprecated three parameters in the configuration file:根据https://blogs.oracle.com/supportingmysql/entry/remove_on_sight_thread_concurrency ,MySQL 5.6 将弃用配置文件中的三个参数:

thread_concurrency innodb_additional_mem_pool_size innodb_use_sys_malloc thread_concurrency innodb_additional_mem_pool_size innodb_use_sys_malloc

Solution: If you are currently using version 5.1 or 5.5, it is recommended to set the parameter value to 1 innodb_use_sys_malloc = 1 If version 5.6.3 or later, comment the parameter: innodb_additional_mem_pool_size解决方案:如果你当前使用的是5.1或5.5版本,建议将参数值设置为1 innodb_use_sys_malloc = 1 如果是5.6.3或更高版本,注释参数:innodb_additional_mem_pool_size

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM