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

This article mainly explains "the solution to the failure of starting mysql server". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn the solution to the failure of starting mysql server.

Failed to start mysql server, check / var/log/mysqld.err

080329 16:01:29 [ERROR] Cant start server: Bind on unix socket: No such file or directory

080329 16:01:29 [ERROR] Do you already have another mysqld server running on socket: / var/run/mysqld/mysqld.sock?

080329 16:01:29 [ERROR] Aborting

080329 16:01:29 InnoDB: Starting shutdown...

080329 16:01:30 InnoDB: Shutdown completed; log sequence number 0 4646872

080329 16:01:30 [Note] / usr/sbin/mysqld: Shutdown complete

I was puzzled. Later, I checked the / var/db/pkg/dev-db/mysql-5.0.56/CONTENTS file, or executed equery f mysql (the two methods are not applicable for Gentoo release). I learned that the installation file contained / var/run/d, but this directory did not exist. I recalled that I had emptied the / var/run directory before, and I always thought that the following contents were created dynamically. After deletion, I could restart the system. That doesn't seem to be the case for mysql.

Create this directory and chown to resolve the problem.

# mkdir / var/run/mysqld

# chown mysql:mysql / var/run/mysqld

Thank you for your reading, the above is the content of "the solution to the failure of starting mysql server". After the study of this article, I believe you have a deeper understanding of the solution to the failure of starting mysql server, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

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.