MySQL Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
MySQL Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
MySQL (Percona 5.6) 将无法启动。
这个错误发生在我身上好几次了。每次，我都不得不删除 MySQL 数据目录并重新安装 MySQL.
还有其他方法可以修复 MySQL 吗？ （具体哪个数据没被吹走？）
/var/log/mysql/error.log
150214 16:36:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-02-14 16:36:40 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2015-02-14 16:36:40 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-02-14 16:36:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-02-14 16:36:40 1018 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2015-02-14 16:36:40 1018 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Incorrect file format 'plugin'
2015-02-14 16:36:40 1018 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2015-02-14 16:36:40 1018 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-14 16:36:40 1018 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-14 16:36:40 1018 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-02-14 16:36:40 1018 [Note] InnoDB: Memory barrier is not used
2015-02-14 16:36:40 1018 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-02-14 16:36:40 1018 [Note] InnoDB: Using Linux native AIO
2015-02-14 16:36:40 1018 [Note] InnoDB: Using CPU crc32 instructions
2015-02-14 16:36:40 1018 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2015-02-14 16:36:40 1018 [Note] InnoDB: Completed initialization of buffer pool
2015-02-14 16:36:40 1018 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-14 16:36:40 1018 [Note] InnoDB: The log sequence numbers 714340126 and 714340126 in ibdata files do not match the log sequence number 716513090 in the ib_logfiles!
2015-02-14 16:36:40 1018 [Note] InnoDB: Database was not shutdown normally!
2015-02-14 16:36:40 1018 [Note] InnoDB: Starting crash recovery.
2015-02-14 16:36:40 1018 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-14 16:36:40 1018 [Note] InnoDB: Restoring possible half-written data pages
2015-02-14 16:36:40 1018 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 292596, file name binlog.000056
2015-02-14 16:36:40 1018 [Note] InnoDB: 128 rollback segment(s) are active.
2015-02-14 16:36:40 1018 [Note] InnoDB: Waiting for purge to start
2015-02-14 16:36:40 1018 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.1 started; log sequence number 716513090
2015-02-14 16:36:40 1018 [Note] Recovering after a crash using binlog
2015-02-14 16:36:40 1018 [Note] Starting crash recovery...
2015-02-14 16:36:40 1018 [Note] Crash recovery finished.
2015-02-14 16:36:40 1018 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2015-02-14 16:36:40 1018 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2015-02-14 16:36:40 1018 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-14 16:36:40 1018 [Note] IPv6 is available.
2015-02-14 16:36:40 1018 [Note] - '::' resolves to '::';
2015-02-14 16:36:40 1018 [Note] Server socket created on IP: '::'.
2015-02-14 16:36:40 1018 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
150214 16:36:40 mysqld_safe mysqld from pid file /tmp/mysqld.pid ended
我设法用 answer from ruby.b
解决了这个问题
You'll have to repair your host table. To do this, issue the following command to start your server bypassing the privilege system
在一个终端中，运行
$ sudo mysqld --skip-grant-tables
打开另一个终端并执行这些命令
$ mysql
mysql> use mysql
mysql> repair table host use_frm;
mysql> exit
并重启mysql服务
$ sudo service mysql restart
感谢 John 让我走上了正确的轨道，我的系统上还有其他一些障碍需要跳过。希望这对某人有所帮助。
这是一个损坏的特权 table。可能是由升级或电源故障引起的。我的系统 OpenSUSE 13.2，MySQL 5.6。简单的重新安装并不能解决问题，必须在重新安装之前删除 MySQL 的所有痕迹，或者...
关闭MySQL
的所有实例
$ systemctl stop mysql.service
$ pkill -9 mysqld
绕过特权系统启动服务器
$ sudo mysqld_safe --user=root --skip-grant-tables
启动MySQL命令行工具
$ mysql
如果您收到
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
mysqld_safe 是 运行 它在别处的套接字。用.
找
$ sudo find / -type s
我的在 /var/run/mysql/
编辑 my.cnf 中的套接字行，记下您现有的套接字设置。
我的台词变成了
socket=/var/run/mysql/mysql.sock
Return 到 'Close down all instances of MySQL'（这些说明的顶部）。跟随他们到达 'Start MySQL command line tool'。希望你能成功打开mysql。来自 mysql 命令行。
mysql> use mysql
mysql> repair table user use_frm;
mysql> exit
关闭MySQL
的所有实例
$ systemctl stop mysql.service
$ pkill -9 mysqld
重新编辑my.cnf，将插座线恢复到原来的设置。
我不得不重置 mysql 数据目录中 2 个文件的权限。
$ chown mysql:mysql server2.err
$ chown mysql:mysql server2.pid
启动 MySQL 服务器
$ systemctl start mysql.service
然后我得到了与另一个相同的原始错误 table (db)
[ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'db'
并且必须多次重复上述过程，更改 'repair' 命令，直到所有权限 table 都得到修复。
mysql> repair table db use_frm;
这是 @John Linhart 的答案的设置，如果你 运行宁 Docker:
首先，使用 mysql 容器中的适当标签启动一个新的 docker 容器（与您用来编写数据库的标签相同）。
$ docker run --rm -it -v <named_volume>:/var/lib/mysql mysql:<tag> /bin/bash
这将启动一个新容器，并在容器中安装了正确命名的卷（或已安装的卷），并将您作为 root 放入 shell。 mysqld-Daemon 将拒绝以 root 身份启动，因此我们将 运行 它作为 mysql-user:
$ whoami
root
$ which mysqld
/usr/sbin/mysqld
$ su mysql
$ whoami
mysql
$ /usr/sbin/mysqld --skip-grant-tables
....
现在 运行 SQL 命令，我们将从新终端连接到 运行ning 容器：
$ docker ps
CONTAINER ID [...]
abc123 [...]
$ docker exec -it abc123 /bin/bash
# We're on the container now!
$ whoami
root
$ mysql
...
然后从那里继续。完成后，通过 exit 将容器留在第二个终端上。终端 运行ning mysqld 不会响应 CMD+C，所以我们将通过 Docker:
停止容器
$ docker ps
CONTAINER ID [...]
abc123 [...]
$ docker stop abc123
MySQL (Percona 5.6) 将无法启动。
这个错误发生在我身上好几次了。每次，我都不得不删除 MySQL 数据目录并重新安装 MySQL.
还有其他方法可以修复 MySQL 吗？ （具体哪个数据没被吹走？）
/var/log/mysql/error.log
150214 16:36:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2015-02-14 16:36:40 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2015-02-14 16:36:40 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2015-02-14 16:36:40 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-02-14 16:36:40 1018 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2015-02-14 16:36:40 1018 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Incorrect file format 'plugin'
2015-02-14 16:36:40 1018 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2015-02-14 16:36:40 1018 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-02-14 16:36:40 1018 [Note] InnoDB: The InnoDB memory heap is disabled
2015-02-14 16:36:40 1018 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-02-14 16:36:40 1018 [Note] InnoDB: Memory barrier is not used
2015-02-14 16:36:40 1018 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-02-14 16:36:40 1018 [Note] InnoDB: Using Linux native AIO
2015-02-14 16:36:40 1018 [Note] InnoDB: Using CPU crc32 instructions
2015-02-14 16:36:40 1018 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2015-02-14 16:36:40 1018 [Note] InnoDB: Completed initialization of buffer pool
2015-02-14 16:36:40 1018 [Note] InnoDB: Highest supported file format is Barracuda.
2015-02-14 16:36:40 1018 [Note] InnoDB: The log sequence numbers 714340126 and 714340126 in ibdata files do not match the log sequence number 716513090 in the ib_logfiles!
2015-02-14 16:36:40 1018 [Note] InnoDB: Database was not shutdown normally!
2015-02-14 16:36:40 1018 [Note] InnoDB: Starting crash recovery.
2015-02-14 16:36:40 1018 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-02-14 16:36:40 1018 [Note] InnoDB: Restoring possible half-written data pages
2015-02-14 16:36:40 1018 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 292596, file name binlog.000056
2015-02-14 16:36:40 1018 [Note] InnoDB: 128 rollback segment(s) are active.
2015-02-14 16:36:40 1018 [Note] InnoDB: Waiting for purge to start
2015-02-14 16:36:40 1018 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.21-70.1 started; log sequence number 716513090
2015-02-14 16:36:40 1018 [Note] Recovering after a crash using binlog
2015-02-14 16:36:40 1018 [Note] Starting crash recovery...
2015-02-14 16:36:40 1018 [Note] Crash recovery finished.
2015-02-14 16:36:40 1018 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
2015-02-14 16:36:40 1018 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
2015-02-14 16:36:40 1018 [Note] Server hostname (bind-address): '*'; port: 3306
2015-02-14 16:36:40 1018 [Note] IPv6 is available.
2015-02-14 16:36:40 1018 [Note] - '::' resolves to '::';
2015-02-14 16:36:40 1018 [Note] Server socket created on IP: '::'.
2015-02-14 16:36:40 1018 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'user'
150214 16:36:40 mysqld_safe mysqld from pid file /tmp/mysqld.pid ended
我设法用 answer from ruby.b
解决了这个问题You'll have to repair your host table. To do this, issue the following command to start your server bypassing the privilege system
在一个终端中，运行
$ sudo mysqld --skip-grant-tables
打开另一个终端并执行这些命令
$ mysql
mysql> use mysql
mysql> repair table host use_frm;
mysql> exit
并重启mysql服务
$ sudo service mysql restart
感谢 John 让我走上了正确的轨道，我的系统上还有其他一些障碍需要跳过。希望这对某人有所帮助。
这是一个损坏的特权 table。可能是由升级或电源故障引起的。我的系统 OpenSUSE 13.2，MySQL 5.6。简单的重新安装并不能解决问题，必须在重新安装之前删除 MySQL 的所有痕迹，或者...
关闭MySQL
的所有实例$ systemctl stop mysql.service
$ pkill -9 mysqld
绕过特权系统启动服务器
$ sudo mysqld_safe --user=root --skip-grant-tables
启动MySQL命令行工具
$ mysql
如果您收到
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
mysqld_safe 是 运行 它在别处的套接字。用.
找$ sudo find / -type s
我的在 /var/run/mysql/ 编辑 my.cnf 中的套接字行，记下您现有的套接字设置。 我的台词变成了
socket=/var/run/mysql/mysql.sock
Return 到 'Close down all instances of MySQL'（这些说明的顶部）。跟随他们到达 'Start MySQL command line tool'。希望你能成功打开mysql。来自 mysql 命令行。
mysql> use mysql
mysql> repair table user use_frm;
mysql> exit
关闭MySQL
的所有实例$ systemctl stop mysql.service
$ pkill -9 mysqld
重新编辑my.cnf，将插座线恢复到原来的设置。
我不得不重置 mysql 数据目录中 2 个文件的权限。
$ chown mysql:mysql server2.err
$ chown mysql:mysql server2.pid
启动 MySQL 服务器
$ systemctl start mysql.service
然后我得到了与另一个相同的原始错误 table (db)
[ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'db'
并且必须多次重复上述过程，更改 'repair' 命令，直到所有权限 table 都得到修复。
mysql> repair table db use_frm;
这是 @John Linhart 的答案的设置，如果你 运行宁 Docker:
首先，使用 mysql 容器中的适当标签启动一个新的 docker 容器（与您用来编写数据库的标签相同）。
$ docker run --rm -it -v <named_volume>:/var/lib/mysql mysql:<tag> /bin/bash
这将启动一个新容器，并在容器中安装了正确命名的卷（或已安装的卷），并将您作为 root 放入 shell。 mysqld-Daemon 将拒绝以 root 身份启动，因此我们将 运行 它作为 mysql-user:
$ whoami
root
$ which mysqld
/usr/sbin/mysqld
$ su mysql
$ whoami
mysql
$ /usr/sbin/mysqld --skip-grant-tables
....
现在 运行 SQL 命令，我们将从新终端连接到 运行ning 容器：
$ docker ps
CONTAINER ID [...]
abc123 [...]
$ docker exec -it abc123 /bin/bash
# We're on the container now!
$ whoami
root
$ mysql
...
然后从那里继续。完成后，通过 exit 将容器留在第二个终端上。终端 运行ning mysqld 不会响应 CMD+C，所以我们将通过 Docker:
$ docker ps
CONTAINER ID [...]
abc123 [...]
$ docker stop abc123