Issue #3238 has been updated by Scott Dodson.
Status changed from Closed to Re-opened
I get the same behavior using puppet 0.25.5 on RHEL 5.5. This is happening with
only a dozen or so nodes, every few hours I run into connection limits.
mysql Ver 14.12 Distrib 5.0.77, for redhat-linux-gnu (i386) using readline 5.1
rubygems-1.3.1-1.el5
rubygem-rails-2.1.1-2.el5
rubygem-actionpack-2.1.1-5.el5
rubygem-activerecord-2.1.1-2.el5
rubygem-activeresource-2.1.1-1.el5
rubygem-rake-0.8.3-1.el5
rubygem-activesupport-2.1.1-2.el5
rubygem-actionmailer-2.1.1-1.el5
ruby-mysql-2.7.3-1.el5
Options I've got relevant to mysql are :
dbadapter = mysql
dbuser = puppet
dbpassword = password
dbserver = localhost
dbname = puppet
dbmigrate = true
----------------------------------------
Bug #3238: puppetmaster uses to many mysql connections
http://projects.puppetlabs.com/issues/3238
Author: Nicolas Szalay
Status: Re-opened
Priority: Normal
Assigned to:
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.
