Solve the Problem of MySQL startup failure

From: http://1.1lifes.sinaapp.com /? P = 186

I am a newbie to Linux and installed software randomly. I found an article. Install MySQL to a specific file. However, after stress testing handlersocket, MySQL suddenly crash. Why cannot I start it! The folder where I installed MySQL is in/opt/yq. If it cannot be started, I will find the error log. However, because of the default method used by the installation file, I google it, the log file is indeed found under the data in the installation path. The file name is ***. err file, found that the content is very old, depressed. The error log for starting MySQL is not found here. Where is it? Continue searching. After Google finds that there will be related logs under/data/MySQL/. After that, it will find that there are data files besides the error log files and check the error logs:

111217 23:23:57 InnoDB: database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the. IBD files... InnoDB: restoring possible half-written data pages from the doublewrite InnoDB: Buffer... InnoDB: Last MySQL BINLOG file position 0 406839588, file name./mysql-bin.000012 111217 23:23:58 InnoDB: waiting for the background threads to start 111217 23:23:59 InnoDB: 1.1.8 started; log sequence number 3430959679 Handlersocket: Not listening for reads Handlersocket: Not listening for writes Handlersocket: initialized 111217 23:23:59 [note] recovering after a crash using MySQL-bin 111217 23:24:04 [Error] Error in log_event: read_log_event (): 'read error', data_len: 749, event_type: 23 111217 23:24:04 [note] Starting crash Recovery... 111217 23:24:04 [note] crash recovery finished. /Opt/yq/MySQL/bin/mysqld: disk is full Writing './MySQL-bin .~ REC ~ '(Errcode: 28). Waiting for someone to free space... (Keep CT up to 60 secs delay for server to continue after freeing disk space)

The red part is found. It turns out that the disk is full and it is dizzy! Ll-LH: Check the file size. The mysql-bin database backup file is too large. delete the file and restart the file to solve the problem. Haha! Good!