Issue #3238 has been updated by Rich Rauenzahn.
This seems to fix the issue, but it is a large hammer:
<pre>
$ diff -u puppet-2.6.4.orig/lib/puppet/rails.rb
puppet-2.6.4/lib/puppet/rails.rb
--- puppet-2.6.4.orig/lib/puppet/rails.rb 2011-05-25 14:12:22.000000000
-0700
+++ puppet-2.6.4/lib/puppet/rails.rb 2011-05-25 15:49:25.000148000 -0700
@@ -24,7 +24,7 @@
end
# As of ActiveRecord 2.2 allow_concurrency has been deprecated and no
longer has any effect.
- ActiveRecord::Base.allow_concurrency = true if
Puppet::Util.activerecord_version < 2.2
+ ActiveRecord::Base.allow_concurrency = false if
Puppet::Util.activerecord_version < 2.2
ActiveRecord::Base.verify_active_connections!
</pre>
----------------------------------------
Bug #3238: puppetmaster uses to many mysql connections
https://projects.puppetlabs.com/issues/3238
Author: Nicolas Szalay
Status: In Topic Branch Pending Merge
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.
