Issue #3238 has been updated by micah -.
here is my hacky work-around that I am doing every 20 minutes:
<pre>
file { "/usr/local/sbin/puppetmaster_kill_mysql.sh":
source => "$fileserver/riseup/puppetmaster_kill_mysql.sh",
mode => 0755, owner => root, group => root;
}
cron { "stop_being_annoying":
command => "/usr/local/sbin/puppetmaster_kill_mysql.sh",
user => root,
minute => '*/20',
require => File["/usr/local/sbin/puppetmaster_kill_mysql.sh"];
}
#!/bin/sh
export HOME=/root
MYSQLADMIN=/usr/bin/mysqladmin
# Connections caught sleeping after this many seconds will be terminated.
TIMEOUT=600;
$MYSQLADMIN processlist | grep puppet | awk '{print $2,$12}' | while read
PROCESSID SLEEPING
do
if [ $SLEEPING -gt $TIMEOUT ];
then
echo "killing $PROCESSID"
$MYSQLADMIN kill $PROCESSID
fi
done
</pre>
----------------------------------------
Bug #3238: puppetmaster uses to many mysql connections
https://projects.puppetlabs.com/issues/3238
Author: Nicolas Szalay
Status: Code Insufficient
Priority: Normal
Assignee:
Category: stored configuration
Target version: Statler
Affected Puppet 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.
