MySQL socket link broke

[ChrisUpjohn]

Hi,

After restating my server last night for the heartbleed fix I went off to bed without any thought in mind that something had gone wrong until I woke up this morning and found the MySQL service was failing because it couldn't find the socket.

In order to fix it I had to re-link /var/lib/mysql/mysql.sock to /tmp/mysql.sock which I've never had to do in the entire time I've managed my own server.

Is there a reason this would have happened out of the blue?

 

[SS-Maddy]

Very hard guess. Did you explicitly set socket file in my.cnf ? Default is /tmp/my.cnf but in older systems only. Which is the OS version you are running ?

I googled to get an article related to the issue you mentioned http://www.mysqlab.net/knowledge/kb/detail/topic/configuration/id/5156

just my 2c. had this issue many times but never had a thought why. You have a very good intriguing mind !

 

[cPanelMichael]

Hello

It's difficult to pinpoint any specific reason why the file was missing. It sounds like the /tmp partition might have been cleared, resulting in the removal of /tmp/mysql.sock.

Thank you.

 

[ChrisUpjohn]

I've never explicitly set a socket path as I like to stay true to the default config apart from the minor optimisations here and there which have worked fine up until the mysql service decided to hit the fan last night.

OS: CentOS release 6.5 (Final)
MySQL: Ver 14.14 Distrib 5.6.16

Hopefully I can work out why this happened, its bugging the absolute crap out of me.

- - - Updated - - -

Hello

It's difficult to pinpoint any specific reason why the file was missing. It sounds like the /tmp partition might have been cleared, resulting in the removal of /tmp/mysql.sock.

Thank you.

My tmp folder has cleared itself before without any issue which is why I'm confused this issue occurred out of the blue, however I did only just update to MySQL 5.6.16, is it possible that WHM behaves differently with this version compared to 5.5?

- - - Updated - - -

Just to clarify, by updating the MySQL server I meant last month

 

[cPanelMichael]

It seems like the issue happened during the reboot of your server. Have you experienced this problem anymore since the reboot?

Thank you.