The following is from localhost./usr/local/mysql5/libexec/mysqld: Table 'plugin' is read only [ERROR]: Can't open the mysql.plugin table.
Inform us if you still get same error after removing pid file.
Manager of pid-file quit without updating[FAILED] The server shut down fine and that is when the pid file should have gone away. This is from the error log: 081212 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 081212 Inno DB: Started; log sequence number 5 2292330012 /usr/sbin/mysqld(print_stacktrace 0x1e)[0x6cd03e] /usr/sbin/mysqld(handle_segfault 0x320)[0x5b8610] /lib64/0[0x319ae0de70] /usr/sbin/mysqld(_Z12push_warning P3THDN11MYSQL_ERROR18enum_warning_level Ej PK c 0x40)[0x632b30] /usr/sbin/mysqld(_Z19push_warning_printf P3THDN11MYSQL_ERROR18enum_warning_le vel Ej PKcz 0xd9)[0x632de9] /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG22purge_logs_before_date El 0x236)[0x64192 6] /usr/sbin/mysqld[0x5b7072] /usr/sbin/mysqld(main 0x6f9)[0x5b9059] /lib64/6(__libc_start_main 0xf4)[0x319a21d8b4] /usr/sbin/mysqld[0x507ea9] 081212 - mysqld got signal 11 ; This could be because you hit a bug.
Please use the full name instead.160308 [Note] Plugin 'FEDERATED' is disabled.160308 [Note] Plugin 'partition' is disabled.160308 Inno DB: The Inno DB memory heap is disabled160308 Inno DB: Mutexes and rw_locks use GCC atomic builtins160308 Inno DB: Compressed tables use zlib 1.2.3160308 Inno DB: Using Linux native AIO160308 Inno DB: Initializing buffer pool, size = 64.0M160308 Inno DB: Completed initialization of buffer pool160308 Inno DB: highest supported file format is Barracuda.
This error log may be under your system’s log directory (/var/log/mysql) or under the mysql data folder (usually /usr/local/mysql/data). In my case the error log listed the following items: Inno DB: No valid checkpoint found.
Inno DB: If this error appears when you are creating an Inno DB database, Inno DB: the problem may be that during an earlier attempt you managed Inno DB: to create the Inno DB data files, but log file creation failed.
It is also possible that this binaryor one of the libraries it was linked against is corrupt, improperly built,or misconfigured.
This error can also be caused by malfunctioning hardware.