Issue #3238 has been updated by Rein Henrichs. Status changed from Re-opened to Needs more information
We would like some more info to help reproduce this behavior: 1. Are you all using async_storeconfigs or is it just Jason? 2. How can you tell that the connections are leaked? Do they show up in netstat or some other diagnostic tool? Do you get error messages that you can post here? 3. What's the behavior of the system once it reaches max connections? Is it sluggish? How does it "trash the system"? 4. How are you setting max connections? What value are you using? Is it the mysql max_connections variable? Is it the puppet dbconnections setting? Is it set to 1? 10? 100? ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections http://projects.puppetlabs.com/issues/3238 Author: Nicolas Szalay Status: Needs more information Priority: Normal Assignee: Category: Target version: Affected 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.
