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

[Kalle Lehtonen < >]

And now running the same few times with success. And then the same
stacktrace I posted for cookbook versions.

-Kalle

2014-07-30 16:55 GMT+03:00 Kalle Lehtonen 
<
 >:
> Hi,
>
> I did not use client.rb for debugging. Just ran:
> chef-client -S <chef-server name> -N <node name> -k <client.pem key
> location> -l debug -L chef.log
>
> Also client printed out:
> [2014-07-30T13:23:16+00:00] WARN: Did not find config file: 
> C:\chef\client.rb, u
> sing command line options.
>
> So what I gather those were the only parameters chef-client used.
>
> Example error. There has not been as many cookbook file sync errors
> than node info, runlist and this for cookbook versions:
> [2014-07-30T13:49:20+00:00] DEBUG: Reporting error starting run. URL:
> reports/nodes/TEST-WINDOWS/runs Received 404. Disabling reporting for
> run.
> [2014-07-30T13:49:20+00:00] DEBUG: Checking for administrator privileges....
> [2014-07-30T13:49:20+00:00] DEBUG: chef-client has administrator
> privileges on node TEST-WINDOWS.
> [2014-07-30T13:49:20+00:00] DEBUG: Synchronizing cookbooks
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::JSONInput#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::JSONToModelOutput#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::CookieManager#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::Decompressor#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::Authenticator#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Signing the request as TEST-WINDOWS
> [2014-07-30T13:49:20+00:00] DEBUG: String to sign: 'Method:POST
> Hashed Path:zXHyJOjo6pCoVGEbbPQWMq1P1mY=
> X-Ops-Content-Hash:o0CAJ5UPSa3dnhX2UFKxcIGVJZI=
> X-Ops-Timestamp:2014-07-30T13:49:20Z
> X-Ops-UserId:TEST-WINDOWS'
> Header hash: {"X-Ops-Sign"=>"algorithm=sha1;version=1.0;",
> "X-Ops-Userid"=>"TEST-WINDOWS",
> "X-Ops-Timestamp"=>"2014-07-30T13:49:20Z",
> "X-Ops-Content-Hash"=>"o0CAJ5UPSa3dnhX2UFKxcIGVJZI=",
> "X-Ops-Authorization-1"=>"Ff2B/dvRKKSL+sAkDJVHcmInvRLqYSQO4W4k94WoLhZnO+tKSEDYJ5pw5sRJ",
> "X-Ops-Authorization-2"=>"3oekeXQRHLXnDP7F+5pQjYqfBGdp4wFcpnY7PI3p2zdTWjw4CGz/xGkUcbmG",
> "X-Ops-Authorization-3"=>"uLpaL123sY+cS+NB/3F9WvdyBRqEDm4ALZxp2KUdC4TGtlsoEQFSh74zotZW",
> "X-Ops-Authorization-4"=>"Yo5M/u7teKnS7cx4fZQb+T9faKfbX5Qkcsu0lVeXFLANbyLxCkHNsQRpuwQZ",
> "X-Ops-Authorization-5"=>"aK6aLBzCFEMwV+9J6Fy2CHOcN4HKqYUFefjvUeHuGR21g0IVehD1oxS4EO/u",
> "X-Ops-Authorization-6"=>"069JI8MGvkAiEDpnex0OE7P/F8Xa9QXXNvad8mvGYQ=="}
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::RemoteRequestID#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Chef::HTTP calling
> Chef::HTTP::ValidateContentLength#handle_request
> [2014-07-30T13:49:20+00:00] DEBUG: Initiating POST to
> https://<chef-server>/environments/_default/cookbook_versions
> [2014-07-30T13:49:20+00:00] DEBUG: ---- HTTP Request Header Data: ----
> [2014-07-30T13:49:20+00:00] DEBUG: Content-Type: application/json
> [2014-07-30T13:49:20+00:00] DEBUG: Accept: application/json
> [2014-07-30T13:49:20+00:00] DEBUG: Accept-Encoding:
> gzip;q=1.0,deflate;q=0.6,identity;q=0.3
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-SIGN: algorithm=sha1;version=1.0;
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-USERID: TEST-WINDOWS
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-TIMESTAMP: 2014-07-30T13:49:20Z
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-CONTENT-HASH:
> o0CAJ5UPSa3dnhX2UFKxcIGVJZI=
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-1:
> Ff2B/dvRKKSL+sAkDJVHcmInvRLqYSQO4W4k94WoLhZnO+tKSEDYJ5pw5sRJ
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-2:
> 3oekeXQRHLXnDP7F+5pQjYqfBGdp4wFcpnY7PI3p2zdTWjw4CGz/xGkUcbmG
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-3:
> uLpaL123sY+cS+NB/3F9WvdyBRqEDm4ALZxp2KUdC4TGtlsoEQFSh74zotZW
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-4:
> Yo5M/u7teKnS7cx4fZQb+T9faKfbX5Qkcsu0lVeXFLANbyLxCkHNsQRpuwQZ
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-5:
> aK6aLBzCFEMwV+9J6Fy2CHOcN4HKqYUFefjvUeHuGR21g0IVehD1oxS4EO/u
> [2014-07-30T13:49:20+00:00] DEBUG: X-OPS-AUTHORIZATION-6:
> 069JI8MGvkAiEDpnex0OE7P/F8Xa9QXXNvad8mvGYQ==
> [2014-07-30T13:49:20+00:00] DEBUG: HOST: <chef-server>:443
> [2014-07-30T13:49:20+00:00] DEBUG: X-REMOTE-REQUEST-ID:
> 4fc51587-2fbe-4ae9-bd08-9039faa8648e
> [2014-07-30T13:49:20+00:00] DEBUG: Content-Length: 71
> [2014-07-30T13:49:20+00:00] DEBUG: ---- End HTTP Request Header Data ----
> [2014-07-30T13:49:20+00:00] DEBUG: Re-raising exception: EOFError -
> end of file reached
> C:/opscode/chef/embedded/lib/ruby/1.9.1/openssl/buffering.rb:174:in
> `sysread_nonblock'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/openssl/buffering.rb:174:in
> `read_nonblock'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/protocol.rb:141:in `rbuf_fill'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/protocol.rb:122:in `readuntil'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/protocol.rb:132:in `readline'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:2563:in 
> `read_status_line'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:2552:in `read_new'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1320:in `block
> in transport_request'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1317:in `catch'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1317:in
> `transport_request'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1294:in `request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/rest-client-1.6.7/lib/restclient/net_http_ext.rb:51:in
> `request'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1287:in `block in 
> request'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:746:in `start'
>   C:/opscode/chef/embedded/lib/ruby/1.9.1/net/http.rb:1285:in `request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/rest-client-1.6.7/lib/restclient/net_http_ext.rb:51:in
> `request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http/basic_client.rb:65:in
> `request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http.rb:257:in
> `block in send_http_request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http.rb:289:in
> `retrying_http_errors'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http.rb:251:in
> `send_http_request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http.rb:141:in
> `request'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/http.rb:124:in
> `post'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/policy_builder/expand_node_object.rb:168:in
> `sync_cookbooks'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/policy_builder/expand_node_object.rb:66:in
> `setup_run_context'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:265:in
> `setup_run_context'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:429:in
> `do_run'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:227:in
> `run'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/application.rb:217:in
> `run_chef_client'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/application/client.rb:328:in
> `block in run_application'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/application/client.rb:317:in
> `loop'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/application/client.rb:317:in
> `run_application'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/application.rb:67:in
> `run'
>   
> C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/bin/chef-client:26:in
> `<top (required)>'
>   C:/opscode/chef/bin/chef-client:23:in `load'
>   C:/opscode/chef/bin/chef-client:23:in `<main>'
>
>
> -Kalle
>
> 2014-07-30 16:30 GMT+03:00 Carlos Camacho 
> <
 >:
>> Can you send the client.rb of your node?
>>
>> On Wed, Jul 30, 2014 at 3:28 PM, Kalle Lehtonen 
>> <
 >
>>  wrote:
>>> Hi,
>>>
>>> Just ran on performance server with "chef-client -S <chef-server name>
>>> -N <node name> and I still get that EOFError.
>>>
>>> We tested as well with standard flavors and those were successful as
>>> you mentioned in your e-mail to the list on 9th of July.
>>>
>>> Cheers,
>>> Kalle
>>>
>>> 2014-07-30 13:02 GMT+03:00 Carlos Camacho 
>>> <
 >:
>>>> Hello,
>>>>
>>>> Again, the problem its that you should not have the node_name
>>>> parameter in your client.rb file.
>>>> Do it, and you will fix the problem in your Performance images.
>>>> Its not about the Rackspace images as they replace the images to get
>>>> the latest updates once in a while.
>>>>
>>>>
>>>> Cheers.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jul 30, 2014 at 10:31 AM, Kalle Lehtonen
>>>> <
 >
>>>>  wrote:
>>>>> Hi Carlos,
>>>>>
>>>>> Sorry to comeback to this issue this late.
>>>>>
>>>>> But would you be able elaborate more on the issue?
>>>>>
>>>>> We have encountered the same issue (and still encounter) in Rackspace
>>>>> environment with Windows 2008R2 images with Rackconnect enabled 
>>>>> servers. The
>>>>> only difference was that we were able to try Windows client with 
>>>>> non-Rackspace
>>>>> server which worked. Also Chef client and server both running CentOS 
>>>>> 6.5 PVHVM
>>>>> image worked correctly.
>>>>>
>>>>>
>>>>> I cannot find either of those server IDs on the list I get from 
>>>>> Rackspace.
>>>>> Could you tell the names of those images?
>>>>> You also mentioned that the server flavor had an impact to it. I would 
>>>>> then
>>>>> guess you used standard flavors? Was it required for both client and 
>>>>> server?
>>>>>
>>>>> It would be also interesting to know if Rackspace was planning to fix 
>>>>> the
>>>>> performance flavor images and was this only affecting clients, server 
>>>>> or both?
>>>>>
>>>>> I am just interested on this because I would hate to go back to standard
>>>>> servers in Rackspace.
>>>>>
>>>>> Cheers,
>>>>> Kalle
>>>>>
>>>>> 2014-07-30 9:39 GMT+03:00 Carlos Camacho 
>>>>> <
 >:
>>>>>> Hello Kalle,
>>>>>>
>>>>>> No problem man, this was a really nasty issue with a really simple fix 
>>>>>> (Really).
>>>>>> Them problems its that ohai some times get crazy getting the node name
>>>>>> for Windows Performance images on Rackspace.
>>>>>> This is the fix,
>>>>>>
>>>>>> You can either bootstrap your chef-client with the -N shortcut (My 
>>>>>> choice):
>>>>>>
>>>>>> knife bootstrap windows winrm IP -x Administrator -P pass -N hostname
>>>>>>
>>>>>> Or add to client.rb:
>>>>>>
>>>>>> node_name "hostname"
>>>>>>
>>>>>>
>>>>>> I hope that this helps,
>>>>>>
>>>>>> Carlos.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jul 29, 2014 at 5:23 PM,  
>>>>>> <
 >
>>>>>>  wrote:
>>>>>>> Hi Carlos,
>>>>>>>
>>>>>>> Sorry to comeback to this issue this late.
>>>>>>>
>>>>>>> But would you be able elaborate more on the issue?
>>>>>>>
>>>>>>> We have encountered the same issue (and still encounter) in Rackspace
>>>>>>> environment with Windows 2008R2 images with Rackconnect enabled 
>>>>>>> servers. The
>>>>>>> only difference was that we were able to try Windows client with 
>>>>>>> non-Rackspace
>>>>>>> server which worked. Also Chef client and server both running CentOS 
>>>>>>> 6.5 PVHVM
>>>>>>> image worked correctly.
>>>>>>>
>>>>>>>
>>>>>>> I cannot find either of those server IDs on the list I get from 
>>>>>>> Rackspace.
>>>>>>> Could you tell the names of those images?
>>>>>>> You also mentioned that the server flavor had an impact to it. I 
>>>>>>> would then
>>>>>>> guess you used standard flavors? Was it required for both client and 
>>>>>>> server?
>>>>>>>
>>>>>>> It would be also interesting to know if Rackspace was planning to fix 
>>>>>>> the
>>>>>>> performance flavor images and was this only affecting clients, server 
>>>>>>> or both?
>>>>>>>
>>>>>>> I am just interested on this because I would hate to go back to 
>>>>>>> standard
>>>>>>> servers in Rackspace.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Kalle