Hello all,
I'm playing with a new puppet setup (2.6.1 on debian stable with ruby
1.8) and I've run into a problem with puppetd consuming ridiculous
amounts of memory.
My setup isn't that complex (apache2 configuration and a few other
packages/services), but puppetd will force the machine into swapping. It
seems to be CPU bound; if I run strace -e '!rt_sigprocmask' on it, I can
see that the only system calls it makes are brk() calls. The system ends
up swapping heavily and of course puppetd never makes progress. (On this
VM with 512MB of RAM, puppetd ends up w/ an RSS that oscillates around
450MB, while having 596MB mapped).
It seems like there's a superlinear algorithm or some infinite loop
that's triggered by my configuration. FWIW, the catalog for this client
is 3145 lines long and the server compiles it in 0.21 seconds.
Now, this client was able to run the catalog just fine a few days ago,
so I'm going to concentrate on my last set of changes, but I'm reporting
this here as this seems like an obvious bug to me. Perhaps others have
run into it before?
Also, is there some mechanism to monitor what puppetd is doing that will
provide me with more information than --debug?
Thanks,
Aggelos
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
