Hi all
Recently (last couple of weeks) I have found that mysql and apache have been eating my server resources pretty badly. When I execute a top command I find that 1 or the other has an extremely long running process. For example the following is taken from a top command 5 minutes ago:-
24256 mysql 15 0 101m 6704 2472 S 5.3 0.9 11:53.69 mysqld
As you can see it has been running for almost 12 hours. (and consuming a lot of memory). When I try the 'watch mysqladmin proc' command there was only 2 running and nothing looked out of ordinary. The longest I have seen so far is a process running for 23 hours.
Has anyone any idea what could cause this? Is mysql simply not closing a dormant connection?
As soon as I restart the service the load of the server returns to a very good level but before the commands they can be anywhere between 4 and 6 on a single core server.
Recently (last couple of weeks) I have found that mysql and apache have been eating my server resources pretty badly. When I execute a top command I find that 1 or the other has an extremely long running process. For example the following is taken from a top command 5 minutes ago:-
24256 mysql 15 0 101m 6704 2472 S 5.3 0.9 11:53.69 mysqld
As you can see it has been running for almost 12 hours. (and consuming a lot of memory). When I try the 'watch mysqladmin proc' command there was only 2 running and nothing looked out of ordinary. The longest I have seen so far is a process running for 23 hours.
Has anyone any idea what could cause this? Is mysql simply not closing a dormant connection?
As soon as I restart the service the load of the server returns to a very good level but before the commands they can be anywhere between 4 and 6 on a single core server.