The socket file is created by mysqld when it starts, and goes away when mysqld shuts down. That is, you have no socket file because mysqld is not running, not the other way around.

You appear to be trying to start mysqld as OS user admin. Normally, only root has the power make the switch to user mysql called for by --user=mysql. Thus, mysqld starts running as user admin, who has no permission to touch data files owned by mysql.

Try `sudo bin/mysqld_safe --user=mysql --log`.  Better yet, do

  sudo -v
  sudo bin/mysqld_safe --user=mysql --log &

Michael

Kenji LEFEVRE wrote:

Hello,

OS : macos X 10.3
mysql version 4.0.21, for apple-darwin6.8 (powerpc)

it's seems that after my last crash,
the socket of mysql '/tmp/mysql.sock' has
been deleted
(and i have read afterwards that it should have
been protected with a sticky bit)
i thought that restarting mysql daemon would fix
this problem but i encounter the following problem :

when starting Raspoutine3:/usr/local/mysql admin$ bin/mysqld_safe --user=mysql --log

i get touch: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied
chown: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied
Starting mysqld daemon with databases from /usr/local/mysql/data
bin/mysqld_safe: line 302: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied
rm: /usr/local/mysql/data/Raspoutine3.local.pid: Permission denied
bin/mysqld_safe: line 1: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied
tee: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied
041110 14:03:44 mysqld ended
tee: /usr/local/mysql/data/Raspoutine3.local.err: Permission denied


though user 'mysql' is the owner of directory '/usr/local/mysql/data/'
indeed
Raspoutine3:/usr/local/mysql admin$ ls -ld data/
drwxr-x---  13 mysql  wheel  442 10 Nov 00:34 data/

How can i fix this two problems :
recovering socket and starting daemon

thanks in advance, Kenji.



-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to