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

[Daniel DeLeo < >]

On Monday, July 8, 2013 at 4:22 PM, Brad Knowles wrote:

On Jul 8, 2013, at 1:34 PM, Brad Knowles < "> > wrote:

I've seen CHEF-3432 and CHEF-3985, but I'm still seeing memory leak issues with chef-client 10.18.2, even though it's not running in daemon mode. The VM is configured for 2GB of "RAM" and 8GB of swap, and I'm now seeing chef-client reliably running up to ~9GB VSZ and 1.7GB RSS. This just started today, as I've been debugging and resolving various other issues in the cookbooks and recipes that we're using for this system.

Okay, so I think I may have found a bug in chef-client. If you change the name returned by `hostname` to something else, I'm guessing that chef-client will flake out in precisely this manner because the node name no longer matches the hostname.

When we changed the hostname back to match the node name, this memory leak behaviour disappeared.

Should I update CHEF-3432 or CHEF-3985 with this new piece of information?

--

Brad Knowles < "> >

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

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?

-- 

Daniel DeLeo