Shulou(Shulou.com)06/02 Report--

In this issue, the editor will bring you solutions to the failure of MYSQL startup and the standardized configuration of MYSQL parameters. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.

The thing is, I don't know about some MYSQL servers before historical reasons, but I am busy with later work and have no time, and these servers have no problems. Recently, I began to straighten out these MYSQL and accidentally found that a server could not start after adding log-bin parameters, so write this article to analyze the reason why you cannot start after adding a normal parameter MYSQL.

The place to log out is what I added later.

The historical reason is that the previous MYSQL basically did not even start the bin log of MYSQL, so to start multi-source replication this time, you must open log-bin, but as long as you open log-bin, the following error message will be displayed.

And the weird thing is that there won't be any error messages in error log.

Well, from this point of view, it shows that MYSQLD closed the my.cnf file directly before it could record errors, so it needs to be started by command line, and non-command line startup mode may not be able to troubleshoot errors for the time being.

Start directly on the command line

The first error prompt is that mysqld started using the root account, which is a common sense problem. Generally, it is not allowed to use root to start and operate MYSQL, but it is already in this state, so you need to add a parameter to let MYSQL continue to run.

Need to add the user=root parameter to the configuration file

We started MYSQL again and found that it still couldn't start.

The main reason why server-id cannot be started in this prompt is that binlog cannot be started because there is no binlog in the configuration.

After adding the server_id parameter, the server can start normally.

Later, according to some later requirements, the following parameters are added, and MYSQL is not reporting an error.

Through this incident, we can see that MYSQL is different from other databases, especially in terms of configuration parameters, it seems that one parameter may be missing, and two parameters may not be a big deal for a MYSQL with more than 400 configuration parameters, but the configuration parameters of MYSQL are ring by ring, so it is necessary to understand the basic or commonly used MYSQL parameters.

At the same time, generally speaking, I recommend that the configuration of MYSQL should have a template of parameters, and you can make some necessary comments according to the necessity of the parameters, or configure several different templates according to the different requirements of MYSQL. And temporary patchwork of MY.CNF is not recommended.

So the standardization of MY.CNF is still very necessary.

The above is the solution to the failure of MYSQL startup and the standardized configuration of MYSQL parameters shared by Xiaobian. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.