--On Monday, January 28, 2002 04:11:53 PM -0600 Ed Carp <[EMAIL PROTECTED]>
wrote:
>> --On Monday, January 28, 2002 11:52:08 AM -0600 Ed Carp <[EMAIL PROTECTED]>
>> wrote:
>>
>> > Hi, Bill! Did you ever get this issue resolved? I've got the same
>> > problem - MySQL starts, but no clients can connect, not even
>> mysqladmin.
>> > TIA :)
>>
>> I have not completely figured out what the problem is and I never got a
>> response from any one else on the list. I can tell you it looks like a
>> mutex problem between two threads. We have followed it down into
>> pthreads
>> where it seems to be stuck. The external symptom we see is that
>> the MySQL
>> server does not open any of the databases.
>>
>> The really bad news is that it is not a MySQL problem so
>> reinstalling MySQL
>> does nothing to fix it. The worse news is that the MySQL server does not
>> give you a clue what the problem is.
>
> I'm wondering if we have the same problem. My main symptom is that I
> can't connect with *any* client - when I do a "telnet localhost 3306", I
> can connect, but MySQL doesn't send anything back.
Sure sounds like the same problem to me. What you see when you look at the
system when you start mysql up is something like:
%ps -ef | grep mysql
root 25104 1 0 Jan18 ? 00:00:01 [safe_mysqld]
root 25137 25135 0 Jan18 ? 00:00:00 [mysqld]
root 25135 25104 0 Jan18 ? 00:00:00 [mysqld]
root 25138 25137 0 Jan18 ? 00:00:00 [mysqld]
Now look at the open files with lsof, i.e.
lsof -p 25104,25137,25135,25138
On my broken system I don't see any db files open, not mysql, not my local
databases. When I do the same thing on a working system I see db files
opened by all processes except safe_mysqld. Note, that mysql is running as
root on my broken system. We wanted to eliminate permission problems as we
did our research.
What seems to be happening is that the "open" of the db hangs. So, when
you attempt to connect with a client, mysql tries to look at the grant
tables and hangs waiting for access. This is just a guess though.
We had a Linux guru look at the version of mysql on this system that we
compiled with debug. I got information about the debugging session third
hand and really don't have any details other than the problem appeared to
be in pthreads. I am not so sure pthreads is at fault other than a
dead-lock condition exists and it is not detecting it and blowing one of
the stuck processes away.
I'll post if I find out anything else, but right now we are pretty much
stuck. At this point the only sure way I know to over come this problem is
to wipe the disk and reinstall Linux. It is not affecting our production
only because we were just about to move to newer systems when we were
hacked. The hacked system is a P100 that served as a development machine.
We would really like to understand the problem that is why I keep including
the list on my responses to you. Maybe someone else knows what is going on
and will tell us.
Bill
+---------------------------------------------------
| Bill MacAllister
| 14219 Auburn Road
| Grass Valley, CA 95949
| 530-272-8555
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
