Re: Possible mysql.sock problem | ERROR 2002 (HY000)

2010-01-07 Thread 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.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Possible mysql.sock problem | ERROR 2002 (HY000)

2010-01-07 Thread Michael Powell
jaymax wrote:

 
 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
 
[snip]

The new default location for my.cnf as installed by the ports system is 
now /usr/local/etc, although MySQL will still find it if it is in 
mysql_dbdir.
 
MySQL startup will skip it if it has world write permissions on it, more 
specific info is in the docs. I just chmod mine 444 when I'm done with it as 
it is something I don't change once configured. But if you have two of them 
the permissions thingy can be the cause of why it skips over and ignores the 
one you think it should be using.

-Mike


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Possible mysql.sock problem | ERROR 2002 (HY000)

2010-01-03 Thread jaymax

 HELP! NEEDED URGENTLY

7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009
installed /usr/ports/databases/mysql54-server from ports

Installation seemed to go to completion - OK
but 
# /usr/local/bin/mysql_install_db - ERRORS listed as ==
Installing MySQL system tables...
091230 13:35:02 [ERROR] The update log is no longer supported by MySQL in
version 5.0 and above. It is replaced by the binary log.
091230 13:35:02 [Note] Falcon: unable to open system data files.
091230 13:35:02 [Note] Falcon: creating new system data files.
091230 13:35:03 [Warning] Forcing shutdown of 2 plugins
OK
Filling help tables...
091230 13:35:04 [ERROR] The update log is no longer supported by MySQL in
version 5.0 and above. It is replaced by the binary log.
091230 13:35:05 [Warning] Forcing shutdown of 2 plugins
OK

Then running /usr/local/bin/mysqld_safe  ==
091230 17:45:16 mysqld_safe Logging to
'/disk02/db/mysql/DATA/ax.lall.com.err'.
091230 17:45:16 mysqld_safe Starting mysqld daemon with databases from
/disk02/db/mysql/DATA
091230 17:45:16 mysqld_safe mysqld from pid file
/disk02/db/mysql/DATA/ax.lall.com.pid ended

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)


Tried various strategies for mysql.sock problems as suggested in thre forum
but can't seem to get any to work, if someone has any ideas they will be
much appreciated.

Thanks!

PS:
Settings in rc.conf
mysql_enable=YES
mysql_limits=YES
mysql_dbdir=/disk02/db/mysql/DATA
mysql_args=

In my.cnf file
[client] 
socket=/usr/tmp/mysql.sock
[mysqld] 
socket=/usr/tmp/mysql.sock

/usr/tmp permissions set to drwxrwxrwt

datadir = mysql:mysql ownership

HELP! NEEDED URGENTLY

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

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Possible mysql.sock problem | ERROR 2002 (HY000)

2010-01-03 Thread Matthew Seaman

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 ?)


In my.cnf file
	[client] 
	socket=/usr/tmp/mysql.sock
	[mysqld] 
	socket=/usr/tmp/mysql.sock


Is this the only my.cnf file on the system?  There are several places
where MySQL will pick up a my.cnf file: directly from the mysql_dbdir
or /usr/local/etc/my.cnf [The rc.d/mysql-server script automatically
adds ${mysql_dbdir}/my.cnf to the list of locations]

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.


Cheers,

	Matthew 


--
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
 Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature