Jira (PUP-3345) Puppet Master Memory Leak

[Jason Fonseca (JIRA)]

Title: Message Title

Jason Fonseca commented on an issue   Re: Puppet Master Memory Leak I have undone our Rack configuration to be able to run Puppet with the following parameters: /usr/bin/ruby /usr/bin/puppet master --no-daemonize --debug --trace The process exhibits the same behavior of growing until killed by the OOM. I will begin trying to find which manifest or module or setting is causing the leak. When should the puppet master process reach its maximum memory usage? After initialization or after all systems have checked in? Running the master in debug outputs a couple of error messages frequently. I don't know if they are related to this issue, caused by a misconfiguration, or normal. They are: Debug: Failed to load library 'msgpack' for feature 'msgpack' Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing Debug: Did not match path ("/production/file_metadata/modules/securetty/securetty") The last one occurs with any file we distribute via puppet. Add Comment   Puppet / PUP-3345 Puppet Master Memory Leak Starting with 3.7, the Puppet master process will allocate more and more memory until it is killed by the OOM process. This occurs in about 24 hours in our environment. The behaviour occurs in both Rack and WEBRick configurations. In the Rack configuration the four Rack processes will grow until killed. In WEBRick configuration the one puppet maste... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.