Thanks
From: Sascha Bates [mailto: " target="_blank"> ]
Sent: Tuesday, May 21, 2013 11:46 AM
To: " target="_blank">
Subject: [chef] Re: Re: Nodes not checking in since yesterday's maintenance
There's a bug in Chef client that, if it can't talk to the mothership, it can lose track of its pid and will hang out indefinitely until restarted. This is fixed in I think the next release. Or you can do what I did and just grab the hack and make it a cookbook file deploy. I also think that setting the client.rb property of client_fork to true can prevent this behavior.
Sascha
Daniel DeLeo wrote:
On Tuesday, May 21, 2013 at 8:15 AM, Don Couture wrote:
Hi All,
Hopefully this isn’t a dumb newbie question but none of my chef-client running as a service nodes are checking in since yesterday’s maintenance that was performed on hosted chef.
Is anyone else seeing this?
From our side, traffic returned to normal right after the maintenance completed. Your best bet is to get in touch with support and include any relevant details about how you've set up your daemonized chef clients and any errors you're seeing.
Thanks,
Don
--
Daniel DeLeo
Archive powered by MHonArc 2.6.16.