MySQL suddenly fails to start

Today to work, open the test virtual machine, but found that MySQL can not start. Then, look at the logs and configuration files for MySQL. But there is no useful information found in the MySQL error log. We all know that database systems, often the most demanding applications, are not only demanding CPU memory (especially memory), but have more stringent requirements for hard drive speed (I/O) and size. So, I first see if the hard disk space is sufficient. Sure enough, the disk space occupancy rate is absolutely.

Then, use the du-ms/* command to find out which directory occupies the most. The results see is the/var directory occupies 15G, and then with du-h--max-depth=1|grep g|sort-n command, layers in-depth to find the/var/log directory Docker occupies the most, because it is a test machine, So just delete the Docker log file and fix it.

In addition, Docker runs for a long time, and the log at the end of the Json.log in/var/lib/docker/containers also occupies space, so it has to be cleaned up regularly.

This article from the "Little Flash" blog, declined to reprint!

MySQL suddenly fails to start