MySQL/MariaDB Does Not Start After Changing innodb_log_file_size#
Problem#
It is recommended to increase the value of innodb_log_file_size (depending on RAM) for a better performance of MySQL/MariaDB. After this change the service is restarted but only an error message appears:
1 2 3 4 5 6 |
|
Solution#
Terminate the service in a clean manner and remove all existing logs when changing this option, as described in a more comprehensive answer at StackExchange:
1 2 3 4 |
|
MySQL/MariaDB creates the logs again automatically. This can take some time in bigger databases. The new value for innodb_log_file_size is now active.