Thanks Johan. Yes, it shows the mysqld holding it open. Not suprising really
I guess. I did check the cron jobs and the history file searching for
something/someone who deleted it, but didn't find anything. Still, that is
what it looks like happend. I will move the sock file to /var/run/mysql so
it is out of the way.
On Tue, Dec 15, 2009 at 11:00 AM, Johan De Meersman <vegivamp@stripped>wrote:
> Presumably someone deleted it :-) You can try an 'lsof -U |grep mysql' to
> see if any processes still have it open. If the mysqld process still has it
> open, it's probably not the server.
> Why do you keep it in /tmp, btw ? My guess would be that someone (or some
> process) decided it was time to clean /tmp out.
> On Tue, Dec 15, 2009 at 4:46 PM, Keith Murphy <bmurphy@stripped>wrote:
>> Take one perfectly functional production server running 5.0.77. It has
>> up and running under load for quite some time. I am using xtrabackup for
>> backups and suddenly three or four days ago backup stop running.
>> Investigation shows that the socket file '/tmp/mysql.sock' is no longer
>> there. The mysql server itself is still functioning .. you can specify
>> --host=localhost instead of --socket=/tmp/mysql.sock so the mysql client
>> uses tcp/ip instead of the socket file to connect to the server.
>> - Permissions did not change on the /tmp directory..I checked.
>> - There are no errors in the .err log.
>> - No cron jobs clearing out /tmp.
>> - SHOW VARIABLES LIKE '%sock%' displays the proper socket location
>> Any thoughts? I have seen this type of thing occasionally before, but
>> taken the time to really investigate. I would just restart the server. I
>> will end up having to do so in this case, but I would really like to find
>> out WHY this happened. Is this is bug in the server code? I can't come up
>> with any other explanation. I would love for this to be explainable!
>> Chief Training Officer
>> Paragon Consulting Services
Chief Training Officer
Paragon Consulting Services