[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Problem running chef-client, just from 2 days ago.

[Carlos Camacho < >]

Hello,

No it didn't work, i upgraded rest-client to 1.6.8 locally in the
chef-client node but the error remain.

Thanks and look forward to have more clues!





On Tue, May 20, 2014 at 9:34 AM, Carlos Camacho
<
 >
 wrote:
> Hello,
>
> Adam, Lamont good morning.
>
> Ill give it a try to CHEF-5270 because this error is recent (I don't
> loose any trying as i'm stuck right now) about 2 weeks ago it suddenly
> stop working. Also I'm attaching the chef-client logs in debug mode
> and the chef-server logs. But again i don't see any error in the
> application layer.
>
> Thanks for your help,
>
> Cheers!
>
>
> On Mon, May 19, 2014 at 9:15 PM, Lamont Granquist 
> <
 >
>  wrote:
>> On 5/19/14, 12:24 AM, Carlos Camacho wrote:
>>>
>>> Hello Julian and Lamont,
>>>
>>> I just check all logs in the server and there is not any apparent
>>> error... It so confusing and frustrating this issue..
>>>
>>>
>> Well, the server is actually tearing down the connection normally with a
>> FIN|ACK, but then the client is still sending data, which produces a RST
>> from the server, then the client receives those and sends back FIN|ACK and
>> RST of its own.  So TCP is behaving normally and it does look like this
>> isn't a rackspace issue.  The question is why the server seems to tear down
>> the connection early while the client is still attempting to send data.
>>
>> There should be something either in the nginx or erchef logs on the server
>> on in the -l debug logs or the stacktrace on the client.
>>