Nodes not checking in since yesterday's maintenance


#1

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?

Thanks,

Don


#2

What happens if you do a manual chef-client run?


~~ StormeRider ~~

“Every world needs its heroes […] They inspire us to be better than we
are. And they protect from the darkness that’s just around the corner.”

(from Smallville Season 6x1: “Zod”)

On why I hate the phrase “that’s so lame”… http://bit.ly/Ps3uSS

On Tue, May 21, 2013 at 8:15 AM, Don Couture dcouture@copyright.com 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?****


Thanks,****


Don****


#3

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


#4

Probably hung on a resource or something connecting to hosted chef. Dare I
ask, but have you tried restarting them yet?

On Tue, May 21, 2013 at 11:15 AM, Don Couture dcouture@copyright.comwrote:

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?****


Thanks,****


Don****


#5

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


#6

Thanks

From: Sascha Bates [mailto:sascha.bates@gmail.com]
Sent: Tuesday, May 21, 2013 11:46 AM
To: chef@lists.opscode.com
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


#7

Thanks a lot! I’ve send detailed information to support

On Wed, May 22, 2013 at 12:40 AM, Don Couture dcouture@copyright.comwrote:

Thanks****



From: Sascha Bates [mailto:sascha.bates@gmail.com]
Sent: Tuesday, May 21, 2013 11:46 AM
To: chef@lists.opscode.com
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****