[chef] Re: Re: Re: Re: Re: Re: Chef 11 in production

[Peter Donald < >]

On Sun, Apr 21, 2013 at 9:09 PM, Anton K 
<
 >
 wrote:
>> Based on my investigation, the same bug is present in both 10.x and 11.x
>> release tracks, but is completely worked around by running the chef-client
>> with --fork. If you're not seeing any problem with 10.24, then you 
>> shouldn't
>> have a problem with 11.4 either.
>
> I found that chef-client 11.x in forked state generate many processes with
> each call. Like this:

We have hit the same problem. Except we have also found that --fork
was not sufficient - we ended up moving to executing it as a cron
script with a monitor that kills and retries when it gets stuck. (even
ignoring the memory problem ohai seems to get a little stuck checking
the uptodate-ness of apt packages).

-- 
Cheers,

Peter Donald