Issue #3238 has been updated by Craig Dunn.
Following on from yesterdays update... After resorting to the mysql kill
process script on a crontab, which seemed to be working, this morning we
noticed the server giving 400 errors for "too many open files".... a quick lsof
gives us...
# lsof -p 19797 | grep socket | wc -l
1016
Even though mysql's processlist was empty, it looks like the sockets still
mount up. Restarting puppetmasterd seemed to sort it out
----------------------------------------
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.
