are you running on a dedicated machine? It sounds like it.
When you hit the problem try the mysql show status command to see if anything looks out of whack. You can also use mysql show variables for additional info.
I'm not sure what the solution is, but I've been running several sites off the same mysql server for over a year now, using 90% GT software, and it's never had a problem like that. Current uptime is almost 200 days. My limit is set at 100 as well. I have apache set at 150, and I've hit problems with that a couple of times though.
Very often this has been fixed by the ISP making changes.
Often, a bad script -- or modified script -- will cause that. If you don't explicitly disconnect, there may be a lag in the reclamation of resources. But, a system reboot should have fixed that, and you shouldn't have started to hit problems unless you are really having 100+ simultaneous connects.
I would think you'd notice a load/performance problem before that.
I wonder if it's a problem with apache-keep-alive and persistent connections? If you have more apache sessions running than you have MySQL connections, you could run out even with lower loads. Just speculation.
I haven't hit this, so I haven't had a chance/cause to try to solve it.
PUGDOGŪ
PUGDOGŪ Enterprises, Inc.
FAQ: http://postcards.com/FAQ
When you hit the problem try the mysql show status command to see if anything looks out of whack. You can also use mysql show variables for additional info.
I'm not sure what the solution is, but I've been running several sites off the same mysql server for over a year now, using 90% GT software, and it's never had a problem like that. Current uptime is almost 200 days. My limit is set at 100 as well. I have apache set at 150, and I've hit problems with that a couple of times though.
Very often this has been fixed by the ISP making changes.
Often, a bad script -- or modified script -- will cause that. If you don't explicitly disconnect, there may be a lag in the reclamation of resources. But, a system reboot should have fixed that, and you shouldn't have started to hit problems unless you are really having 100+ simultaneous connects.
I would think you'd notice a load/performance problem before that.
I wonder if it's a problem with apache-keep-alive and persistent connections? If you have more apache sessions running than you have MySQL connections, you could run out even with lower loads. Just speculation.
I haven't hit this, so I haven't had a chance/cause to try to solve it.
PUGDOGŪ
PUGDOGŪ Enterprises, Inc.
FAQ: http://postcards.com/FAQ