Greetings, I am stumped. I have a very busy MySQL db that we've run for about 3 years with no problems. A couple of months ago we upgraded the system to RH-3AS with RedHat's distro mysql-server 3.23.58-1.9. Recently I've started getting zombie processes ([mysql <defunct>]). I've checked/tested the obvious things (netstat/web logs/mysql logs). No connection on the network to the defunct process. Every mysql log entry has a connect/query(s)/quit entry. The web logs don't show anything conclusive during the time the mysql process goes zombie. It comes at different times from different scripts. Sometimes the server is busy, sometimes it's not when a process goes defunct. The /proc/(PID) of the defunct mysql process are empty files. When I restart the mysqld, the defunct processes disappear. My question is this, what is the mysql daemon waiting for to release the <defunct> thread? There is something holding up the system and creating these problems. The server is pretty buff (Dual Zeon, 2G RAM). I cannot just take the system apart, it's one of the flag ships of our department. I have googled this and found very little about "[mysql <defunct>]" processes. Any ideas where to start looking/testing? Your help in this matter would be greatly appreciated. Thanks for you help, Ken
-- _________________________________ Ken Sorensen <[EMAIL PROTECTED]> -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
