I have been having a problem with MySQL lately. Specs are: RedHat Linux 7.3 MySQL 3.23.56, for pc-linux (i686) (same behavior with 4.0.12 as well) Apache 1.3.27 PHP 4.3.2
(most (99%) of the MySQL connections are made through PHP scripts running as an apache module) The problem happens as such: 1) MySQL will be running fine for a day or so, then any connections attempted to MySQL will start to 'hang' - no error messages or connection refused just sitting there trying to connect. 2) After around 10 minutes MySQL will start to return an error message thatthere are too many connections and the connection has been refused. 3) A look at 'mysqladmin processlist' shows what appears to be normal processes doing normal queries or trying to open tables. The last time this happened there were 60 processes all attempting to open different tables. There were no queries that were using any table that would have kept the other processes sitting. Nothing is logged to the slow query log which is set to log any queries running longer than a second. At this point, a look in 'top' will show a single MySQL process running at 99.9% of CPU. Any attempts to restart the MySQL server will result in an error saying a mysqld server is already running on 3306. There are no other errors listed in the error file for before or during the crash/incident. At this point, a 'kill -9 pid' on the pid of the MySQL process in top has no effect and does not kill the process. Other signals also have no effect. After killing the parents of the process, MySQL will restart; however, the process in top stays there at 99.9% CPU utilization until the server is rebooted. This happens about once or twice per day, with seemingly no predictability. If anyone has any steps I can take to trouble shoot this or I would be grateful. -Steven -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
