[chef] Re: Re: Debugging memory leak issues with chef-client?

[Daniel DeLeo < >]

On Monday, July 8, 2013 at 5:17 PM, Brad Knowles wrote:

On Jul 8, 2013, at 5:31 PM, Daniel DeLeo < "> > wrote:

CHEF-3432 is fixed, and I believe based on some internal debug work that CHEF-3985 has a different root cause than what you're describing, so please put this information in a new ticket. Can you also confirm that this has nothing to do with any cookbooks you're using by running with an empty run list or a cookbook that just sleeps for a while?

I tried running with an empty run list, and chef-client only ran for a few seconds -- not long enough to show up under "top" that I had running in another terminal window.

I'll try using a cookbook that just sleeps for a while.

--

Brad Knowles < "> >

LinkedIn Profile: <http://tinyurl.com/y8kpxu>

Thanks!

The reason I ask is that we run chef on all of our boxes with generated node ids and we haven't seen this issue. Could still be a bug in Chef, but I'm pretty sure there must be an additional factor besides just the node name.

-- 

Daniel DeLeo