Symptoms and problems during MySQL Service Startup

Recently, a server has been configured and has been running for more than a month. However, MySQL was shut down unexpectedly recently, and the logs did not record any process.

So I started the MySQL service. The MySQL process is displayed in the Process Manager, but port 3306 is not enabled when I use netstat to view the port, and MySQL does not record any logs, even failures are not recorded. After MySQL is enabled, it should immediately occupy several hundred MB of memory. Now it only occupies a dozen MB, and it cannot be closed due to the problem of shutting down the MySQL service, if it is stuck there, you must kill it from the Process Manager. So it took a long time. Restarting the server, restoring the original MySQL database, uninstalling and reinstalling, and uninstalling the new version of MySQL have all done, but it has no effect.

When I was about to give up the problem, after a dozen minutes, I found it was ready and the port was enabled. So it does not matter. But a few days later, the problem occurs again, and this time, it takes a longer time to start.

So I was wondering what was going on. Suddenly I thought that MySQL would generate some temporary files in the C: \ WINDOWS \ Temp directory at startup. Will it be a problem here. Unexpectedly, due to permission settings problems, the session files are accumulated and not deleted, so there are 2 million session files. No wonder it is so slow to enable the folder. The problem is found, rename the temp folder (because there are too many files, it cannot be deleted), and create a new temp folder with the correct permissions. This restart is okay, haha.