mysql.user台突然损坏
mysql.user台突然损坏
提问于 2018-02-11 03:12:04
我没有进行任何升级，但是MySQL (MariaDB)在重启后突然停止工作。这是日志：
2018-02-11 14:10:02 140193631740480 [Note] Using unique option prefix 'innodb_buffer_pool_instance' is error-prone and can break in the future. Please use the full name 'innodb-buffer-pool-instances' instead.
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: The InnoDB memory heap is disabled
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Using Linux native AIO
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Using SSE crc32 instructions
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Initializing buffer pool, size = 2.0G
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Completed initialization of buffer pool
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Highest supported file format is Barracuda.
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: The log sequence number 1445306045 in ibdata file do not match the log sequence number 1445306065 in the ib_logfiles!
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: 128 rollback segment(s) are active.
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Waiting for purge to start
2018-02-11 14:10:03 140193631740480 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 1445306065
2018-02-11 14:10:03 140190647551744 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-02-11 14:10:03 140193631740480 [Note] Plugin 'FEEDBACK' is disabled.
2018-02-11 14:10:03 140193631740480 [Note] Recovering after a crash using tc.log
2018-02-11 14:10:03 140193631740480 [Note] Starting crash recovery...
2018-02-11 14:10:03 140193631740480 [Note] Crash recovery finished.
2018-02-11 14:10:03 140193631740480 [Note] Server socket created on IP: '127.0.0.1'.
2018-02-11 14:10:03 140193631740480 [ERROR] Fatal error: mysql.user table is damaged or in unsupported 3.20 format.我试着环顾四周，但看不出怎么修好它。
回答 2
Database Administration用户
发布于 2018-02-18 00:56:12
试试mysqlcheck --all-databases。这可能会说mysql.user需要修理。那就去做
mysqlcheck --all-databases --repair参考文献：https://dev.mysql.com/doc/refman/5.7/en/mysqlcheck.html
Database Administration用户
发布于 2019-08-28 23:47:58
我也有过类似的问题。在我的例子中，在从旧服务器导入用户表之后，在重新启动mysql时，我无法再次启动它。
我通过以下方式修正了我的用户表：
- 编辑
my.cnf(可能在/etc/mysql/my.cnf中)并附加：米舍尔德跳过-授予-表 #service mysql start#mysql_upgrade#service mysql restart
不要忘记再次编辑my.cnf并删除skip-grant-tables
页面原文内容由Database Administration提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://dba.stackexchange.com/questions/197593
复制相关文章
相似问题
腾讯云开发者
