Looks like the sysadmin was re-orging the partitions and changed the 
permissions for /tmp from 1777 to 777. Mike Burns helped out. Thanks Mike.

I guess that this mysql.sock is the pipe used by mysql.




Brian Reichert <[EMAIL PROTECTED]>

03/17/2004 08:58 AM

 
        To:     Ranga Nathan <[EMAIL PROTECTED]>
        cc:     [EMAIL PROTECTED]
        Subject:        Re: [Boston.pm] OT - MySQL crashed?


On Wed, Mar 17, 2004 at 07:48:09AM -0800, Ranga Nathan wrote:
> 
> 
> 
> 
> mysql seems to have crashed on a box running my application. However I 
dont
> see any signs. When I tried to bring it up using safe_mysqld (tried with
> sudo as well as mysql root) I get this error:

Well, OS, version, etc.  WOuld help.


>               ======================
> 040317 10:40:09  mysqld started
> 040317 10:40:09  Can't start server : Bind on unix socket: Permission
> denied
> 040317 10:40:09  Do you already have another mysqld server running on
> socket: /tmp/mysql.sock ?
> 040317 10:40:09  Aborting
> 
> 040317 10:40:09  /usr/local/libexec/mysqld: Shutdown Complete
> 
> 040317 10:40:09  mysqld ended
>                =======================
> 
> There is no /tmp/mysqlchk. myisamchk did not report any serious problem
> with tables. How does mysql think that there is a daemon already 
running?

It's not asking about /tmp/mysqlchk, it's asking about /tmp/mysql.sock.

Does 'ps' reveal another mysql server running?  Does 'lsof' or 'fstat'
reveal '/tmp/mysql.sock' in use by any processes?


> 
> Any clues will be helpful.
> 
> _______________________________________________
> Boston-pm mailing list
> [EMAIL PROTECTED]
> http://mail.pm.org/mailman/listinfo/boston-pm

-- 
Brian Reichert <[EMAIL PROTECTED]>
37 Crystal Ave. #303                                             Daytime 
number: (603) 434-6842
Derry NH 03038-1713 USA                                          BSD 
admin/developer at large 



_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm

Reply via email to