Issue #3238 has been updated by micah -.
micah - wrote: > I'm having this same problem with 2.6.2. I've tried different rails versions > (2.1, 2.2.3, 2.3.2), I tried turning of async_storeconfigs, I've tried > running with and without the puppet queuing daemon. I've also tried now with activerecord and activesupport 2.3.5, the mysql ruby library 2.8.2... nothing seems to change the fact that I've got mysql connections that are sleeping for ages, the oldest right now is 10842 seconds. I'm afraid I'm going to have to resort to a depressingly hacky script that connects to mysql and kills those threads. ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections https://projects.puppetlabs.com/issues/3238 Author: Nicolas Szalay Status: Code Insufficient Priority: Normal Assignee: Category: stored configuration Target version: Statler Affected Puppet version: 0.25.4 Keywords: mysql postgresql max_connections connections storeconfigs Branch: Hello, after upgrading to 0.25.4 this morning (debian package from squeeze on lenny ), I saw that the number of mysql connections increased greatly and then reached max_connections. Accordingly to the number of managed hosts and the time taken to reach the maximum connections I suppose that it uses one connection per client checkin. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
