Re: /tmp/mysql.sock dissapears

2008-03-01 Thread Ian
Hi, Okay, ill remove the extra log then. The problem isnt that the socket doesn't get created, its that it randomly disappears when mysql has been running for weeks already. So, /tmp's permissions are correct, and everything works for a undecided amount of time, then it just disappears and mysql

Re: /tmp/mysql.sock dissapears

2008-02-29 Thread Sebastian Mendel
Ian schrieb: Hi, I am running mysql 5.0.45 on freebsd 4.11 and for some strange reason /tmp/mysql.sock keeps on disappearing and we are forced to kill -9 mysql and restart it causing db corruptions as there is no other way of telling it to stop once that file has gone. I have tried to find any

Re: /tmp/mysql.sock dissapears

2008-02-29 Thread Ian
Hi, I wouldnt have thought so but whenever that file is missing and try the stop/restart it just sits at the waiting for pids part of the stop loop (where it lists the pids), and it never stops the server - i have left it for over an hour and it never stops - just keeps on in the stop loop.

Re: /tmp/mysql.sock dissapears

2008-02-29 Thread Ian
Hi, I dont know about network, but I know using php we cant access anything in MySQL once the file is gone. When it happens again, ill be sure to check network. Cheers Ian On Fri, Feb 29, 2008 at 12:54 PM, Sebastian Mendel [EMAIL PROTECTED] wrote: Ian schrieb: Hi, I wouldnt have thought

Re: /tmp/mysql.sock dissapears

2008-02-29 Thread Sebastian Mendel
Ian schrieb: Hi, I wouldnt have thought so but whenever that file is missing and try the stop/restart it just sits at the waiting for pids part of the stop loop (where it lists the pids), and it never stops the server - i have left it for over an hour and it never stops - just keeps on in the

/tmp/mysql.sock dissapears

2008-02-28 Thread Ian
Hi, I am running mysql 5.0.45 on freebsd 4.11 and for some strange reason /tmp/mysql.sock keeps on disappearing and we are forced to kill -9 mysql and restart it causing db corruptions as there is no other way of telling it to stop once that file has gone. I have tried to find any reason why this

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Vidal Garza
how do you start up? you can start up from scrip. #!/bin/sh id=02 ip=192.168.0.42 sockfile=/tmp/mysql$id.sock user=mysql datdir=/var/db/mysql$id port=3306 /bin/sh /usr/local/bin/mysqld_safe --user=$user --datadir=$datdir --bind-address=$ip --port=$port --sock=$sockfile Ian escribió: Hi,

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Ian
Hi, We use the following sh script to start (its the default one when installed) cat /usr/local/etc/rc.d/mysql-server.sh #!/bin/sh # # $FreeBSD: ports/databases/mysql50-server/files/mysql-server.sh.in,v 1.32006/03/07 16:25:00 ale Exp $ # # PROVIDE: mysql # REQUIRE: LOGIN # KEYWORD: shutdown #

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Vidal Garza
Its for test. put the log file on my.cnf and tellus what going on my.cnf ... log-error=/var/db/mysql/Server_Error.log Ian escribió: Hi, We use the following sh script to start (its the default one when installed) cat /usr/local/etc/rc.d/mysql-server.sh #!/bin/sh # # $FreeBSD:

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Steve Bernacki
Does the system in question have some type of /tmp cleaner script that might be removing the socket file? Check /etc/crontab and root's crontab (crontab -l) Steve

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Ian
Hi, Okay, I have added that and will wait and see when it happens again if there is anything in that log. Just out of interest, does that log show anything different to the /var/db/mysql/hostnameofunit.err file ? Cheers Ian On Thu, Feb 28, 2008 at 8:44 PM, Vidal Garza [EMAIL PROTECTED] wrote:

Re: /tmp/mysql.sock dissapears

2008-02-28 Thread Ian
Hi, No, there is nothing in there cleaning /tmp. Mind you, further investigating there are still some temp files in there from last year - so the directory isnt getting wiped clean. Thanks :) On Fri, Feb 29, 2008 at 3:36 AM, Steve Bernacki [EMAIL PROTECTED] wrote: Does the system in question