MySQL報錯Table 'plugin' is read only [ERROR] Can't open the mysql.plugin table.
今天遷移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。
修改許可權後,恢復正常。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26506993/viewspace-2284295/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [ERROR] Can't open the mysql.plugin tableErrorMySqlPlugin
- MySQL 啟動報錯 Table 'mysql.plugin' doesn't existMySqlPlugin
- Mysql報錯Fatal error:Can't open and lock privilege tablesMySqlError
- Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist解決辦法ErrorMySql
- MySQL 建立外來鍵報錯Can't write; duplicate key in tableMySql
- MySQL 5.5 原始碼安裝報錯"[ERROR] Can't start server"MySql原始碼ErrorServer
- MYSQL報1022錯誤:Can't write;duplicate key in table '.....'MySql
- [ERROR] mysqld: Can‘t open shared library ‘/usr/local/mysql/lib/plugin/validate_password.so‘ (errno:ErrorMySqlPlugin
- mysql [ERROR] InnoDB: ./ibdata1 can't be opened in read-write modeMySqlError
- MySQL 報錯'Variable 'XXX' is a read only variable'MySql
- RMAN的"rman: can't open target"錯誤
- 【MySQL】ERROR 1005 (HY000): Can't create table' (errno: 150)MySqlError
- MySQL報錯'ERROR 2002 (HY000): Can't connect to local MySQL server through'MySqlErrorServer
- rman: can't open target
- mysql [ERROR] Can't create IP socket: Permission deniedMySqlError
- mysql啟動時報錯Can't read from messagefile errmsg.sysMySql
- GTID複製報錯處理:Last_Error: Error 'Can't drop database 'test';ASTErrorDatabase
- Linux下安裝Oracle 錯誤解決 - Error: Can't open display:127.0..0.1:0.0LinuxOracleError
- 備庫open read only報錯,經查是有一個trigger在open後觸發
- view the favorites table.View
- mysql 5.7啟動報錯"Expected to open undo tablespaces but was able to find only 0"MySql
- mysql中You can’t specify target table for update in FROM clMySql
- Mysql update in報錯 [Err] 1093 - You can't specify target table 'company_info' for update in FROM clauseMySql
- mysql can't connect error about privilege----not root userMySqlError
- eslint --fix 報錯 can't not find modulesEsLint
- MongoDB報錯:"assertion" : "can't map file memory"MongoDB
- Open a Database in Read-Only Mode (301)Database
- 解決Error (1133): Can’t find any matching row in the user tableError
- Swift代理報錯Optional can only be applied to members of an @objc protocolSwiftAPPOBJProtocol
- mysql匯入報錯Variable 'sql_notes' can't be set to the value of 'NULL'MySqlNull
- 【報錯】elasticsearch 報錯blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]ElasticsearchBloCORBIndexdeleteAPI
- MySQl報錯之@@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ONMySql
- MySQL 5.5 關閉資料庫報錯"Can't connect to local MySQL server through socket"MySql資料庫Server
- MySQL 中出現報錯提示: ‘Variable ‘XXX‘ is a read only variable‘的解決方法MySql
- MySQL查詢報錯:ERROR 1146 (42S02): Table 'craw.sitePageConfig' doesn't existMySqlError
- MySQL 5.7向表匯入資料包錯"ERROR 13 (HY000): Can't get stat of"MySqlError
- Error:/etc/fstab:Read-only file system錯誤的解決辦法Error
- ERROR 1005 (HY000): Can't create table 'starive.SC' (errno: 150)"Error