While repeatedly running migrations and importing SQL files with Laravel, and interrupting them recklessly, MySQL started acting up.

Solution

It was resolved by setting the log size in the MySQL configuration file.

innodb_log_file_size=5M

Thoughts

Let's avoid reckless actions!

References

• "Plugin 'InnoDB' registration as a STORAGE ENGINE failed" error prevents MySQL service from starting

• Changing innodb_log_file_size casually can be fatal