On 2013-11-29 14:10:37, Markus Frosch wrote:
> On So, 2013-11-24 at 21:21 +0100, Stig Sandbeck Mathisen wrote:
>> Control: tags -1 + moreinfo
>>
>> Did the new version of puppet (2.7.23) in Debian stable fix the memory
>> leak you observed?
>>
>
> Hey Stig,
> looks like no, unfortunately.
>
> A colleague of mine suggested to switch the agent to ruby1.9.1 for
> testing, have done that now... Maybe this gives us an idea if it's a
> Ruby or a Puppet problem.
>
> Do you have any suggestions what I could do for testing?
It's been almost a decade since this bug was filed, and several major
releases were issued. The past few Debian stable releases shipped with
Puppet 5, did that fix the issue?
Otherwise, could you confirm the latest puppet-agent (currently 7.16.0-2
in Debian experimental, installable in bookworm) still shows this
behavior?
I'm otherwise tempted to just close this bug report, it's hard to
believe that upstream would have left such a memory leak go on for so
long, but then again I myself run puppet agent through cron exactly for
that reason (amongst others).
a.
--
Le matraquage publicitaire est une forme moderne et supérieure de la
propagande.
- Henri Gobard
