Possible mysql.sock problem | ERROR 2002 (HY000)

[jaymax]

Thanks !!!
Got it resolved after adding 
mysql_socket="/usr/tmp/mysql.sock" to the rc.conf file
Removing the /etc/my.cnf file as the aetting were redundant with those used
in the compilation
deinstalling and reinstalling both the server and the client



Matthew Seaman-2 wrote:
> 
> jaymax wrote:
> 
>> Direct start from script /usr/local/etc/rc.d/mysql-server start fails
>> also
>> 
>> And running /usr/local/bin/mysql ==>
>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket
>> '/usr/tmp/mysql.sock' (2)
>> 
> 
> There's a $mysql_socket rc.conf variable you need to set as well.
> 
>> Settings in rc.conf
>> 	mysql_enable="YES"
>> 	mysql_limits="YES"
>> 	mysql_dbdir="/disk02/db/mysql/DATA"
>> 	mysql_args=""
>         mysql_socket="/usr/tmp/mysql.sock"
> 
> (Although if /usr/tmp is set to mode 1777, what's the benefit of using
> that
> location rather than the default /tmp/mysql.sock ?)
> 
> Initially they were on their own file systems both ran into problems of
> restricted sizes and overflow condition.
>  
> 
> Judging by the complaints about 'update log no longer supported' I'm
> guessing that there is somewhere a my.cnf or a .my.cnf file filled with
> configuration settings appropriate to a much earlier version of MySQL.
> A good strategy is to grab one of the sample .cnf files from
> /usr/local/share/mysql (according to the capabilities of your server)
> copy that into ${mysql_dbdir}/my.cnf and edit to make any local 
> customizations.
> 
> Aparently  ignored after 
> 

-- 
View this message in context: http://old.nabble.com/Possible-mysql.sock-problem-%7C-ERROR-2002-%28HY000%29-tp27001411p27066296.html
Sent from the freebsd-questions mailing list archive at Nabble.com.