A ps -A | grep mysqld reveals:
6563 ? 00:00:00 safe_mysqld
6594 ? 00:00:00 mysqld
6596 ? 00:00:02 mysqld
6597 ? 00:00:00 mysqld
So I appear to have multiple instances of mysqld running AS WELL as
safe_mysqld. Ghod only knows what people have been doing to my system.
Since it is a test system I think I will do a shutdown/restart of it and
see what we get.
|---------+---------------------------->
| | Ranga Nathan |
| | <[EMAIL PROTECTED]|
| | l.com> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 01/14/2004 11:49 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: mysql
|
>------------------------------------------------------------------------------------------------------------------------------|
I had the same issue. We had re-IPLed the Linux LPAR and possibly it got
shutdown uncleanly.
mysqld did not work but safe_mysqld did.
I can connect as any user now.
My guess is that the mysqld daemon is not up. When it tries to come up it
checks its pid fild and sock file. If it is already there, it thinks there
is another process using the socket or mysqld is already running.
James Melin <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
01/14/2004 07:57 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: mysql
I have a user that wants to use mysql on one of my lpars.
I have an issue where root can issue the mysql command from shell and get
into the mysql command line interface. When a non-root user tries, I get
this:
/ > mysql
ERROR 2002: Can't connect to local MySQL server through socket
'/tmp/mysql.sock' (2)
What perchance did I miss? I have pathing in profile .local to /usr/sbin
so
things get picked up there... but shouldn't this have worked out of the
box
on a suse 7.2 installation?
