Re: MySQL Socket Error

[Rick James]

Try not to stop mysqld abruptly. It will leave behind the 'sock' file. This confuses the next attempt to run mysqld into thinking that mysqld is still running.

Normally (on *nix), /tmp/ is cleared out on reboot. Take advantage of that by putting the sock file in /tmp/. Then, if you do have an unexpected reboot, the sock file will be removed and mysqld can start.

Disk full is unlikely to cause "too many connections". The usual cause for this is your application failing to disconnect.

SHOW VARIABLES LIKE 'max_connections';
SHOW GLOBAL VARIABLES LIKE 'wait_timeout';