[chef] chef server down - how to troubleshoot?

[Stuart Cracraft < >]

When any knife to a previously
known good chef server 
fails, yet the node is up and
I can ssh into the chef server...

In /var/log/chef/client.log on
the server I see ECONN refused
errors connecting to local host
port 4000 with stack trace dumps. 

I see no error in server.log. 

Thoughts on how to proceed?



> On Aug 10, 2014, at 12:30 PM, Torben Knerr 
> <
 >
>  wrote:
> 
> There was once https://tickets.opscode.com/browse/CHEF-4027 to support
> SemVer with prerelease version identifiers, that would help in this
> situation.
> 
> Not sure if it will ever come, though...
> 
>> On Fri, Aug 8, 2014 at 10:38 PM, Andrew Brown 
>> <
 >
>>  wrote:
>> Thank you!
>> 
>>> On 2014-08-08, 3:44 PM, "Daniel DeLeo" 
>>> <
 >
>>>  wrote:
>>> 
>>> 
>>> 
>>>> On Friday, August 8, 2014 at 12:42 PM, Mike wrote:
>>>> 
>>>> This is currently an unsolved problem.
>>>> There's a lot of contention around versioning and Chef, and there's no
>>>> clear workflow for "what works best".
>>>> 
>>>> The flow Ranjib mentioned is one we do as well, and we don't freeze
>>>> cookbooks on upload for this reason.
>>>> 
>>>> Is it perfect? Nope. But it works for now, at least until we can
>>>> introduce better version identifiers in to Chef, chef-client, knife, and
>>>> any plugins that we leverage for that to speak the same versioning
>>>> language.
>>>> 
>>>> -M
>>> Not an immediate solution, but we¹re working on it. See
>>> https://github.com/opscode/chef-dk/blob/master/POLICYFILE_README.md and
>>> https://github.com/opscode/chef-rfc/pull/20
>>> 
>>> --
>>> Daniel DeLeo
>>