Ok, I've been having this problem every so often and it's happening more and more these days and I still can't figure out a solution. I know this sounds vague, but maybe you can help me make it less so...
I'm running version 3.23.44 and after a while, the maximum number of connections is reached regardless of how high it's set. Running (the very handy) mytop, I see that the oldest connections are 20 minutes old (or older). Since this happens only on a live server and I need to fix it ASAP, it's hard to do quick investigation, but it seems that MySQL eventually just stops executing these old queries and over time, enough of them fill up the max connections. An Apache server running PHP is the client and I can verify (via netstat) that there are not enough connections to the server to justify the high number of connections. In normal use, the number of connections is very low, the key efficiency is high (99% or better) and the server has no trouble. But then, after several hours, the connections reach the max (and always when I'm not looking;). Does this sound familiar? The machine is not swapping either, it's as if the connections are just dead. I have no choice (it seems) but to kill the threads or restart mysqld. I know I could upgrade to a newer version, but I would prefer to understand what's happening and why first. Any ideas? Is there anything I can check to see why these connections hang out for so long? Is the lack of swapping expected, i.e., does MySQL simply refuse to try to alloc more memory than the machine physically has? Would adding RAM give the server some headroom to finish these queries? Thanks! --------------------------------------------------------------------- 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
