I could observe that it even leaks in standalone mode up to 800M of
memory just for that litlle augeas recipe.
And it does not leak with 0.25.4.
This is why I'm suspecting these augeas changes to be the cause of the
problem. But I'm only suspecting them.
Does it leak if you remove all the augeas parts from your manifest?
If I run a manifest with the standalone cmd containing some package
and file resources I cannot observe it leaking. However, I could
observe it leaking up to 800M by applying _only_ the augeas resource
mentioned in the bug with the standalone cmd. Therefore I suspect
the augeas changes.
so I applied the patch bryan provided for #3379 [1] and it fixes the
problem with the augeas resource and it _also_ fixes the encountered
memory problem.
as I mentioned:
debug: Augeas[grub_first_default](provider=augeas): Opening augeas
with root /, lens path , flags 0 debug:
Augeas[grub_first_default](provider=augeas): Augeas version 0.7.0 is
installed debug: Augeas[grub_first_default](provider=augeas): Will
attempt to save and only run if files changed debug:
Augeas[grub_first_default](provider=augeas): sending command 'set'
with params ["/files/etc/grub.conf/default", "0"] <----- here it
hangs and grows.
if you compare that to the bugreport it hung and grew right before
closing the conenction to augeas:
debug: Augeas[grub_first_default](provider=augeas): sending command
'set' with params ["/files/etc/grub.conf/default", "0"]
debug: Augeas[grub_first_default](provider=augeas): Closed the
augeas connection
/usr/lib/ruby/site_ruby/1.8/puppet/util/errors.rb:51:in `fail'
[...]
I didn't yet look any deeper in the code, but something allocated a
lot of memory in communication with augeas. :/
Anybody any ideas on that? Or do we want to assume that either there
have been a fault on my side or that magic can happen?
cheers pete
[1] http://projects.reductivelabs.com/issues/3379
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" 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-dev?hl=en.
