Bug #28578 mysqld shutdown hangs

Description:
I am seeing the exact same behavior as described in Bug #27310: mysqld will hang indefinitely when I try to run the shutdown script. I reported my case there, but since that bug is closed, I don't know if my comment will be seen.

That bug stated that it was fixed in 5.0.40, but I am running mysql 5.0.41 and it still hangs on shutdown.

If I hit Ctrl-C after waiting for the shutdown script to complete, I get an error message that says this:

  Warning;  Aborted waiting on pid file: '/var/mysql/pid' after 12 seconds

At this point mysql is still running, and even a 'killall' will not stop it. However, I have found that if I run the following command, it will stop with a bunch of errors:

    mysqladmin shutdown && mysqladmin shutdown

If I do this then I get the following errors, and mysql finally shuts down:

mysqladmin: connect to server at 'localhost' failed
error: 'Lost connection to MySQL server at 'reading initial communication packet', system error: 104'
error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)'
Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists!

Here is some system information that someone asked for in the other thread (where the bug was closed):

root@srv$ uname -a
Linux a0 2.6.15.7 #1 SMP Sat Jul 1 06:26:14 GMT 2006 i686 unknown unknown
GNU/Linux

root@srv$ free
             total       used       free     shared    buffers     cached
Mem:        239536     222012      17524          0      47732     106336
-/+ buffers/cache:      67944     171592
Swap:       524280      59312     464968

root@srv$ getconf GNU_LIBPTHREAD_VERSION
linuxthreads-0.10

root@srv$ getconf GNU_LIBC_VERSION
glibc 2.3.5

How to repeat:
Start mysqld, then try to stop it. Always hangs.

Thank you for a problem report. I had re-opened Bug #27310. This will be marked as its duplicate.

Ugh, please ignore this report and close this bug. I accidentally compiled 5.0.37 in a directory labeled 5.0.41, and thus was testing against the wrong version.

This problem is indeed fixed in 5.0.41. Sorry for the trouble.