Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about deleting mysql-bin logs that cause mysql to fail to start. Many people may not know much about it. In order to let you know more, Xiaobian summarizes the following contents for you. I hope you can gain something according to this article.

Today, I transferred the forum from the old server to the new Cloud Virtual Machine and found that the database directory log file mysql-bin.000** was very large. I deleted it without thinking, but mysql could not be started. A lot of information on the Internet is to comment out log-bin=mysql-bin in my.cnf. However, it still could not be activated. It took me a long time to find out that binlog_format=mixed needs to be commented out. I don't know if it's because of mysql version or lnmp installation package, so I need to comment one more line. Write it out in the hope that it will help others who encounter the same problem, so as not to spend more time.

Solution:

Edit my.cnf (usually in etc directory)

Log-bin=mysql-bin is OK. (preceded by a #)

If not, please comment out binlog_format=mixed as well!

Start mysql: /etc/init.d/mysql start

/etc/init.d/mysql restart

After reading the above, do you have any further understanding of the solution to deleting mysql-bin logs that cause mysql to fail to start? If you still want to know more knowledge or related content, please pay attention to the industry information channel, thank you for your support.

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.