[chef] Re: Re: Memory leak

[Astlock < >]

Thanks Nic, with fork it randomly down with [chef-client] <defunct> :(

Hi Steve. You know the problem was not repeated last 2-3 days. I monitor memory consumption with Zabbix. I'll Let you know as soon as the situation is repeated.

Thank you.

On Thu, Jun 13, 2013 at 9:25 AM, Steven Danna < " target="_blank"> > wrote:

Hi,

On 6/12/13 2:59 AM, "> wrote:
> Anyone else care about this problem(
> http://tickets.opscode.com/browse/CHEF-3432 ) besides me? :)

Yes. :)

> We do
> automatically restart every 100 Mb. It's not a production way as I think.

As others have mentioned, using --fork avoids many of these issues.
However, it would also be great to track down the source of the leaks
when we can.

One issue in a number of the memory-leak related bugs is that it is hard
to discern whether the various reports are stemming from the same root
cause.

For instance, after some investigation via a support ticket, a colleague
and I believe we have one reproducible memory leak in Chef 10 pinned
down.  However, this reproduction case doesn't manifest in Chef 11 as
some users are reporting.

Some helpful information would include answers to some of the following
(if you are one of the contributors to that ticket, my apologies, if you
have already answered these):

- Are you experiencing this problem on a particular version of Chef?
- Are you experiencing this problem on a particular version of Ruby?
- Can you reproduce the problem with a minimal run list or small example
cookbook?

Cheers,

Steven


--
Steven Danna
Systems Engineer, Opscode, Inc
GPG Key: http://stevendanna.github.com/downloads/code/public.key