Bug #21501 mysql process stuck
Submitted: 8 Aug 2006 11:29 Modified: 10 Sep 2006 15:58
Reporter: Eugene Golubitsky Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.22-log OS:FreeBSD (FreeBSD 5.4)
Assigned to: CPU Architecture:Any

[8 Aug 2006 11:29] Eugene Golubitsky
Description:
After upgrading from 4.1.15 to 5.0.22(from sources) we encountered the following problem:
during load hours mysql process goes to 150% CPU (ufs state) use and stops to execute queries (actually die). Neither mysql_server.sh restart nor kill -9 successed to kill this process; after all possible manipulation kill -STOP, kill -WHATEVER, etc. it dies after aproximately 15 min. The problem exists also when MySQL compiled with LinuxThreads.
See "printscreen" from shell :
www# /usr/local/etc/rc.d/mysql-server.sh stop
Stopping mysql.
Waiting for PIDS: 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952
20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20
2, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952,
0952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 20952, 209

How to repeat:
I really don't know
[9 Aug 2006 12:55] Eugene Golubitsky
One more thing - there's nothing in error log.
[10 Aug 2006 15:58] Miguel Solorzano
Thank you for the bug report. Have you applied the upgrade recommendations?
according:

http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html

Thanks in advance.
[10 Sep 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".