I keep having to get the mySQL.sock error fixed on my installation of movable type.  Is this a server issue, or is it something else?  I'd like to find a permanent solution.

What error?  Are you using the DBHost line in mt.cfg?

Got an error: Connection error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)


Then, my server admin rebuilds the sock, and it is ok for a few days.  They I will get the error again.

DBHost localhost

is what I use.

Well, if things are okay for a few days after your admin rebuilds the socket, then I'd think it's a server problem.

If you got the message consistently, I'd think perhaps the socket was in a non-standard location, in which case you'd be advised to use the DBSocket config line:

DBSocket /path/to/mysql.sock

My mysql.sock is gone after moving /var to another drive.  How can I recreate it?

Sorry I rebooted after fixing file perms all better DOH

whenever i try to load the mt.cgi or open up the comments box, i get this following error:

An error occurred: Connection error: Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)

my actual sock is located in /tmp; i was able to resolve the problem by creating /var/run/mysql/ and then symlinking the mysql.sock...i don't like doing it that way.

this all worked perfectly fine with just the /tmp/mysql.sock until my server rebooted itself do a storm last night.  at this point, there are two questions...

1. can i get MT to 'see' the /tmp/mysql.sock instead of the /var/run/mysql/mysql.sock?

2.  this happened to me right after i installed something as well, and i resolved it by uninstalling and reinstalling...i believe it might have been courier imap.  is there something in the system that it could have changed to modify an env var on where mysql.sock is really located...

my php scripts that read off the database are all working fine, if that makes a difference.