mysql.sock

January 12th, 2008 | by jg3 |

So this is an old server. It is slow and it has ailments that aren’t worth the effort to fix, since there’s a new box to replace it in the next rack over. It’s just …. finding the time to make the leap has been hard and doing it piece-meal, daemon by daemon, is slow. Anyway, it wasn’t completely surprising to me when J’fy called me yesterday and told me that my mailserver was busted. But when I looked and saw that the was returning “Error: Can’t connect to database.” I thought that the two must surely be related. (spoiler: they weren’t).

Looking around, I got really scared for a minute because I saw the SANS story about a mass attack on SQL servers but then realized that (at the time of the attack) it was thought to only impact MS SQL servers.

In the end, the problem was that the <code>/tmp/mysql.sock</code> file was gone. Executing a simple <code>/usr/local/etc/rc.d/mysql-server.sh stop</code> && <code>/usr/local/etc/rc.d/mysql-server.sh start</code> didn’t fix it and I was stumped for exactly why. However, executing <code>/usr/local/etc/rc.d/mysql-server.sh restart</code> recreated the socket and all became well in happy land once more.

The end. time for breakfast.

Filed under:

Related stuff

You must be logged in to post a comment.