View source for Remove MySQL errors from "mysql error.log"

=== <h1>Remove MySQL errors from "mysql_error.log"</h1> ===
<hr>
<br>


<h2>Problem:</h2>
<b>"mysql_error.log"</b>
<br>
<pre>[Note] InnoDB: Completed initialization of buffer pool
161128 20:46:43 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
161128 20:46:43 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
161128 20:46:43 [Note] InnoDB: Retrying to lock the first data file
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
161128 20:48:57 [ERROR] InnoDB: Can't open './ibdata1'
161128 20:48:57 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
161128 20:48:57 [ERROR] Plugin 'InnoDB' init function returned error.
161128 20:48:57 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
161128 20:48:57 [ERROR] mysqld: Can't lock aria control file '/opt/zimbra/db/data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
161128 20:48:57 [ERROR] mysqld: Can't lock aria control file '/opt/zimbra/db/data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
</pre>



<h2>Solution:</h2>

'''Cause:''' Found two "innodb_force_recovery" parameter defined in my.cnf and many MySQL open processes found <br>
Removed "innodb_force_recovery=1" parameter from my.cnf file and killed all MySQL open processes.




Submitted by:  Navdeep Mathur