MySQL error

[Pete Nesbitt]

On November 8, 2004 04:50 pm, J G wrote:
> Hi all,
>
> just installed Mysql binaries.
>
> When i try to start Mysql using the mysql_safe
> command, i get the message:
>
> [root at palrhsrv /]# /usr/bin/mysqld_safe &
> [1] 18547
> [root at palrhsrv /]# Starting mysqld daemon with
> databases from /var/lib/mysql
> STOPPING server from pid file
> /var/lib/mysql/palrhsrv.pid
> 041108 16:44:48  mysqld ended
>
>
> [1]+  Done                    /usr/bin/mysqld_safe
>
> ************************************
>
> then, when I start the command:
>
> [root at palrhsrv bin]# ./mysqladmin create testDB
> ./mysqladmin: connect to server at 'localhost' failed
> error: 'Can't connect to local MySQL server through
> socket '/var/lib/mysql/mysql.sock' (2)'
> Check that mysqld is running and that the socket:
> '/var/lib/mysql/mysql.sock' exists!
>
>
> I looked under the var/lib/mysql and obviously the
> mysql.sock does not exist.
>
> I changed permissions under /var/lib/mysql to chown -R
> mysql and chrgp to daemon.
> Still getting the same errors.
>
> any help?
>
> thanks


Hi,
I am no mysql expert but it would appear from reading above that the 
mysqladmin failure makes sence as the mysqld daemon was not running. That 
kind of failure (start and immediately stop) is often a permission issue 
creating/writing a log or pid or some related file.

-when you changed "permissions' on /var/lib/mysql  to be owned by mysql, did 
you also ensure the dir is writeable by mysql? Isn't the group 'mysql' as not 
'daemon'?

-is there anything in /var/log/mysqld.log or /var/log/messages ?

-make sure  /var/log/mysqld.log is writeable by the mysql user (probably 
mysql)

-that seems like strange place for a pid file, they usually go in /var/run 

Hope something there helps.
-- 
Pete Nesbitt, rhce