Solution to the problem that the configuration file my.cnf in MySQL cannot be started due to permission issues

This article mainly introduces the relevant solution process for the failure to start the MySQL configuration file my.cnf due to permission problems. It is shared for your reference and learning. Let's take a look at the detailed introduction below:

Problem Description

MySQL cannot start and reports the following error:

Problem Analysis

Checking the MySQL error log, I found the following error (prompting that the host table of the MySQL library cannot be opened):

View the /etc/my.cnf configuration file:

Go to the directory where the MySQL database is located to check whether the table exists:

I found that the host table of the MySQL library does exist, so why does it say that it does not exist?

The problem should be with the /etc/my.cnf file. You can also see the warning message from the first screenshot (/etc/my.cnf is ignored)
Check the file permissions:

The original file permission was set to 777, which was ignored by MySQL due to security issues. So when I queried the default database storage path, I found that there was no host table for the MySQL library, which caused the startup to fail:

Solution

Change the permissions of /etc/my.cnf to 644, and then start MySQL:

Summarize

The above is the full content of this article. I hope that the content of this article can bring some help to your study or work. If you have any questions, you can leave a message to communicate. Thank you for your support of 123WORDPRESS.COM.