Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm getting a bizarre error running my mysql daemon as the user 'mysql' here is what the command spews out, now I've checked and the instance isn't running already :S So, I have no idea why it's displaying this output:

120729 18:54:28 [Note] Plugin 'FEDERATED' is disabled.
120729 18:54:28 InnoDB: The InnoDB memory heap is disabled
120729 18:54:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120729 18:54:28 InnoDB: Compressed tables use zlib 1.2.5
120729 18:54:28 InnoDB: Using Linux native AIO
120729 18:54:28 InnoDB: Initializing buffer pool, size = 128.0M
120729 18:54:28 InnoDB: Completed initialization of buffer pool
120729 18:54:28 InnoDB: highest supported file format is Barracuda.
120729 18:54:28  InnoDB: Waiting for the background threads to start
120729 18:54:29 InnoDB: 1.1.8 started; log sequence number 2929794
120729 18:54:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
120729 18:54:29 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
120729 18:54:29 [Note] Server socket created on IP: '0.0.0.0'.
120729 18:54:29 [ERROR] Can't start server : Bind on unix socket: No such file or directory
120729 18:54:29 [ERROR] Do you already have another mysqld server running on socket: /var/mysql/mysql.sock ?
120729 18:54:29 [ERROR] Aborting

120729 18:54:29  InnoDB: Starting shutdown...
120729 18:54:30  InnoDB: Shutdown completed; log sequence number 2929794
120729 18:54:30 [Note] mysqld: Shutdown complete

Any help is greatly appreciated, thanks guys!

share|improve this question
2  
Did you try to configure another socket file? Does the file exist and have the correct rights? –  Wolfram Jul 29 '12 at 17:03
    
Yeh, the file is there, but still getting this error :/ –  Conner Stephen McCabe Jul 30 '12 at 1:52
    
That's tough. The only info we got is "no such file" and "is there another mysqld running". You say both are not the cause. Try changing the socket file to a completely new location. –  Wolfram Jul 30 '12 at 13:26
    
Yeh, there's very little error outputs :/ it's baffling me, I've been wading through each error and I'm at this point, but my knowledge of MySQL's requirements is limited, so it's a learning experience I guess :P But yes, it's pretty difficult, I'm getting another error now, to do with 'World Writable Config Files'? And I have no clue what these are :S –  Conner Stephen McCabe Jul 30 '12 at 15:57
    
World-writable means that they have permissions set that allow everyone to write that file (user, groups, other => the world). These files get ignored as they may be altered by a not really authorized person. Try chmod 755 /etc/my.cnf or whatever file is ignored. –  Wolfram Jul 30 '12 at 16:39
add comment

migrated from stackoverflow.com Aug 23 '12 at 4:58

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 0 down vote accepted

The problem is clear in the error messages:

120729 18:54:29 [ERROR] Can't start server : Bind on unix socket: No such file or directory
120729 18:54:29 [ERROR] Do you already have another mysqld server running on socket: /var/mysql/mysql.sock ?

Most likely that socket doesn't actually exist. This is probably a simple typo.

By default the socket is located at /var/lib/mysql/mysql.sock on a Fedora box. So, in your /etc/my.cnf file you should have:

socket=/var/lib/mysql/mysql.sock
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.