这篇文章主要为大家展示了“MySQL报错Table 'plugin' is read only [ERROR] Can't open the mysql.plugin table怎么办”，内容简而易懂，条理清晰，希望能够帮助大家解决疑惑，下面让小编带领大家一起研究并学习一下“MySQL报错Table 'plugin' is read only [ERROR] Can't open the mysql.plugin table怎么办”这篇文章吧。
创新互联建站是一家专业提供陆港企业网站建设,专注与成都做网站、成都网站建设、H5高端网站建设、小程序制作等业务。10年已为陆港众多企业、政府机构等服务。创新互联专业网站建设公司优惠进行中。
迁移MySQL数据库的时候，发生了下面的报错
181205 14:10:22 mysqld_safe Starting mysqld daemon with databases from /data/mysql_3308/ 2018-12-05 14:10:22 18964 [Warning] You need to use --log-bin to make --log-slave-updates work. 2018-12-05 14:10:22 18964 [Warning] You need to use --log-bin to make --binlog-format work. 2018-12-05 14:10:22 18964 [Note] Plugin 'FEDERATED' is disabled. /usr/sbin/mysqld: Table 'plugin' is read only 2018-12-05 14:10:22 18964 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2018-12-05 14:10:22 7fe3f219b740 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-12-05 14:10:22 18964 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-12-05 14:10:22 18964 [Note] InnoDB: The InnoDB memory heap is disabled 2018-12-05 14:10:22 18964 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-12-05 14:10:22 18964 [Note] InnoDB: Memory barrier is not used 2018-12-05 14:10:22 18964 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-12-05 14:10:22 18964 [Note] InnoDB: Using Linux native AIO 2018-12-05 14:10:22 18964 [Note] InnoDB: Using CPU crc32 instructions 2018-12-05 14:10:22 18964 [Note] InnoDB: Initializing buffer pool, size = 4.0G 2018-12-05 14:10:22 18964 [Note] InnoDB: Completed initialization of buffer pool 2018-12-05 14:10:23 18964 [Note] InnoDB: Highest supported file format is Barracuda. 2018-12-05 14:10:23 18964 [Note] InnoDB: 128 rollback segment(s) are active. 2018-12-05 14:10:23 18964 [Note] InnoDB: Waiting for purge to start 06:10:23 UTC - mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=2000 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4387598 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8dd30b] /usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6720b1] /lib64/libpthread.so.0(+0xf6d0)[0x7fe3f1d7c6d0] /usr/sbin/mysqld(my_realpath+0x87)[0x8da5d7] /usr/sbin/mysqld(_Z19find_or_create_fileP10PFS_threadP14PFS_file_classPKcjb+0x9c)[0xabaddc]
报错提示plugin表只读，无法正常打开。
查看对应数据目录的权限，已经授予了mysql的所属权限。
[root@bi-multi-mysql-d9 mysql_3307]# ls -trl total 3621384 drwxr-xr-x 2 mysql2 mysql2 10 Jul 13 2017 test -rwxr-xr-x 1 mysql2 mysql2 536870912 Jul 13 2017 ib_logfile1 -rwxr-xr-x 1 mysql2 mysql2 536870912 Jul 13 2017 ib_logfile2 drwxr-xr-x 2 mysql2 mysql2 4096 Jul 13 2017 performance_schema -rwxr-xr-x 1 mysql2 mysql2 431 Jul 13 2017 mysql-bin.000001 drwxr-xr-x 2 mysql2 mysql2 8192 Jul 13 2017 mysql -rwxr-xr-x 1 mysql2 mysql2 143 Jul 13 2017 mysql-bin.000002 -rwxr-xr-x 1 mysql2 mysql2 57 Jul 13 2017 mysql-bin.index -rwxr-xr-x 1 mysql2 mysql2 56 Jul 13 2017 auto.cnf -rwxr-xr-x 1 mysql2 mysql2 109302 Jul 14 2017 mysql-bin.000003 drwxr-xr-x 2 mysql2 mysql2 4096 Sep 29 09:12 jolly_alliance_center -rwxr-xr-x 1 mysql2 mysql2 221 Dec 5 12:20 mysqld-relay-bin.000670 -rwxr-xr-x 1 mysql2 mysql2 52 Dec 5 12:20 mysqld-relay-bin.index -rwxr-xr-x 1 mysql2 mysql2 69 Dec 5 15:08 relay-log.info -rwxr-xr-x 1 mysql2 mysql2 358775 Dec 5 15:08 mysqld-relay-bin.000671 -rwxr-xr-x 1 mysql2 mysql2 137 Dec 5 15:08 master.info -rwxr-xr-x 1 mysql2 mysql2 536870912 Dec 5 16:37 ib_logfile0 -rwxr-xr-x 1 mysql2 mysql2 1048576000 Dec 5 16:37 ibdata2 -rwxr-xr-x 1 mysql2 mysql2 1048576000 Dec 5 16:37 ibdata1
报错的原因：
mysql操作系统用户的权限被修改，无法进入数据目录，进而导致报错。
数据目录是/data/mysql_3307，mysql操作系统用户无法进入/data。
![MySQL报错Table 'plugin' is read only [ERROR] Can't open the mysql.plugin table怎么办](/upload/otherpic55/21442.png)
修改权限后，恢复正常。
以上是“MySQL报错Table 'plugin' is read only [ERROR] Can't open the mysql.plugin table怎么办”这篇文章的所有内容，感谢各位的阅读！相信大家都有了一定的了解，希望分享的内容对大家有所帮助，如果还想学习更多知识，欢迎关注创新互联行业资讯频道！
