Issue #3238 has been updated by Egon Kastelijn.
Hi, We bounced into the same problem. Puppet opens a MySQL connection to the database every time a Puppet-agent asks for its catalog. The connections stay open, and MySQL runs out of available connections. The puppet code contains a line in "rails.rb" that enables/disables connection concurrency based on the ActiveRecord version (< 2.2), but the problem is indeed (as mentioned by Rich Rauenzahn) that the check is wrong. In our infrastructure I had to set "ActiveRecord::Base.allow_concurrency = false". We are running: puppet-2.6.8-1.el5 rubygem-activerecord-2.1.1-2.el5 kind regards, Egon ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections https://projects.puppetlabs.com/issues/3238 Author: Nicolas Szalay Status: In Topic Branch Pending Review Priority: Normal Assignee: Category: stored configuration Target version: 2.7.x Affected Puppet version: 0.25.4 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.
