Skip to main content
6 events
when toggle format what by license comment
Jan 31 at 17:30 answer added Cpt.Whale timeline score: 0
Jan 29 at 19:57 comment added Chris @Cpt.Whale thanks, bud...nothing interesting output from the set... call. I theorize Docker changed some default directory where the sock file is being referenced (ie, from default /var/run... to the /tmp location)...nothing turned up doing a find for the location, do you know where the socket directory is specified in some mysql config file so I can change it back to where it actually exists?
Jan 29 at 16:40 comment added Cpt.Whale The default directory is where the sock file currently exists: /var/run/mysqld/mysqld.sock. The mysql command error says it's checking for /tmp/mysql.sock, so I'm curious if set | grep MYSQL shows something unexpected. You might just need to link it like ln -s /private/var/mysql/mysql.sock /tmp/mysql.sock like in the answer here: stackoverflow.com/a/18418296/7411885 there are some other good troubleshooting steps in there as well
Jan 27 at 0:34 comment added Chris @Cpt.Whale The server is running. Only see an auto.cnf file (and has no directory related to one in question). Do you know what the default path is supposed to be? Possible Docker altered this I suppose (and the source of the issue, as this worked until I used Docker and MySQL image)
Jan 26 at 20:58 comment added Cpt.Whale Check if the mysql process is running (ps ax | grep mysql). looks like you can use the --socket option, the MYSQL_UNIX_PORT environment variable, or various .cnf files to get mysql to check a different socket path. Since the command looks like it's checking a non-default path, maybe docker or some other process updated that env?
Jan 26 at 20:08 history asked Chris CC BY-SA 4.0