InnoDB crashed

Sometimes, our databases got corrupted and innoDB crashed in the server. Due to this, MySQL service won't restart and following message:

Starting MySQL..The server quit without updating PID file (/var/lib/mysql/my.server.com.pid).[FAILED] or MySQL server PID file could not be found!

In such situation, you will have to start MySQL with InnoDB in force recovery mode using the following steps:

Step 1. Stop MySQL service

Step 2. Backup /var/lib/mysql directory

Step 3. Add the following line into /etc/my.cnf: innodb_force_recovery = 4

Step 4: Restart MySQL. Your database will now start, but with innodb_force_recovery, all INSERTs and UPDATEs will be ignored.

Step 5: Dump all tables

Step 6: Shutdown database and delete the data directory. Run mysql_install_db to create MySQL default tables

Step 7: Remove the innodb_force_recovery line from your /etc/my.cnf file and restart the database. (It should start normally now)

Step 8: Restore everything from your backup

Comments

Post a Comment

Popular posts from this blog

SVN: File remains in conflict

This error occurs when you didn't update the SVN and try to commit changes or, someone has made changes to this file that are conflicting with your changes. There are two ways to handle this situation. Either, you can revert back the changes you want to commit and then, update the SVN and after that make the changes again and commit. The other way is, you need to resolve the conflicted files one by one. You can keep all the conflicted files in a folder and resolved it at once. >> Revert the changes steps: svn revert . -R svn up >> Resolve the conflicted files: svn resolved <file_name>
Read more

HowTo: Enable extended logging for exim

When troubleshooting mail or attempting to discover the source of spam originating from your server, it is often useful to enable extended Exim logging. You can enable extended logging for exim though your shell prompt as well as through WHM interface. I am giving the steps for both ways one by one: 1. Through shell prompt: 1. Open exim.conf 2) Find this: hostlist auth_relay_hosts = * 3) After hostlist auth_relay_hosts = * add the following: log_selector = +address_rewrite +all_parents +arguments +connection_reject +delay_delivery +delivery_size +dnslist_defer +incoming_interface +incoming_port +lost_incoming_connection +queue_run +received_sender +received_recipients +retry_defer +sender_on_delivery +size_reject +skip_delivery +smtp_confirmation +smtp_connection +smtp_protocol_error +smtp_syntax_error +subject +tls_cipher +tls_peerdn 4) The final result should look like this hostlist auth_relay_hosts = * log_selector = +address_rewrite +all_parents +arguments +connecti
Read more

12 tweakings for WHM/cPanel to speed up WordPress

   1. Turning Mailman off – WHM >> Server Configuration >>  Tweak Settings and turning it off    2. Number of minutes between mail server queue runs (default is 60) – Setting it 120    3. Default catch-all/default address behavior for new accounts” to fail    4. Boxtrapper Spam Trap and SpamAssassin Spam Box delivery – off    5. Analog Stats – off    6. Conserve Memory at the expense of using more cpu/diskio – turn on    7. WHM >> Service Configuration >> FTP Server Configuration – Check ‘no’ to ‘allow anonymous logins and ‘no’ to ‘anonymous uploads’    8. WHM >> cPanel >> Manage Plugins – install spamdconf – then go to ‘Setup Spamd Startup Configuration’ – select option 2 ‘Maximum Children” to 2′    9. Run your cron jobs at off peak hours.   10. Install e Accelerator PHP accelerator (Recompile Apache with eAccelerator)   11. Compiling Apache with mod_deflate Gzip Module   12. Running Apache with the thread-based “Worker” MPM
Read more