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

[Carlos Camacho < >]

Hello Lamont, Adam.

I'm finishing some tests and the PG error is documented here
(https://tickets.opscode.com/browse/CHEF-4390).

I have a new clue, so please if you can tell me what should be the
differences between these two types of connections.

If i connect the chef node (Windows) using pptpd and the server, it works 
fine.
If i connect the chef node (Windows)  and the server using the
standard network, it fails.

Cheers!


On Wed, May 21, 2014 at 8:32 PM, Lamont Granquist 
<
 >
 wrote:
>
> The postgresql logs look interesting.  The failed unique constraints might
> be the problem.  I would expect to see stack traces in the erchef logs
> though.
>
>
> On 5/20/14, 12: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.
>>>
>