Issue #961 has been updated by madduck. Category set to network Status changed from Closed to Re-opened Assigned to changed from community to luke Affected version set to 0.24.1
The 933b1df6d84ec34a6ff347240c0151434ecc80a9 commit might have fixed the problem, but according to James, it's been refactored before 0.24.1 came out, and as a result, neither 0.24.1 or any later version includes the fix in lib/puppet/network/xmlrpc/client.rb, but in lib/puppet/network/http_pool.rb. It seems, however, that the fix is buggy or a new bug has been introduced since then, because my 0.24.5 and 0.24.7 clients both leave plenty of connections around. I think that this is the root cause of Debian bug #502193 (http://bugs.debian.org/502193). ---------------------------------------- Bug #961: puppetd creating too many/not closing TCP connections http://projects.reductivelabs.com:80/issues/961 Author: col_s Status: Re-opened Priority: Normal Assigned to: luke Category: network Target version: Complexity: Unknown Patch: None Affected version: 0.24.1 Keywords: With a single client puppetd run, established concurrent TCP connections between the client and the puppetmaster often exceeds 100. If two or three clients are run in parallel, and sometimes even with a single client, the number of connections exceeds 256. On my Solaris 10 puppetmaster, the maximum number of open files defaults to 256, when this limit is exceeded for the puppetmasterd process, no further connections can be opened and we receive the following error message on the client(s): <pre> warning: Other end went away; restarting connection and retrying </pre> Before starting a client run, the number of connections is zero: <pre> $ netstat -an | grep 8140.*ESTABLISH | wc -l 0 </pre> Soon after I start puppetd on the client: <pre> puppetmaster $ netstat -an | grep 8140.*ESTABLISH | wc -l 101 </pre> Prior to 0.24.0 I don't believe puppetd opened many connections to the puppetmaster concurrently. I have needed to increase the limit on maximum open files on the puppetmaster, but this is not an ideal workaround as having all those sockets open consumes a lot of system resources and i'm still very limited in the number of clients we can run concurrently. So I think that this is a major issue. ---------------------------------------- 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://reductivelabs.com/redmine/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 -~----------~----~----~----~------~----~------~--~---
