Mysql is Offline

abdelhost77

February 04, 2015 04:22

Please HELP !! Mysql is offline even if i try to put innodb_force_recovery = 6 in /etc/my.cnf it want be started with following error :

InnoDB: The user has set SRV_FORCE_NO_LOG_REDO on
InnoDB: Skipping log redo
InnoDB: Error: tried to read 16384 bytes at offset 0 49152.
InnoDB: Was only able to read -1.
150204 10:16:25  InnoDB: Operating system error number 5 in a file operation.
InnoDB: Error number 5 means 'Input/output error'.
InnoDB: Some operating system error numbers are described at
InnoDB: [url=http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html]MySQL :: MySQL 5.5 Reference Manual :: 14.21.6 Operating System Error Codes
InnoDB: File operation call: 'read'.
InnoDB: Cannot continue operation.

Comments

2 comments

abdelhost77

February 04, 2015 10:36
It seems that this is related to the last Upgared to Cpanel 11.48 ( build 7), because i found this on the last /var/cpanel/updatelogs
[20150203.231106] cpanel-perl-514-HTML-Format-2.11-1.cp1146 [20150203.231109] MySQL55-test-5.5.40-1.cp1148 [20150203.231151] Giving mysqld 10 seconds to exit nicely [20150203.231201] MySQL55-server-5.5.40-1.cp1148 [20150203.231231] Upgrading [20150203.231232] Starting MySQL using init.d [20150203.231250] Starting MySQL..................The server quit without updating PID file (/var/lib/mysql/.pid).[FAILED] [20150203.231250] Giving mysqld 5 seconds to start [20150203.231339] Waiting for "mysql" to start "" [20150203.231339] "failed. [20150203.231339] [20150203.231339] ^[[1mService Error^[[0m [20150203.231339] The "mysql" service failed to start. [20150203.231339] [20150203.231339] ^[[1mStartup Log^[[0m [20150203.231339] Starting MySQL........The server quit without updating PID file (/var/lib/mysql/.pid).[FAILED] [20150203.231339] [20150203.231339] ^[[1mLog Messages^[[0m [20150203.231339] 150203 23:13:33 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended [20150203.231339] 150203 23:13:25 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql [20150203.231339] 150203 23:13:19 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended [20150203.231339] 150203 23:13:11 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql [20150203.231339] 150203 23:13:04 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended [20150203.231339] 150203 23:12:56 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql [20150203.231339] 150203 23:12:49 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended [20150203.231339] 150203 23:12:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql [20150203.231339] 150203 23:11:51 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended [20150203.231339] 150203 23:11:51 [Note] /usr/sbin/mysqld: Shutdown complete [20150203.231339] ^[[1;30;43m150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 9 user: 'eximstats'^[[0m [20150203.231339] ^[[1;30;43m150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 16 user: 'modsec'^[[0m [20150203.231339] ^[[1;30;43m150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 271 user: 'root'^[[0m [20150203.231339] ^[[1;30;43m150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 325720 user: 'leechprotect'^[[0m [20150203.231339] 150203 23:11:28 [Note] /usr/sbin/mysqld: Normal shutdown [20150203.231339] [20150203.231339] ^[[1;30;41mmysql has failed. Please contact your system administrator if the service does not automagically recover.^[[0m [20150203.231344] Looking for 'mysql' as: /usr/bin/mysql [20150203.231344] Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck [20150203.231344] FATAL ERROR: Upgrade failed [20150203.231345] The "mysql" service is down. [20150203.231345] Unable to reset root MySQL password. at /usr/local/cpanel/scripts/securemysql line 151. [20150203.231345] The "mysql" service is down.
And almost in the same time in /var/lib/mysql/*err
150203 23:11:28 [Note] /usr/sbin/mysqld: Normal shutdown 150203 23:11:28 [Note] Event Scheduler: Purging the queue. 1 events 150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 325720 user: 'leechprotect' 150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 271 user: 'root' 150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 16 user: 'modsec' 150203 23:11:30 [Warning] /usr/sbin/mysqld: Forcing close of thread 9 user: 'eximstats' 150203 23:11:38 InnoDB: Starting shutdown... 150203 23:11:50 InnoDB: Shutdown completed; log sequence number 5619987215 150203 23:11:51 [Note] /usr/sbin/mysqld: Shutdown complete 150203 23:11:51 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended 150203 23:12:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 150203 23:12:32 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead. 150203 23:12:32 [Note] Plugin 'FEDERATED' is disabled. 150203 23:12:32 InnoDB: The InnoDB memory heap is disabled 150203 23:12:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins 150203 23:12:32 InnoDB: Compressed tables use zlib 1.2.3 150203 23:12:32 InnoDB: Using Linux native AIO 150203 23:12:32 InnoDB: Initializing buffer pool, size = 1.0G 150203 23:12:32 InnoDB: Completed initialization of buffer pool 150203 23:12:32 InnoDB: highest supported file format is Barracuda. InnoDB: Error: tried to read 16384 bytes at offset 0 49152. InnoDB: Was only able to read -1. 150203 23:12:49 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: [url=http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html]MySQL :: MySQL 5.5 Reference Manual :: 14.21.6 Operating System Error Codes InnoDB: File operation call: 'read'.
0
cPanelMichael

February 04, 2015 12:24
Hello :) The following error message is often an indicator of a failing hard drive: InnoDB: Error number 5 means 'Input/output error'.
Do you notice any error messages in /var/log/messages or /var/log/dmesg that would indicate a failing hard drive? Thank you.
0

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?