Issue #3238 has been updated by Raphaël Pinson.
This is still badly broken, using a 2.7.19 puppetmaster on Lenny with ActiveRecord 2.3.2. I've tried: - reducing the `wait_timeout` value for MySQL, but that only causes active connections to be killed; - increasing the `max_connections` value for MySQL, but Puppet eventually catches up anyway; - playing with `dbconnections` in puppet.conf, but that doesn't solve anything. It just takes a bit longer to reach the limit. Killing MySQL threads is not an option either, as it kills active connections, which cancels catalog compilations. ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections https://projects.puppetlabs.com/issues/3238#change-73632 Author: Nicolas Szalay Status: In Topic Branch Pending Review Priority: Urgent Assignee: Category: stored configuration Target version: Affected Puppet version: 2.7.19 Keywords: mysql postgresql max_connections connections storeconfigs Branch: https://github.com/jamtur01/puppet/tree/tickets/2.7.x/3238 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.
