On 7/24/15 12:56 AM, Michael Wörz wrote:
Hello,
in the past months we are observing raising memory usage on our puppet
server and we have to restart it once a week when it starts swapping.
Mainly there are 5 Passenger processes that are running for days and
using about 15-20% of memory each.
System has 4 GB of memory and is serving about 1600 Clients.
-> rpm -qa | grep passenger
ruby193-rubygem-passenger-native-libs-4.0.18-9.8.el6.x86_64
rubygem-passenger-native-libs-4.0.18-9.8.el6.x86_64
mod_passenger-4.0.18-9.8.el6.x86_64
rubygem-passenger-4.0.18-9.8.el6.x86_64
rubygem-passenger-native-4.0.18-9.8.el6.x86_64
ruby193-rubygem-passenger-native-4.0.18-9.8.el6.x86_64
ruby193-rubygem-passenger-4.0.18-9.8.el6.x86_64
-> cat /etc/redhat-release
CentOS release 6.6 (Final)
-> rpm -qa | grep puppet
puppet-server-3.8.1-1.el6.noarch
There were some reports of memory growth in Puppet masters starting with
late 3.6 and definitely in 3.7. I don't recall if a ticket was ever
generated.
One workaround is a to set PassengerMaxRequests = 10000 so that your
Puppet master processes are recycled sooner. This should keep RAM usage
below 200-250MB per process.
Ramin
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55B26FCC.4000106%40badapple.net.
For more options, visit https://groups.google.com/d/optout.
