Avi, I doubt that is my problem. I'm running this in a test environment, and I'm doing a full 'service puppet restart' every single time. I've seen this memory problem occur on the very first run of puppet after the restart.
I read about the ruby memory leak, but I don't see where I can get a ruby 1.8.7 RPM from. :( Doug On Sun, Nov 15, 2009 at 12:45 PM, Avi Miller <avi.mil...@gmail.com> wrote: > > Hi Douglas, > > Douglas Garstang wrote: >> Actually, I just noticed that puppetd was using approx 1.5Gb of memory >> before it barfed. Nice... > > If you're running on RHEL/CentOS, there is a known issue with the Ruby > that ships with that distribution that causes memory leaks. I have a > cronjob that restarts puppetd each night to ensure that it doesn't use > too much memory. > > An alternative is to not run puppetd as a service, but rather as a > cronjob with the --no-daemonize and --onetime command-line options. That > way, puppetd never remains resident. > > Hope that helps, > Avi > > > > -- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garst...@gmail.com Cell: +1-805-340-5627 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
