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

[Adam Edwards < >]

I retract my statement on CHEF-5270. Looks like I was reading too much into
a certain part of the stack, looks like it's just regular net http
interacting with the server, so it's best to disregard CHEF-5270 /
rest-client for now.

Sorry for the confusion.

-Adam

-----Original Message-----
From: Adam Edwards 
[mailto:
 
Sent: Monday, May 19, 2014 11:24 AM
To: 
'
 '
Cc: Lamont Granquist
Subject: RE: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Problem running
chef-client, just from 2 days ago.

It sounds like you're hitting CHEF-5270, which is actually an issue with the
rest-client gem:
https://tickets.opscode.com/browse/CHEF-5270

The ticket has some workarounds, including using chef_gem in the recipe to
change to a version of rest-client that doesn't have the bug.

Sorry you are hitting this Carlos -- the longer term fix is to stop shipping
this gem at some point to avoid sensitivity to regressions since it's no
longer a dependency for Chef.

Thanks.

-Adam

-----Original Message-----
From: Carlos Camacho 
[mailto:
 
Sent: Monday, May 19, 2014 2:10 AM
To: 

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

Hello to all,

Windows chef-client fails in rackspace no mather if its rackconnected or
un-rackconnected, im starting to feel that this is a bug in windows
chef-client. Is there any way to put a bug request or something related? OR
having a chef-client debugger...

My problem is that i have more than 100 Windows servers in Rackspace cloud
and ill like to use chef to manage them.

At the end this is what i'm having in the chef-client logs.



Cheers.

On Mon, May 19, 2014 at 9: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..
>
>
> I just finished to run the chef using the standard rackspace network
> (Which produces the error) and with the VPN which runs perfect.
> Ill send you the tcpdump outputs in two txt files.
>
> I hope you can find some clue to help me fix this... :)
>
> I'm also have a open ticket in rackspace but they are sure that it's a
> chef problem (I don't think that because of my VPN test).
>
> My today tests will be this.
>
> Install the same environment in a non rackconnected network to see if
> it is failing.
>
> Cheers.
>
>
>
>
> On Fri, May 16, 2014 at 7:51 PM, Lamont Granquist 
> <
 >
> wrote:
>> On Fri May 16 00:38:29 2014, Carlos Camacho wrote:
>>>
>>> Daniel, doing some tcpdump in the chef server...
>>>
>>>
>>> RST sent from server
>>> 07:30:35.013370 IP chef.server.https > mynode.49776: Flags [R], seq
>>> 2457752489, win 0, length 0
>>>
>>> RST from client
>>> 07:30:35.472340 IP mynode.49779 >chef.server.https: Flags [R], seq
>>> 3250774265, win 0, length 0
>>>
>>>
>>
>> those actually have different ephemeral ports 49779 vs 49776, so
>> without any more context it looks like they're from different
>> connections (unless the rackspace stuff is rewriting the headers).
>> it might be useful to see the fuller context of the tcpdumps from both
>> the client and the server.
>>