gpt4 book ai didi

MYSQL 启动几秒后崩溃

转载 作者:行者123 更新时间:2023-11-29 10:04:01 24 4
gpt4 key购买 nike

我的 xampp 附带的 mysql 工作正常一年了,但几秒钟后突然崩溃了..

这是日志

2018-09-13 12:30:34 48 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.
2018-09-13 12:30:34 72 [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.

2018-09-13 12:30:34 72 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-09-13 12:30:34 72 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-13 12:30:34 72 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-13 12:30:34 72 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-09-13 12:30:34 72 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-13 12:30:34 72 [Note] InnoDB: Using generic crc32 instructions
2018-09-13 12:30:34 72 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-09-13 12:30:34 72 [Note] InnoDB: Completed initialization of buffer pool
2018-09-13 12:30:35 72 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-13 12:30:35 72 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 5523302532 in the ib_logfiles!
2018-09-13 12:30:36 72 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2018-09-13 12:30:36 72 [Note] InnoDB: 128 rollback segment(s) are active.
2018-09-13 12:30:36 72 [Note] InnoDB: Waiting for purge to start
2018-09-13 12:30:36 72 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 5523302532
2018-09-13 12:30:36 2928 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-09-13 12:30:36 72 [Note] Plugin 'FEEDBACK' is disabled.
2018-09-13 12:30:36 72 [Note] Server socket created on IP: '::'.
2018-09-13 12:30:36 72 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format.

最佳答案

错误显示: fatal error :mysql.user 表已损坏或不受支持的 3.20 格式。

警告和注释不会破坏服务。要尝试解决此问题,您可以尝试使用 mysqlcheck

mysqlcheck --all-databases

这可能会告诉您用户表已损坏,如错误所示,然后运行:

mysqlcheck --repair --all-databases

关于MYSQL 启动几秒后崩溃,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/52306810/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com