Issue #3238 has been updated by micah -. Category set to stored configuration
I'm having this same problem with 2.6.2. I've tried different rails versions (2.1, 2.2.3, 2.3.2), I tried turning of async_storeconfigs, I've tried running with and without the puppet queuing daemon. I originally was getting a puppet error that comes when the max pool size is reached. So I changed the dbconnections variable to 20, but I still would get it: <pre> err: Could not retrieve catalog from remote server: Error 400 on SERVER: could not obtain a database connection within 5 seconds. The max pool size is currently 20; consider increasing it. </pre> So I raised that value to 150, which is what my my.cnf max_connections value is set to, but it just prolongs the problem until eventually I've got 150 sleeping mysql connections. The problem isn't number of mysql connections overwhelming the database, the problem is puppet not closing inactive connections. The mysql connections stick around and aren't doing anything. They basically are sleeping forever: <pre> mysql> show processlist\g +------+--------+-----------+--------+---------+------+-------+------------------+ | Id | User | Host | db | Command | Time | State | Info | +------+--------+-----------+--------+---------+------+-------+------------------+ | 2704 | puppet | localhost | puppet | Sleep | 6767 | | NULL | | 8310 | puppet | localhost | puppet | Sleep | 6604 | | NULL | | 8314 | puppet | localhost | puppet | Sleep | 6567 | | NULL | | 8316 | puppet | localhost | puppet | Sleep | 6509 | | NULL | | 8330 | puppet | localhost | puppet | Sleep | 6449 | | NULL | | 8336 | puppet | localhost | puppet | Sleep | 6349 | | NULL | | 8340 | puppet | localhost | puppet | Sleep | 6279 | | NULL | | 8355 | puppet | localhost | puppet | Sleep | 6177 | | NULL | | 8357 | puppet | localhost | puppet | Sleep | 6109 | | NULL | | 8365 | puppet | localhost | puppet | Sleep | 6005 | | NULL | | 8366 | puppet | localhost | puppet | Sleep | 5945 | | NULL | | 8367 | puppet | localhost | puppet | Sleep | 5950 | | NULL | | 8382 | puppet | localhost | puppet | Sleep | 5870 | | NULL | | 8385 | puppet | localhost | puppet | Sleep | 5832 | | NULL | | 8387 | puppet | localhost | puppet | Sleep | 5767 | | NULL | .... | 8903 | puppet | localhost | puppet | Sleep | 189 | | NULL | | 8910 | puppet | localhost | puppet | Sleep | 112 | | NULL | | 8913 | puppet | localhost | puppet | Sleep | 39 | | NULL | | 8914 | puppet | localhost | puppet | Sleep | 3 | | NULL | | 8917 | root | localhost | NULL | Query | 0 | NULL | show processlist | +------+--------+-----------+--------+---------+------+-------+------------------+ 115 rows in set (0.00 sec) </pre> ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections https://projects.puppetlabs.com/issues/3238 Author: Nicolas Szalay Status: Ready for Testing Priority: Normal Assignee: Category: stored configuration Target version: 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.
