Too many conncetions error question

[Boofo]

Does anybody have any ideas what would cause the var direcdtiory to fill up with MySQL logs to the point of the sites getting the dreaded "Too many connections" error on a daily basis? We delete the logs and the next day it happens all over again. Is there a setting in the MySQL files that we need to set or do something with to avoid this?

[Marco van Herwaarden]

How big do those logs get?
What is in it?

Logs itself don't cause a too many connections error, although they could give problems if they get over 2Gb.

[Paul M]

Originally Posted by Boofo

Does anybody have any ideas what would cause the var direcdtiory to fill up with MySQL logs to the point of the sites getting the dreaded "Too many connections" error on a daily basis? We delete the logs and the next day it happens all over again. Is there a setting in the MySQL files that we need to set or do something with to avoid this?

Logging is a setting in the my.cnf file - as I recall you have to turn it on - so if you check the file you should see a logging command you can remove.

No amount of logging will cause a too many connections error - that's a seperate problem.

[Boofo]

Well, everytime we start getting the errors, the host goes in and deletes the MySQL logs form the var directory and then the error goes away and the sites are opened back up. So, yes, the logs are causing the error. Apparently the host is saying that the var directory gets filled up with the logs and then the errors start.

[Marco van Herwaarden]

So what is logged in those log-files?

[Boofo]

Originally Posted by MarcoH64

So what is logged in those log-files?

I have no idea as he usually erases them before I can see them.

[Paul M]

Originally Posted by Boofo

Well, everytime we start getting the errors, the host goes in and deletes the MySQL logs form the var directory and then the error goes away and the sites are opened back up. So, yes, the logs are causing the error. Apparently the host is saying that the var directory gets filled up with the logs and then the errors start.

Sorry, but IMO - No, the logs are not causing the error - log files cannot cause that error.

Much more likely is that while removing them he restarts mysql - which will also drop all the connections.