Hassan Schroeder wrote:
Mark Sargent wrote:
ok, I don't fully understand why, but, mysql is still installed in /usr/bin. What I've done, just for now, is renamed mysql in that dir to mysqlold. I've added /usr/local/mysql/bin to my path. I then tried the cmd mysql and also ./mysql from within the dir /usr/local/mysql/bin, and after entering the correct password, I get the following,
[EMAIL PROTECTED] bin]# ./mysql -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
If I run ./usr/bin/mysqlold I can connect. What am I not understanding with this..?
If it were me, I'd remove all traces of mysql* anything from the system and start fresh. :-)
But in any case, which mysqld process is now running? I'm guessing it's the old one. If so, kill it, and start up your new version using an unambiguous path (e.g., /usr/local/mysql/bin/mysqld_safe).
Then try to connect with your new client.
HTH,
Hi All,
yeah, I'm seriously considering removing all trace of mysql. The startup script points to /usr/local/mysql/bin/mysqld_safe. That was why I was having the original problem. Running the latest mysql shouldn't be experiencing connection problems. What I don't understand, is, the old mysql can connect, but not the latest. Weird. Cheers.
Mark Sargent.
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
