Problem running chef-client, just from 2 days ago


#1

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#2

The server is closing the connection before it sends even the first line of the HTTP response. Try looking at the server logs for hints about why it might be doing that.


Daniel DeLeo

On Friday, May 9, 2014 at 3:40 AM, Carlos Camacho wrote:

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#3

I just made a lot of tests, re install the chef server using Ubuntu
12.04 LTS Ubuntu 14.04 LTS, and im receiving the same issues. Maybe my
workstation is messed up…

Here are the complete logs…

Stacktrace output from c:/chef/cache/chef-stacktrace.out:

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock
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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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

This is my chef-client output.

PS C:\Users\Administrator> chef-client
[2014-05-09T10:42:42+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in

the middle
attacks.

To fix this issue add an entry like this to your configuration file:

```
  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true
```

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

```
  knife ssl check -c C:\chef\client.rb
```

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Starting Chef Client, version 11.12.4
[2014-05-09T10:42:45+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-09T10:42:45+00:00] INFO: Chef-client pid: 1048

================================================================================
Chef encountered an error attempting to load the node data for "mynode"
================================================================================

Unexpected Error:
-----------------
EOFError: end of file reached

[2014-05-09T10:42:54+00:00] FATAL: Stacktrace dumped to

c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 11.232079 seconds
[2014-05-09T10:42:54+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And this is the output of the knife rackspace create server output:

localhost "Rendering

"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 1"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 2"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 3"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 4"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 5"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 6"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 7"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 8"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 9"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 10"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 11"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 12"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 13"
localhost Checking for existing directory “C:\chef”…
localhost Existing directory not found, creating.
localhost
localhost C:\Users\Administrator>(
localhost echo.url = WScript.Arguments.Named(“url”)
localhost echo.path = WScript.Arguments.Named(“path”)
localhost echo.proxy = null
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP”)
localhost echo.Set wshShell = CreateObject( “WScript.Shell” )
localhost echo.Set objUserVariables = wshShell.Environment(“USER”)
localhost echo.
localhost echo.rem http proxy is optional
localhost echo.rem attempt to read from HTTP_PROXY env var first
localhost echo.On Error Resume Next
localhost echo.
localhost echo.If NOT (objUserVariables(“HTTP_PROXY”) = “”) Then
localhost echo.proxy = objUserVariables(“HTTP_PROXY”)
localhost echo.
localhost echo.rem fall back to named arg
localhost echo.ElseIf NOT (WScript.Arguments.Named(“proxy”) = “”) Then
localhost echo.proxy = WScript.Arguments.Named(“proxy”)
localhost echo.End If
localhost echo.
localhost echo.If NOT isNull(proxy) Then
localhost echo.rem setProxy method is only available on
ServerXMLHTTP 6.0+
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP.6.0”)
localhost echo.objXMLHTTP.setProxy 2, proxy
localhost echo.End If
localhost echo.
localhost echo.On Error Goto 0
localhost echo.
localhost echo.objXMLHTTP.open “GET”, url, false
localhost echo.objXMLHTTP.send()
localhost echo.If objXMLHTTP.Status = 200 Then
localhost echo.Set objADOStream = CreateObject(“ADODB.Stream”)
localhost echo.objADOStream.Open
localhost echo.objADOStream.Type = 1
localhost echo.objADOStream.Write objXMLHTTP.ResponseBody
localhost echo.objADOStream.Position = 0
localhost echo.Set objFSO = Createobject(“Scripting.FileSystemObject”)
localhost echo.If objFSO.Fileexists(path) Then objFSO.DeleteFile path
localhost echo.Set objFSO = Nothing
localhost echo.objADOStream.SaveToFile path
localhost echo.objADOStream.Close
localhost echo.Set objADOStream = Nothing
localhost echo.End if
localhost echo.Set objXMLHTTP = Nothing
localhost ) 1>C:\chef\wget.vbs
localhost
localhost C:\Users\Administrator>(
localhost echo.param(
localhost echo. [String] $remoteUrl,
localhost echo. [String] $localPath
localhost echo.)
localhost echo.
localhost echo.$webClient = new-object System.Net.WebClient;
localhost echo.
localhost echo.$webClient.DownloadFile($remoteUrl, $localPath);
localhost ) 1>C:\chef\wget.ps1
localhost
localhost C:\Users\Administrator>(
localhost
localhost
localhost
localhost )
localhost Detected Windows Version 6.2 Build 9200
localhost
localhost C:\Users\Administrator>goto Version6.2
localhost
localhost C:\Users\Administrator>goto architecture_select
localhost
localhost C:\Users\Administrator>goto Architecture
localhost
localhost C:\Users\Administrator>goto ArchitectureAMD64
localhost
localhost C:\Users\Administrator>goto install
localhost Checking for existing downloaded package at
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost No existing downloaded packages to delete.
localhost Attempting to download client package using cscript…
localhost
localhost C:\Users\Administrator>cscript /nologo C:\chef\wget.vbs
/url:“https://www.opscode.com/chef/download?p=windows&pv=2012&m=x86_64&v=
/path:“C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Download via cscript succeeded.
localhost Installing downloaded client package…
localhost
localhost C:\Users\Administrator>msiexec /qn /log
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-msi23498.log” /i
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Installation completed successfully
localhost Writing validation key…
localhost Validation key written.
localhost
localhost C:\Users\Administrator>mkdir C:\chef\ohai\hints
localhost
localhost C:\Users\Administrator>(echo.{})
1>C:\chef\ohai\hints\rackspace.json
localhost
localhost C:\Users\Administrator>(
localhost echo.log_level :info
localhost echo.log_location STDOUT
localhost echo.
localhost echo.chef_server_url "https://chef.server.net"
localhost echo.validation_client_name "chef-validator"
localhost echo.client_key "c:/chef/client.pem"
localhost echo.validation_key "c:/chef/validation.pem"
localhost echo.
localhost echo.file_cache_path "c:/chef/cache"
localhost echo.file_backup_path "c:/chef/backup"
localhost echo.cache_options ({:path =>
“c:/chef/cache/checksums”, :skip_expires => true})
localhost echo.
localhost echo.node_name "mynode"
localhost ) 1>C:\chef\client.rb
localhost
localhost C:\Users\Administrator>(echo.{“run_list”:[“role[windows]”]})
1>C:\chef\first-boot.json
localhost Starting chef to bootstrap the node…
localhost
localhost C:\Users\Administrator>SET
"PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
localhost
localhost C:\Users\Administrator>chef-client -c c:/chef/client.rb
-j c:/chef/first-boot.json -E _default
localhost [2014-05-09T10:06:37+00:00] WARN:
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost SSL validation of HTTPS requests is disabled. HTTPS

connections are still
localhost encrypted, but chef is not able to detect forged replies
or man in the middle
localhost attacks.
localhost
localhost To fix this issue add an entry like this to your
configuration file:
localhost
localhost localhost # Verify all HTTPS connections (recommended) localhost ssl_verify_mode :verify_peer localhost localhost # OR, Verify only connections to chef-server localhost verify_api_cert true localhost
localhost
localhost To check your SSL configuration, or troubleshoot errors,
you can use the
localhost knife ssl check command like so:
localhost
localhost localhost knife ssl check -c c:/chef/client.rb localhost
localhost
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost
localhost [2014-05-09T10:06:39+00:00] INFO: *** Chef 11.12.4 ***
localhost [2014-05-09T10:06:39+00:00] INFO: Chef-client pid: 1408
localhost [2014-05-09T10:07:14+00:00] INFO: Client key

c:/chef/client.pem is not present - registering
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found: error
localhost [2014-05-09T10:07:15+00:00] INFO: Setting the run_list
to [“role[windows]”] from CLI options
localhost [2014-05-09T10:07:15+00:00] INFO: Run List is [role[windows]]
localhost [2014-05-09T10:07:15+00:00] INFO: Run List expands to
[newrelic::server-monitor-agent, ms_dotnet45, powershell]
localhost [2014-05-09T10:07:15+00:00] INFO: Starting Chef Run for mynode
localhost [2014-05-09T10:07:15+00:00] INFO: Running start handlers
localhost [2014-05-09T10:07:15+00:00] INFO: Start handlers complete.
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found:
localhost
localhost ================================================================================
localhost Error Resolving Cookbooks for Run List:
localhost ================================================================================
localhost
localhost Unexpected Error:
localhost -----------------
localhost EOFError: end of file reached
localhost
localhost [2014-05-09T10:07:15+00:00] ERROR: Running exception handlers
localhost [2014-05-09T10:07:15+00:00] ERROR: Exception handlers complete
localhost [2014-05-09T10:07:15+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
localhost [2014-05-09T10:07:15+00:00] FATAL: EOFError: end of file reached

Thanks!

On Fri, May 9, 2014 at 5:32 PM, Daniel DeLeo dan@kallistec.com wrote:

The server is closing the connection before it sends even the first line of the HTTP response. Try looking at the server logs for hints about why it might be doing that.


Daniel DeLeo

On Friday, May 9, 2014 at 3:40 AM, Carlos Camacho wrote:

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#4

You’ll need to look at the chef-server logs, not clients/knife.

ssh into your chef-server and run chef-server-ctl tail to view the server logs.


Daniel DeLeo

On Friday, May 9, 2014 at 8:38 AM, Carlos Camacho wrote:

I just made a lot of tests, re install the chef server using Ubuntu
12.04 LTS Ubuntu 14.04 LTS, and im receiving the same issues. Maybe my
workstation is messed up…

Here are the complete logs…

Stacktrace output from c:/chef/cache/chef-stacktrace.out:

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock
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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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

This is my chef-client output.

PS C:\Users\Administrator> chef-client
[2014-05-09T10:42:42+00:00] WARN:



SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in
the middle
attacks.

To fix this issue add an entry like this to your configuration file:

# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer
 
# OR, Verify only connections to chef-server
verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
knife ssl check command like so:

knife ssl check -c C:\chef\client.rb


Starting Chef Client, version 11.12.4
[2014-05-09T10:42:45+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-09T10:42:45+00:00] INFO: Chef-client pid: 1048

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-09T10:42:54+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 11.232079 seconds
[2014-05-09T10:42:54+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And this is the output of the knife rackspace create server output:

localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 1"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 2"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 3"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 4"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 5"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 6"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 7"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 8"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 9"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 10"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 11"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 12"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 13"
localhost Checking for existing directory “C:\chef”…
localhost Existing directory not found, creating.
localhost
localhost C:\Users\Administrator>(
localhost echo.url = WScript.Arguments.Named(“url”)
localhost echo.path = WScript.Arguments.Named(“path”)
localhost echo.proxy = null
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP”)
localhost echo.Set wshShell = CreateObject( “WScript.Shell” )
localhost echo.Set objUserVariables = wshShell.Environment(“USER”)
localhost echo.
localhost echo.rem http proxy is optional
localhost echo.rem attempt to read from HTTP_PROXY env var first
localhost echo.On Error Resume Next
localhost echo.
localhost echo.If NOT (objUserVariables(“HTTP_PROXY”) = “”) Then
localhost echo.proxy = objUserVariables(“HTTP_PROXY”)
localhost echo.
localhost echo.rem fall back to named arg
localhost echo.ElseIf NOT (WScript.Arguments.Named(“proxy”) = “”) Then
localhost echo.proxy = WScript.Arguments.Named(“proxy”)
localhost echo.End If
localhost echo.
localhost echo.If NOT isNull(proxy) Then
localhost echo.rem setProxy method is only available on
ServerXMLHTTP 6.0+
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP.6.0”)
localhost echo.objXMLHTTP.setProxy 2, proxy
localhost echo.End If
localhost echo.
localhost echo.On Error Goto 0
localhost echo.
localhost echo.objXMLHTTP.open “GET”, url, false
localhost echo.objXMLHTTP.send()
localhost echo.If objXMLHTTP.Status = 200 Then
localhost echo.Set objADOStream = CreateObject(“ADODB.Stream”)
localhost echo.objADOStream.Open
localhost echo.objADOStream.Type = 1
localhost echo.objADOStream.Write objXMLHTTP.ResponseBody
localhost echo.objADOStream.Position = 0
localhost echo.Set objFSO = Createobject(“Scripting.FileSystemObject”)
localhost echo.If objFSO.Fileexists(path) Then objFSO.DeleteFile path
localhost echo.Set objFSO = Nothing
localhost echo.objADOStream.SaveToFile path
localhost echo.objADOStream.Close
localhost echo.Set objADOStream = Nothing
localhost echo.End if
localhost echo.Set objXMLHTTP = Nothing
localhost ) 1>C:\chef\wget.vbs
localhost
localhost C:\Users\Administrator>(
localhost echo.param(
localhost echo. [String] $remoteUrl,
localhost echo. [String] $localPath
localhost echo.)
localhost echo.
localhost echo.$webClient = new-object System.Net.WebClient;
localhost echo.
localhost echo.$webClient.DownloadFile($remoteUrl, $localPath);
localhost ) 1>C:\chef\wget.ps1
localhost
localhost C:\Users\Administrator>(
localhost
localhost
localhost
localhost )
localhost Detected Windows Version 6.2 Build 9200
localhost
localhost C:\Users\Administrator>goto Version6.2
localhost
localhost C:\Users\Administrator>goto architecture_select
localhost
localhost C:\Users\Administrator>goto Architecture
localhost
localhost C:\Users\Administrator>goto ArchitectureAMD64
localhost
localhost C:\Users\Administrator>goto install
localhost Checking for existing downloaded package at
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost No existing downloaded packages to delete.
localhost Attempting to download client package using cscript…
localhost
localhost C:\Users\Administrator>cscript /nologo C:\chef\wget.vbs
/url:“https://www.opscode.com/chef/download?p=windows&pv=2012&m=x86_64&v=
/path:“C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Download via cscript succeeded.
localhost Installing downloaded client package…
localhost
localhost C:\Users\Administrator>msiexec /qn /log
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-msi23498.log” /i
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Installation completed successfully
localhost Writing validation key…
localhost Validation key written.
localhost
localhost C:\Users\Administrator>mkdir C:\chef\ohai\hints
localhost
localhost C:\Users\Administrator>(echo.{})
1>C:\chef\ohai\hints\rackspace.json
localhost
localhost C:\Users\Administrator>(
localhost echo.log_level :info
localhost echo.log_location STDOUT
localhost echo.
localhost echo.chef_server_url "https://chef.server.net"
localhost echo.validation_client_name "chef-validator"
localhost echo.client_key "c:/chef/client.pem"
localhost echo.validation_key "c:/chef/validation.pem"
localhost echo.
localhost echo.file_cache_path "c:/chef/cache"
localhost echo.file_backup_path "c:/chef/backup"
localhost echo.cache_options ({:path =>
“c:/chef/cache/checksums”, :skip_expires => true})
localhost echo.
localhost echo.node_name "mynode"
localhost ) 1>C:\chef\client.rb
localhost
localhost C:\Users\Administrator>(echo.{“run_list”:[“role[windows]”]})
1>C:\chef\first-boot.json
localhost Starting chef to bootstrap the node…
localhost
localhost C:\Users\Administrator>SET
"PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
localhost
localhost C:\Users\Administrator>chef-client -c c:/chef/client.rb
-j c:/chef/first-boot.json -E _default
localhost [2014-05-09T10:06:37+00:00] WARN:
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost SSL validation of HTTPS requests is disabled. HTTPS
connections are still
localhost encrypted, but chef is not able to detect forged replies
or man in the middle
localhost attacks.
localhost
localhost To fix this issue add an entry like this to your
configuration file:
localhost
localhost localhost # Verify all HTTPS connections (recommended) localhost ssl_verify_mode :verify_peer localhost localhost # OR, Verify only connections to chef-server localhost verify_api_cert true localhost
localhost
localhost To check your SSL configuration, or troubleshoot errors,
you can use the
localhost knife ssl check command like so:
localhost
localhost localhost knife ssl check -c c:/chef/client.rb localhost
localhost
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost
localhost [2014-05-09T10:06:39+00:00] INFO: *** Chef 11.12.4 ***
localhost [2014-05-09T10:06:39+00:00] INFO: Chef-client pid: 1408
localhost [2014-05-09T10:07:14+00:00] INFO: Client key
c:/chef/client.pem is not present - registering
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found: error
localhost [2014-05-09T10:07:15+00:00] INFO: Setting the run_list
to [“role[windows]”] from CLI options
localhost [2014-05-09T10:07:15+00:00] INFO: Run List is [role[windows]]
localhost [2014-05-09T10:07:15+00:00] INFO: Run List expands to
[newrelic::server-monitor-agent, ms_dotnet45, powershell]
localhost [2014-05-09T10:07:15+00:00] INFO: Starting Chef Run for mynode
localhost [2014-05-09T10:07:15+00:00] INFO: Running start handlers
localhost [2014-05-09T10:07:15+00:00] INFO: Start handlers complete.
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found:
localhost
localhost ================================================================================
localhost Error Resolving Cookbooks for Run List:
localhost ================================================================================
localhost
localhost Unexpected Error:
localhost -----------------
localhost EOFError: end of file reached
localhost
localhost [2014-05-09T10:07:15+00:00] ERROR: Running exception handlers
localhost [2014-05-09T10:07:15+00:00] ERROR: Exception handlers complete
localhost [2014-05-09T10:07:15+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
localhost [2014-05-09T10:07:15+00:00] FATAL: EOFError: end of file reached

Thanks!

On Fri, May 9, 2014 at 5:32 PM, Daniel DeLeo <dan@kallistec.com (mailto:dan@kallistec.com)> wrote:

The server is closing the connection before it sends even the first line of the HTTP response. Try looking at the server logs for hints about why it might be doing that.


Daniel DeLeo

On Friday, May 9, 2014 at 3:40 AM, Carlos Camacho wrote:

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#5

Was there ever resolution on this thread?

I just got Chef-Server 11.1.1-1 running on Ubuntu 12.04, and am seeing some
of these types of problems when trying to run chef-client 11.12.8
concurrently across some 60 nodes.

Error Resolving Cookbooks for Run List:
Unknown Server Error: "The server had a fatal error attempting to load the
node data."
Server Response: internal service error

Recipe Compile Error in /var/chef/cache/cookbooks/ourcookbook/recipe.rb
Net::HTTPFatalError: 500 "Internal Server Error"
Trace:… points to line where we load data_bag_item from server

Other failures point to server-side issues, as they fail on search queries.

Am open to debugging ideas, let me know what I should be hunting for.

-Mike

On Wed, May 28, 2014 at 5:23 PM, Lamont Granquist lamont@opscode.com
wrote:

The “End of File” is getting thrown because the socket connection gets
torn down (“everything is a file” on unix (but not really, see plan9…)).

On 5/28/14, 11:35 AM, Adam Edwards wrote:

Hello Carlos – do you have the output of c:/chef/cache/chef-stacktrace.
out
from this last failure? And if it still repros, can you run with -l debug?

The error implies some sort of invalid file that is being accessed –
Lamont, can you tell the context from the output we have below?

-Adam

-----Original Message-----
From: Carlos Camacho [mailto:carlos.camacho@frontiersin.org]
Sent: Tuesday, May 27, 2014 2:55 AM
To: Lamont Granquist
Cc: Adam Edwards; chef@lists.opscode.com
Subject: Re: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Problem running
chef-client, just from 2 days ago.

Something really odd just happened.

I restarted the chef server and run the chef-client from Windows and it
worked fine… A few seconds later i executed the same command again and i
had the error… o.O

Check this out…

PS C:\Users\Administrator> chef-client
Starting Chef Client, version 11.12.4
[2014-05-27T09:43:31+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-27T09:43:31+00:00] INFO: Chef-client pid: 3952
[2014-05-27T09:43:39+00:00] INFO: Run List is [role[windows]]
[2014-05-27T09:43:39+00:00] INFO: Run List expands to []
[2014-05-27T09:43:39+00:00] INFO: Starting Chef Run for slwnone10
[2014-05-27T09:43:39+00:00] INFO: Running start handlers
[2014-05-27T09:43:39+00:00] INFO: Start handlers complete.
[2014-05-27T09:43:39+00:00] INFO: HTTP Request Returned 404 Object Not
Found:
resolving cookbooks for run list: []
[2014-05-27T09:43:39+00:00] INFO: Loading cookbooks [] Synchronizing
Cookbooks:
Compiling Cookbooks…
Converging 0 resources
[2014-05-27T09:43:39+00:00] INFO: Chef Run complete in 0.561614 seconds

Running handlers:
[2014-05-27T09:43:39+00:00] INFO: Running report handlers Running handlers
complete [2014-05-27T09:43:39+00:00] INFO: Report handlers complete Chef
Client finished, 0/0 resources updated in 11.029288 seconds

PS C:\Users\Administrator> chef-client
Starting Chef Client, version 11.12.4
[2014-05-27T09:43:51+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-27T09:43:51+00:00] INFO: Chef-client pid: 3580
[2014-05-27T09:43:59+00:00] INFO: Run List is [role[windows]]
[2014-05-27T09:43:59+00:00] INFO: Run List expands to []
[2014-05-27T09:43:59+00:00] INFO: Starting Chef Run for slwnone10
[2014-05-27T09:43:59+00:00] INFO: Running start handlers
[2014-05-27T09:43:59+00:00] INFO: Start handlers complete.
[2014-05-27T09:43:59+00:00] INFO: HTTP Request Returned 404 Object Not
Found:
resolving cookbooks for run list: []
[2014-05-27T09:43:59+00:00] INFO: Loading cookbooks [] Synchronizing
Cookbooks:
Compiling Cookbooks…
Converging 0 resources

Running handlers:
[2014-05-27T09:43:59+00:00] ERROR: Running exception handlers Running
handlers complete [2014-05-27T09:43:59+00:00] ERROR: Exception handlers
complete [2014-05-27T09:43:59+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out Chef Client failed. 0 resources
updated in
10.670475 seconds [2014-05-27T09:43:59+00:00] FATAL: EOFError: end of file
reached

On Tue, May 27, 2014 at 10:54 AM, Carlos Camacho
carlos.camacho@frontiersin.org wrote:

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 lamont@opscode.com
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
lamont@opscode.com
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
FIN|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.


#6

Hello,

Yes, the problem was with the flavor and the image used in Rackspace.

Both images are for Windows Server 2012.

This image has a problem and chef doesn’t work…
c50f70fc-79ec-4c71-bd4a-a4ac8f1641e1

This image works perfect.
715e6459-0330-4f36-89e7-19fb3cfe8620

Also, performance flavors didn’t work for me.

Cheers

On Sun, Jun 8, 2014 at 7:12 PM, Mike miketheman@gmail.com wrote:

Was there ever resolution on this thread?

I just got Chef-Server 11.1.1-1 running on Ubuntu 12.04, and am seeing some
of these types of problems when trying to run chef-client 11.12.8
concurrently across some 60 nodes.

Error Resolving Cookbooks for Run List:
Unknown Server Error: "The server had a fatal error attempting to load the
node data."
Server Response: internal service error

Recipe Compile Error in /var/chef/cache/cookbooks/ourcookbook/recipe.rb
Net::HTTPFatalError: 500 "Internal Server Error"
Trace:… points to line where we load data_bag_item from server

Other failures point to server-side issues, as they fail on search queries.

Am open to debugging ideas, let me know what I should be hunting for.

-Mike

On Wed, May 28, 2014 at 5:23 PM, Lamont Granquist lamont@opscode.com
wrote:

The “End of File” is getting thrown because the socket connection gets
torn down (“everything is a file” on unix (but not really, see plan9…)).

On 5/28/14, 11:35 AM, Adam Edwards wrote:

Hello Carlos – do you have the output of
c:/chef/cache/chef-stacktrace.out
from this last failure? And if it still repros, can you run with -l
debug?

The error implies some sort of invalid file that is being accessed –
Lamont, can you tell the context from the output we have below?

-Adam

-----Original Message-----
From: Carlos Camacho [mailto:carlos.camacho@frontiersin.org]
Sent: Tuesday, May 27, 2014 2:55 AM
To: Lamont Granquist
Cc: Adam Edwards; chef@lists.opscode.com
Subject: Re: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Problem running
chef-client, just from 2 days ago.

Something really odd just happened.

I restarted the chef server and run the chef-client from Windows and it
worked fine… A few seconds later i executed the same command again and
i
had the error… o.O

Check this out…

PS C:\Users\Administrator> chef-client
Starting Chef Client, version 11.12.4
[2014-05-27T09:43:31+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-27T09:43:31+00:00] INFO: Chef-client pid: 3952
[2014-05-27T09:43:39+00:00] INFO: Run List is [role[windows]]
[2014-05-27T09:43:39+00:00] INFO: Run List expands to []
[2014-05-27T09:43:39+00:00] INFO: Starting Chef Run for slwnone10
[2014-05-27T09:43:39+00:00] INFO: Running start handlers
[2014-05-27T09:43:39+00:00] INFO: Start handlers complete.
[2014-05-27T09:43:39+00:00] INFO: HTTP Request Returned 404 Object Not
Found:
resolving cookbooks for run list: []
[2014-05-27T09:43:39+00:00] INFO: Loading cookbooks [] Synchronizing
Cookbooks:
Compiling Cookbooks…
Converging 0 resources
[2014-05-27T09:43:39+00:00] INFO: Chef Run complete in 0.561614 seconds

Running handlers:
[2014-05-27T09:43:39+00:00] INFO: Running report handlers Running
handlers
complete [2014-05-27T09:43:39+00:00] INFO: Report handlers complete Chef
Client finished, 0/0 resources updated in 11.029288 seconds

PS C:\Users\Administrator> chef-client
Starting Chef Client, version 11.12.4
[2014-05-27T09:43:51+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-27T09:43:51+00:00] INFO: Chef-client pid: 3580
[2014-05-27T09:43:59+00:00] INFO: Run List is [role[windows]]
[2014-05-27T09:43:59+00:00] INFO: Run List expands to []
[2014-05-27T09:43:59+00:00] INFO: Starting Chef Run for slwnone10
[2014-05-27T09:43:59+00:00] INFO: Running start handlers
[2014-05-27T09:43:59+00:00] INFO: Start handlers complete.
[2014-05-27T09:43:59+00:00] INFO: HTTP Request Returned 404 Object Not
Found:
resolving cookbooks for run list: []
[2014-05-27T09:43:59+00:00] INFO: Loading cookbooks [] Synchronizing
Cookbooks:
Compiling Cookbooks…
Converging 0 resources

Running handlers:
[2014-05-27T09:43:59+00:00] ERROR: Running exception handlers Running
handlers complete [2014-05-27T09:43:59+00:00] ERROR: Exception handlers
complete [2014-05-27T09:43:59+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out Chef Client failed. 0 resources updated
in
10.670475 seconds [2014-05-27T09:43:59+00:00] FATAL: EOFError: end of
file
reached

On Tue, May 27, 2014 at 10:54 AM, Carlos Camacho
carlos.camacho@frontiersin.org wrote:

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 lamont@opscode.com
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
lamont@opscode.com
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
FIN|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.


#7

On Sunday, June 8, 2014 at 10:12 AM, Mike wrote:

Was there ever resolution on this thread?

I just got Chef-Server 11.1.1-1 running on Ubuntu 12.04, and am seeing some of these types of problems when trying to run chef-client 11.12.8 concurrently across some 60 nodes.

Error Resolving Cookbooks for Run List:
Unknown Server Error: "The server had a fatal error attempting to load the node data."
Server Response: internal service error

Recipe Compile Error in /var/chef/cache/cookbooks/ourcookbook/recipe.rb
Net::HTTPFatalError: 500 "Internal Server Error"
Trace:… points to line where we load data_bag_item from server

Other failures point to server-side issues, as they fail on search queries.

Am open to debugging ideas, let me know what I should be hunting for.

-Mike

Run chef-server-ctl tail on your Chef Server machine to see the logs. There’s also a status command to tell you if any of the required services isn’t running.


Daniel DeLeo


#8

Hello, its a really odd problem… Check the chef logs…

==> /var/log/chef-server/nginx/access.log <==
chef.server - - [13/May/2014:06:45:27 +0000] “GET /nodes/mynode
HTTP/1.1” 200 “0.011” 16264 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.011” “11.12.4” “algorithm=sha1;version=1.0;” "mynode "
“2014-05-13T06:45:27Z” “2jmj7l5rSw0yVb/vlWAYkK/YBwk=” 999

==> /var/log/chef-server/erchef/erchef.log.1 <==
2014-05-13T06:45:27Z erchef@127.0.0.1 INFO
req_id=65+VupG/n3XInsE2MRqX8A==; status=200; method=GET;
path=/nodes/mynode ; user=mynode ; msg=[]; req_time=7; rdbms_time=2;
rdbms_count=2

All seems to be 200 XD…

I don’t know were to find more information about the error…

From the client, the output…


Starting Chef Client, version 11.12.4
[2014-05-13T06:45:19+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-13T06:45:19+00:00] INFO: Chef-client pid: 2612

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-13T06:45:27+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 14.457618 seconds
[2014-05-13T06:45:27+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

Cheers!!

On Fri, May 9, 2014 at 6:07 PM, Daniel DeLeo dan@kallistec.com wrote:

You’ll need to look at the chef-server logs, not clients/knife.

ssh into your chef-server and run chef-server-ctl tail to view the server logs.


Daniel DeLeo

On Friday, May 9, 2014 at 8:38 AM, Carlos Camacho wrote:

I just made a lot of tests, re install the chef server using Ubuntu
12.04 LTS Ubuntu 14.04 LTS, and im receiving the same issues. Maybe my
workstation is messed up…

Here are the complete logs…

Stacktrace output from c:/chef/cache/chef-stacktrace.out:

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock
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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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

This is my chef-client output.

PS C:\Users\Administrator> chef-client
[2014-05-09T10:42:42+00:00] WARN:



SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in
the middle
attacks.

To fix this issue add an entry like this to your configuration file:

# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer

# OR, Verify only connections to chef-server
verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
knife ssl check command like so:

knife ssl check -c C:\chef\client.rb


Starting Chef Client, version 11.12.4
[2014-05-09T10:42:45+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-09T10:42:45+00:00] INFO: Chef-client pid: 1048

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-09T10:42:54+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 11.232079 seconds
[2014-05-09T10:42:54+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And this is the output of the knife rackspace create server output:

localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 1"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 2"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 3"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 4"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 5"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 6"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 7"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 8"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 9"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 10"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 11"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 12"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 13"
localhost Checking for existing directory “C:\chef”…
localhost Existing directory not found, creating.
localhost
localhost C:\Users\Administrator>(
localhost echo.url = WScript.Arguments.Named(“url”)
localhost echo.path = WScript.Arguments.Named(“path”)
localhost echo.proxy = null
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP”)
localhost echo.Set wshShell = CreateObject( “WScript.Shell” )
localhost echo.Set objUserVariables = wshShell.Environment(“USER”)
localhost echo.
localhost echo.rem http proxy is optional
localhost echo.rem attempt to read from HTTP_PROXY env var first
localhost echo.On Error Resume Next
localhost echo.
localhost echo.If NOT (objUserVariables(“HTTP_PROXY”) = “”) Then
localhost echo.proxy = objUserVariables(“HTTP_PROXY”)
localhost echo.
localhost echo.rem fall back to named arg
localhost echo.ElseIf NOT (WScript.Arguments.Named(“proxy”) = “”) Then
localhost echo.proxy = WScript.Arguments.Named(“proxy”)
localhost echo.End If
localhost echo.
localhost echo.If NOT isNull(proxy) Then
localhost echo.rem setProxy method is only available on
ServerXMLHTTP 6.0+
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP.6.0”)
localhost echo.objXMLHTTP.setProxy 2, proxy
localhost echo.End If
localhost echo.
localhost echo.On Error Goto 0
localhost echo.
localhost echo.objXMLHTTP.open “GET”, url, false
localhost echo.objXMLHTTP.send()
localhost echo.If objXMLHTTP.Status = 200 Then
localhost echo.Set objADOStream = CreateObject(“ADODB.Stream”)
localhost echo.objADOStream.Open
localhost echo.objADOStream.Type = 1
localhost echo.objADOStream.Write objXMLHTTP.ResponseBody
localhost echo.objADOStream.Position = 0
localhost echo.Set objFSO = Createobject(“Scripting.FileSystemObject”)
localhost echo.If objFSO.Fileexists(path) Then objFSO.DeleteFile path
localhost echo.Set objFSO = Nothing
localhost echo.objADOStream.SaveToFile path
localhost echo.objADOStream.Close
localhost echo.Set objADOStream = Nothing
localhost echo.End if
localhost echo.Set objXMLHTTP = Nothing
localhost ) 1>C:\chef\wget.vbs
localhost
localhost C:\Users\Administrator>(
localhost echo.param(
localhost echo. [String] $remoteUrl,
localhost echo. [String] $localPath
localhost echo.)
localhost echo.
localhost echo.$webClient = new-object System.Net.WebClient;
localhost echo.
localhost echo.$webClient.DownloadFile($remoteUrl, $localPath);
localhost ) 1>C:\chef\wget.ps1
localhost
localhost C:\Users\Administrator>(
localhost
localhost
localhost
localhost )
localhost Detected Windows Version 6.2 Build 9200
localhost
localhost C:\Users\Administrator>goto Version6.2
localhost
localhost C:\Users\Administrator>goto architecture_select
localhost
localhost C:\Users\Administrator>goto Architecture
localhost
localhost C:\Users\Administrator>goto ArchitectureAMD64
localhost
localhost C:\Users\Administrator>goto install
localhost Checking for existing downloaded package at
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost No existing downloaded packages to delete.
localhost Attempting to download client package using cscript…
localhost
localhost C:\Users\Administrator>cscript /nologo C:\chef\wget.vbs
/url:“https://www.opscode.com/chef/download?p=windows&pv=2012&m=x86_64&v=
/path:“C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Download via cscript succeeded.
localhost Installing downloaded client package…
localhost
localhost C:\Users\Administrator>msiexec /qn /log
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-msi23498.log” /i
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Installation completed successfully
localhost Writing validation key…
localhost Validation key written.
localhost
localhost C:\Users\Administrator>mkdir C:\chef\ohai\hints
localhost
localhost C:\Users\Administrator>(echo.{})
1>C:\chef\ohai\hints\rackspace.json
localhost
localhost C:\Users\Administrator>(
localhost echo.log_level :info
localhost echo.log_location STDOUT
localhost echo.
localhost echo.chef_server_url "https://chef.server.net"
localhost echo.validation_client_name "chef-validator"
localhost echo.client_key "c:/chef/client.pem"
localhost echo.validation_key "c:/chef/validation.pem"
localhost echo.
localhost echo.file_cache_path "c:/chef/cache"
localhost echo.file_backup_path "c:/chef/backup"
localhost echo.cache_options ({:path =>
“c:/chef/cache/checksums”, :skip_expires => true})
localhost echo.
localhost echo.node_name "mynode"
localhost ) 1>C:\chef\client.rb
localhost
localhost C:\Users\Administrator>(echo.{“run_list”:[“role[windows]”]})
1>C:\chef\first-boot.json
localhost Starting chef to bootstrap the node…
localhost
localhost C:\Users\Administrator>SET
"PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
localhost
localhost C:\Users\Administrator>chef-client -c c:/chef/client.rb
-j c:/chef/first-boot.json -E _default
localhost [2014-05-09T10:06:37+00:00] WARN:
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost SSL validation of HTTPS requests is disabled. HTTPS
connections are still
localhost encrypted, but chef is not able to detect forged replies
or man in the middle
localhost attacks.
localhost
localhost To fix this issue add an entry like this to your
configuration file:
localhost
localhost localhost # Verify all HTTPS connections (recommended) localhost ssl_verify_mode :verify_peer localhost localhost # OR, Verify only connections to chef-server localhost verify_api_cert true localhost
localhost
localhost To check your SSL configuration, or troubleshoot errors,
you can use the
localhost knife ssl check command like so:
localhost
localhost localhost knife ssl check -c c:/chef/client.rb localhost
localhost
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost
localhost [2014-05-09T10:06:39+00:00] INFO: *** Chef 11.12.4 ***
localhost [2014-05-09T10:06:39+00:00] INFO: Chef-client pid: 1408
localhost [2014-05-09T10:07:14+00:00] INFO: Client key
c:/chef/client.pem is not present - registering
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found: error
localhost [2014-05-09T10:07:15+00:00] INFO: Setting the run_list
to [“role[windows]”] from CLI options
localhost [2014-05-09T10:07:15+00:00] INFO: Run List is [role[windows]]
localhost [2014-05-09T10:07:15+00:00] INFO: Run List expands to
[newrelic::server-monitor-agent, ms_dotnet45, powershell]
localhost [2014-05-09T10:07:15+00:00] INFO: Starting Chef Run for mynode
localhost [2014-05-09T10:07:15+00:00] INFO: Running start handlers
localhost [2014-05-09T10:07:15+00:00] INFO: Start handlers complete.
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found:
localhost
localhost ================================================================================
localhost Error Resolving Cookbooks for Run List:
localhost ================================================================================
localhost
localhost Unexpected Error:
localhost -----------------
localhost EOFError: end of file reached
localhost
localhost [2014-05-09T10:07:15+00:00] ERROR: Running exception handlers
localhost [2014-05-09T10:07:15+00:00] ERROR: Exception handlers complete
localhost [2014-05-09T10:07:15+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
localhost [2014-05-09T10:07:15+00:00] FATAL: EOFError: end of file reached

Thanks!

On Fri, May 9, 2014 at 5:32 PM, Daniel DeLeo <dan@kallistec.com (mailto:dan@kallistec.com)> wrote:

The server is closing the connection before it sends even the first line of the HTTP response. Try looking at the server logs for hints about why it might be doing that.


Daniel DeLeo

On Friday, May 9, 2014 at 3:40 AM, Carlos Camacho wrote:

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#9

Hello!

I already isolated the problem, i have a case base, and from that
point i’ll try to fix it.

PROBLEM:
chef-client errors when it is executed (EOF exception). This is a
chef-server and node as Rackspace virtual machines.

SOURCE OF THE PROBLEM:
A RST TCP package sent to the client in some point in the connection
(Using Default Rackspace RackConnect network).

SOLUTION TO ISOLATE THE PROBLEM:
Create a VPN tunnel between the server and the node and it works flawlessly.

REAL SOLUTION:
I created a ticket in Rackspace and they told me that the rackconnect
network doesn’t have any restriction, so I’m discussing that with
them.
Do you know reasons to this RST package appears?

Thanks!

On Tue, May 13, 2014 at 8:50 AM, Carlos Camacho
carlos.camacho@frontiersin.org wrote:

Hello, its a really odd problem… Check the chef logs…

==> /var/log/chef-server/nginx/access.log <==
chef.server - - [13/May/2014:06:45:27 +0000] “GET /nodes/mynode
HTTP/1.1” 200 “0.011” 16264 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.011” “11.12.4” “algorithm=sha1;version=1.0;” "mynode "
“2014-05-13T06:45:27Z” “2jmj7l5rSw0yVb/vlWAYkK/YBwk=” 999

==> /var/log/chef-server/erchef/erchef.log.1 <==
2014-05-13T06:45:27Z erchef@127.0.0.1 INFO
req_id=65+VupG/n3XInsE2MRqX8A==; status=200; method=GET;
path=/nodes/mynode ; user=mynode ; msg=[]; req_time=7; rdbms_time=2;
rdbms_count=2

All seems to be 200 XD…

I don’t know were to find more information about the error…

From the client, the output…


Starting Chef Client, version 11.12.4
[2014-05-13T06:45:19+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-13T06:45:19+00:00] INFO: Chef-client pid: 2612

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-13T06:45:27+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 14.457618 seconds
[2014-05-13T06:45:27+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

Cheers!!

On Fri, May 9, 2014 at 6:07 PM, Daniel DeLeo dan@kallistec.com wrote:

You’ll need to look at the chef-server logs, not clients/knife.

ssh into your chef-server and run chef-server-ctl tail to view the server logs.


Daniel DeLeo

On Friday, May 9, 2014 at 8:38 AM, Carlos Camacho wrote:

I just made a lot of tests, re install the chef server using Ubuntu
12.04 LTS Ubuntu 14.04 LTS, and im receiving the same issues. Maybe my
workstation is messed up…

Here are the complete logs…

Stacktrace output from c:/chef/cache/chef-stacktrace.out:

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock
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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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

This is my chef-client output.

PS C:\Users\Administrator> chef-client
[2014-05-09T10:42:42+00:00] WARN:



SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in
the middle
attacks.

To fix this issue add an entry like this to your configuration file:

# Verify all HTTPS connections (recommended)
ssl_verify_mode :verify_peer

# OR, Verify only connections to chef-server
verify_api_cert true

To check your SSL configuration, or troubleshoot errors, you can use the
knife ssl check command like so:

knife ssl check -c C:\chef\client.rb


Starting Chef Client, version 11.12.4
[2014-05-09T10:42:45+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-09T10:42:45+00:00] INFO: Chef-client pid: 1048

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-09T10:42:54+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 11.232079 seconds
[2014-05-09T10:42:54+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And this is the output of the knife rackspace create server output:

localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 1"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 2"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 3"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 4"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 5"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 6"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 7"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 8"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 9"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 10"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 11"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 12"
localhost "Rendering
"C:\Users\ADMINI~1\AppData\Local\Temp\bootstrap-7917-1399629922.bat"
chunk 13"
localhost Checking for existing directory “C:\chef”…
localhost Existing directory not found, creating.
localhost
localhost C:\Users\Administrator>(
localhost echo.url = WScript.Arguments.Named(“url”)
localhost echo.path = WScript.Arguments.Named(“path”)
localhost echo.proxy = null
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP”)
localhost echo.Set wshShell = CreateObject( “WScript.Shell” )
localhost echo.Set objUserVariables = wshShell.Environment(“USER”)
localhost echo.
localhost echo.rem http proxy is optional
localhost echo.rem attempt to read from HTTP_PROXY env var first
localhost echo.On Error Resume Next
localhost echo.
localhost echo.If NOT (objUserVariables(“HTTP_PROXY”) = “”) Then
localhost echo.proxy = objUserVariables(“HTTP_PROXY”)
localhost echo.
localhost echo.rem fall back to named arg
localhost echo.ElseIf NOT (WScript.Arguments.Named(“proxy”) = “”) Then
localhost echo.proxy = WScript.Arguments.Named(“proxy”)
localhost echo.End If
localhost echo.
localhost echo.If NOT isNull(proxy) Then
localhost echo.rem setProxy method is only available on
ServerXMLHTTP 6.0+
localhost echo.Set objXMLHTTP = CreateObject(“MSXML2.ServerXMLHTTP.6.0”)
localhost echo.objXMLHTTP.setProxy 2, proxy
localhost echo.End If
localhost echo.
localhost echo.On Error Goto 0
localhost echo.
localhost echo.objXMLHTTP.open “GET”, url, false
localhost echo.objXMLHTTP.send()
localhost echo.If objXMLHTTP.Status = 200 Then
localhost echo.Set objADOStream = CreateObject(“ADODB.Stream”)
localhost echo.objADOStream.Open
localhost echo.objADOStream.Type = 1
localhost echo.objADOStream.Write objXMLHTTP.ResponseBody
localhost echo.objADOStream.Position = 0
localhost echo.Set objFSO = Createobject(“Scripting.FileSystemObject”)
localhost echo.If objFSO.Fileexists(path) Then objFSO.DeleteFile path
localhost echo.Set objFSO = Nothing
localhost echo.objADOStream.SaveToFile path
localhost echo.objADOStream.Close
localhost echo.Set objADOStream = Nothing
localhost echo.End if
localhost echo.Set objXMLHTTP = Nothing
localhost ) 1>C:\chef\wget.vbs
localhost
localhost C:\Users\Administrator>(
localhost echo.param(
localhost echo. [String] $remoteUrl,
localhost echo. [String] $localPath
localhost echo.)
localhost echo.
localhost echo.$webClient = new-object System.Net.WebClient;
localhost echo.
localhost echo.$webClient.DownloadFile($remoteUrl, $localPath);
localhost ) 1>C:\chef\wget.ps1
localhost
localhost C:\Users\Administrator>(
localhost
localhost
localhost
localhost )
localhost Detected Windows Version 6.2 Build 9200
localhost
localhost C:\Users\Administrator>goto Version6.2
localhost
localhost C:\Users\Administrator>goto architecture_select
localhost
localhost C:\Users\Administrator>goto Architecture
localhost
localhost C:\Users\Administrator>goto ArchitectureAMD64
localhost
localhost C:\Users\Administrator>goto install
localhost Checking for existing downloaded package at
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost No existing downloaded packages to delete.
localhost Attempting to download client package using cscript…
localhost
localhost C:\Users\Administrator>cscript /nologo C:\chef\wget.vbs
/url:“https://www.opscode.com/chef/download?p=windows&pv=2012&m=x86_64&v=
/path:“C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Download via cscript succeeded.
localhost Installing downloaded client package…
localhost
localhost C:\Users\Administrator>msiexec /qn /log
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-msi23498.log” /i
"C:\Users\ADMINI~1\AppData\Local\Temp\chef-client-latest.msi"
localhost Installation completed successfully
localhost Writing validation key…
localhost Validation key written.
localhost
localhost C:\Users\Administrator>mkdir C:\chef\ohai\hints
localhost
localhost C:\Users\Administrator>(echo.{})
1>C:\chef\ohai\hints\rackspace.json
localhost
localhost C:\Users\Administrator>(
localhost echo.log_level :info
localhost echo.log_location STDOUT
localhost echo.
localhost echo.chef_server_url "https://chef.server.net"
localhost echo.validation_client_name "chef-validator"
localhost echo.client_key "c:/chef/client.pem"
localhost echo.validation_key "c:/chef/validation.pem"
localhost echo.
localhost echo.file_cache_path "c:/chef/cache"
localhost echo.file_backup_path "c:/chef/backup"
localhost echo.cache_options ({:path =>
“c:/chef/cache/checksums”, :skip_expires => true})
localhost echo.
localhost echo.node_name "mynode"
localhost ) 1>C:\chef\client.rb
localhost
localhost C:\Users\Administrator>(echo.{“run_list”:[“role[windows]”]})
1>C:\chef\first-boot.json
localhost Starting chef to bootstrap the node…
localhost
localhost C:\Users\Administrator>SET
"PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
localhost
localhost C:\Users\Administrator>chef-client -c c:/chef/client.rb
-j c:/chef/first-boot.json -E _default
localhost [2014-05-09T10:06:37+00:00] WARN:
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost SSL validation of HTTPS requests is disabled. HTTPS
connections are still
localhost encrypted, but chef is not able to detect forged replies
or man in the middle
localhost attacks.
localhost
localhost To fix this issue add an entry like this to your
configuration file:
localhost
localhost localhost # Verify all HTTPS connections (recommended) localhost ssl_verify_mode :verify_peer localhost localhost # OR, Verify only connections to chef-server localhost verify_api_cert true localhost
localhost
localhost To check your SSL configuration, or troubleshoot errors,
you can use the
localhost knife ssl check command like so:
localhost
localhost localhost knife ssl check -c c:/chef/client.rb localhost
localhost
localhost * * * * * * * * * * * * * * * * * * * * * * * * * * * *


localhost
localhost [2014-05-09T10:06:39+00:00] INFO: *** Chef 11.12.4 ***
localhost [2014-05-09T10:06:39+00:00] INFO: Chef-client pid: 1408
localhost [2014-05-09T10:07:14+00:00] INFO: Client key
c:/chef/client.pem is not present - registering
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found: error
localhost [2014-05-09T10:07:15+00:00] INFO: Setting the run_list
to [“role[windows]”] from CLI options
localhost [2014-05-09T10:07:15+00:00] INFO: Run List is [role[windows]]
localhost [2014-05-09T10:07:15+00:00] INFO: Run List expands to
[newrelic::server-monitor-agent, ms_dotnet45, powershell]
localhost [2014-05-09T10:07:15+00:00] INFO: Starting Chef Run for mynode
localhost [2014-05-09T10:07:15+00:00] INFO: Running start handlers
localhost [2014-05-09T10:07:15+00:00] INFO: Start handlers complete.
localhost [2014-05-09T10:07:15+00:00] INFO: HTTP Request Returned
404 Object Not Found:
localhost
localhost ================================================================================
localhost Error Resolving Cookbooks for Run List:
localhost ================================================================================
localhost
localhost Unexpected Error:
localhost -----------------
localhost EOFError: end of file reached
localhost
localhost [2014-05-09T10:07:15+00:00] ERROR: Running exception handlers
localhost [2014-05-09T10:07:15+00:00] ERROR: Exception handlers complete
localhost [2014-05-09T10:07:15+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
localhost [2014-05-09T10:07:15+00:00] FATAL: EOFError: end of file reached

Thanks!

On Fri, May 9, 2014 at 5:32 PM, Daniel DeLeo <dan@kallistec.com (mailto:dan@kallistec.com)> wrote:

The server is closing the connection before it sends even the first line of the HTTP response. Try looking at the server logs for hints about why it might be doing that.


Daniel DeLeo

On Friday, May 9, 2014 at 3:40 AM, Carlos Camacho wrote:

Hello!

I’m having some troubles with new windows node deployments. The
chef-client fails with this error

I want to solve this, but i don’t know were to find errors which can
help me to solve this.

Thanks!!!

Generated at 2014-05-09 10:37:19 +0000
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:inread_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:inreaduntil’
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:inread_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:inblock 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:intransport_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:inrequest’
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:instart’
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:inrequest’
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:inblock 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:insend_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/rest.rb:115:inget’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:507:in
load' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/node.rb:491:infind_or_create’
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:92:in
load_node' C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:249:inload_node’
C:/opscode/chef/embedded/lib/ruby/gems/1.9.1/gems/chef-11.12.4-x86-mingw32/lib/chef/client.rb:418: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:inrun’
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:inblock 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:inrun_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


#10

On Wednesday, May 14, 2014 at 6:43 AM, Carlos Camacho wrote:

Hello!

I already isolated the problem, i have a case base, and from that
point i’ll try to fix it.

PROBLEM:
chef-client errors when it is executed (EOF exception). This is a
chef-server and node as Rackspace virtual machines.

SOURCE OF THE PROBLEM:
A RST TCP package sent to the client in some point in the connection
(Using Default Rackspace RackConnect network).

SOLUTION TO ISOLATE THE PROBLEM:
Create a VPN tunnel between the server and the node and it works flawlessly.

REAL SOLUTION:
I created a ticket in Rackspace and they told me that the rackconnect
network doesn’t have any restriction, so I’m discussing that with
them.
Do you know reasons to this RST package appears?

Thanks!
Could be a configuration issue with your firewall that connects your rack connect stuff, or on the server itself. You’ll probably have to run tcpdump on the chef server box to see if it sends the RST packet or not.


Daniel DeLeo


#11

Daniel! Thanks for your answer,

The RST package it is being send from the chef server, but i don’t
know why, or the service which is failing.

Can you recommend me things to test?!?!

Thanks!

On Wed, May 14, 2014 at 5:57 PM, Daniel DeLeo dan@kallistec.com wrote:

On Wednesday, May 14, 2014 at 6:43 AM, Carlos Camacho wrote:

Hello!

I already isolated the problem, i have a case base, and from that
point i’ll try to fix it.

PROBLEM:
chef-client errors when it is executed (EOF exception). This is a
chef-server and node as Rackspace virtual machines.

SOURCE OF THE PROBLEM:
A RST TCP package sent to the client in some point in the connection
(Using Default Rackspace RackConnect network).

SOLUTION TO ISOLATE THE PROBLEM:
Create a VPN tunnel between the server and the node and it works flawlessly.

REAL SOLUTION:
I created a ticket in Rackspace and they told me that the rackconnect
network doesn’t have any restriction, so I’m discussing that with
them.
Do you know reasons to this RST package appears?

Thanks!
Could be a configuration issue with your firewall that connects your rack connect stuff, or on the server itself. You’ll probably have to run tcpdump on the chef server box to see if it sends the RST packet or not.


Daniel DeLeo


#12

On Thursday, May 15, 2014 at 10:06 AM, Carlos Camacho wrote:

Daniel! Thanks for your answer,

The RST package it is being send from the chef server, but i don’t
know why, or the service which is failing.

Can you recommend me things to test?!?!

Thanks!

Is there a firewall on the server itself?


Daniel DeLeo


#13

Daniel, i have the default iptables rules from rackspace.

It is a very long list and i jut run this to clean it a little bit.

iptables --policy INPUT ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy FORWARD ACCEPT
iptables -F INPUT
iptables -F OUTPUT
iptables -F FORWARD
iptables -F RS-RackConnect-INBOUND
iptables -X RS-RackConnect-INBOUND

Now the output is this.

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Also in windows i disabled the windows firewall (It is important to
tell that this problem only happens with Windows nodes).

Now the chef-client output changed a little bit…

This is now…

[2014-05-16T06:53:30+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-16T06:53:30+00:00] INFO: Chef-client pid: 3924
[2014-05-16T06:53:37+00:00] INFO: Run List is [recipe[frontiers_test]]
[2014-05-16T06:53:37+00:00] INFO: Run List expands to [frontiers_test]
[2014-05-16T06:53:37+00:00] INFO: Starting Chef Run for slwnone09
[2014-05-16T06:53:37+00:00] INFO: Running start handlers
[2014-05-16T06:53:37+00:00] INFO: Start handlers complete.
[2014-05-16T06:53:37+00:00] INFO: HTTP Request Returned 404 Object Not Found:
resolving cookbooks for run list: [“frontiers_test”]
[2014-05-16T06:53:38+00:00] INFO: Loading cookbooks [cookbook_test@0.1.0]
Synchronizing Cookbooks:

  • cookbook_test
    Compiling Cookbooks…
    Converging 1 resources
    Recipe:cookbook_test::default
  • directory[C:\hello_test] action create[2014-05-16T06:53:38+00:00]
    INFO: Processing directory[C:\hello_test
    ] action create (cookbook_test::default line 10)
    (up to date)

Running handlers:
[2014-05-16T06:53:38+00:00] ERROR: Running exception handlers
Running handlers complete
[2014-05-16T06:53:38+00:00] ERROR: Exception handlers complete
[2014-05-16T06:53:38+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.324711 seconds
[2014-05-16T06:53:38+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And before the output was…

Starting Chef Client, version 11.12.4
[2014-05-14T14:02:26+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-14T14:02:26+00:00] INFO: Chef-client pid: 2936

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-14T14:02:34+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.154057 seconds
[2014-05-14T14:02:34+00:00] FATAL: EOFError: end of file reached

So, it is really annoying not to have any help from rackspace, they
only tells me, it is a server problem, not network issue…

Daniel, if you have any idea im open minded!

Cheers!

On Thu, May 15, 2014 at 7:08 PM, Daniel DeLeo dan@kallistec.com wrote:

On Thursday, May 15, 2014 at 10:06 AM, Carlos Camacho wrote:

Daniel! Thanks for your answer,

The RST package it is being send from the chef server, but i don’t
know why, or the service which is failing.

Can you recommend me things to test?!?!

Thanks!

Is there a firewall on the server itself?


Daniel DeLeo


#14

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

So im a little bit blind here…

This is the chef-server-ctl tail output when chef-client it is executed…

==> /var/log/chef-server/nginx/access.log <==
mynode - - [16/May/2014:07:35:34 +0000] "GET /nodes/mynode HTTP/1.1"
200 “0.007” 15767 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.007” “11.12.4” “algorithm=sha1;version=1.0;” “mynode”
“2014-05-16T07:35:38Z” “2jmj7l5rSw0yVb/vlWAYkK/YBwk=” 999
mynode - - [16/May/2014:07:35:34 +0000] “POST
/reports/nodes/mynode/runs HTTP/1.1” 404 “0.044” 173 “-” “Chef
Client/11.12.4 (ruby-1.9.3-p484; ohai-7.0.4; i386-mingw32;
+http://opscode.com)” “127.0.0.1:8000” “404” “0.001” "11.12.4"
“algorithm=sha1;version=1.0;” “mynode” “2014-05-16T07:35:38Z”
“XemsHTvp8BHcocDMY1kiYRTf0dg=” 1214
mynode - - [16/May/2014:07:35:34 +0000] “POST
/environments/_default/cookbook_versions HTTP/1.1” 200 “0.056” 864 “-”
“Chef Client/11.12.4 (ruby-1.9.3-p484; ohai-7.0.4; i386-mingw32;
+http://opscode.com)” “127.0.0.1:8000” “200” “0.009” "11.12.4"
“algorithm=sha1;version=1.0;” “mynode” “2014-05-16T07:35:39Z”
“oxopNq5HHhVWRiVIxCseXf3iHmU=” 1107
mynode - - [16/May/2014:07:35:35 +0000] "PUT /nodes/mynode HTTP/1.1"
200 “0.067” 15758 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.041” “11.12.4” “algorithm=sha1;version=1.0;” “mynode”
“2014-05-16T07:35:39Z” “AI4nEjYvOw1tAkONEqnxBehhvu8=” 124188

==> /var/log/chef-server/chef-solr/current <==
2014-05-16_07:35:35.25015 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrDeletionPolicy onInit
2014-05-16_07:35:35.25018 INFO: SolrDeletionPolicy.onInit: commits:num=1
2014-05-16_07:35:35.25018
commit{dir=/var/opt/chef-server/chef-solr/data/index,segFN=segments_13,version=1399982839679,generation=39,filenames=[_9.tis,
_7_1.del, _8.tis, _v.fdx, _q.prx, _d.tii, _9.tii, _3.fdt, _c.tii,
_k.fnm, _7.fnm, _7.tis, _4.frq, _c.tis, _h.fdt, _10.tii, _y.nrm,
_h.fdx, _k_1.del, _d.tis, _w.fnm, _u.tii, _10.tis, _a.prx, _g.fdt,
_2.prx, _g.fdx, _u.tis, _5_2.del, _7.tii, _8.frq, _9.fdt, _2.frq,
_h.frq, _9.fdx, _1.fdx, _10.prx, _8.tii, _g.nrm, _1.fdt, _0.frq,
_6.fdt, _t.fdt, _a.fnm, _2.nrm, _0_4.del, _r.nrm, _y.tis, _6.fdx,
_u.fdx, _t.frq, _y.tii, _r_1.del, _6.tis, _x_1.del, _r.fdt, _m.tis,
_w_1.del, _r.fdx, _p.tii, _v.prx, _i.fdx, _m.tii, _y.fnm, _i.fdt,
_2_2.del, _g.prx, _x.fnm, _p.tis, _c_3.del, _z.prx, _i.frq, _10.frq,
_6.tii, _4.nrm, _l_1.del, _5.frq, _g.frq, _2.fnm, _3.fdx, _b.frq,
_x.prx, _a.nrm, _f.tis, _0.tis, _g.tis, _p.fdx, _5.prx, _p.fdt,
_m.prx, _4.prx, _c.fdx, _4.fdx, _c.fdt, _i.tis, _o.prx, _q_1.del,
_p.nrm, _5.nrm, _t_1.del, _g.tii, _7.frq, _i.tii, _s.nrm, _f.tii,
_m.fnm, _e.fnm, _o.fnm, _h.fnm, _j_1.del, _h.tis, _j.tis, _u.nrm,
_1_2.del, _0.tii, _h.tii, _j.tii, _u.fdt, _q.fnm, _6.nrm, _h_1.del,
_z.fdt, _x.nrm, _3.tii, _t.fnm, _z.fdx, _6.frq, _u.frq, _s.fnm,
_a.fdt, _b.nrm, _e.tis, _w.prx, _t.prx, _a.fdx, _s.tii, _e.tii,
_l.tis, _l.tii, _n.nrm, _10.fnm, _5.fnm, _n.prx, _b.prx, _x.frq,
_4.fdt, _b.tis, _b.tii, _8.prx, _s.tis, _f_1.del, _6.prx, _b.fnm,
_b.fdt, _8.fdx, _b.fdx, _8.fdt, _3.tis, _s.fdt, _z.frq, _1.frq,
_a.tii, _m.frq, _e.frq, _2.tii, _y.fdt, _v_2.del, _7.nrm, _y.fdx,
_n.frq, _e_1.del, _q.nrm, _c.nrm, _v.fnm, _g_1.del, _x.tis, _o.frq,
_a.tis, _l.nrm, _d.frq, _w.fdt, _9.prx, _l.prx, _w.fdx, _q.frq,
_c.prx, _2.fdt, _7.fdx, _x.tii, _6_1.del, _2.fdx, _z.nrm, _7.fdt,
_f.fdt, _2.tis, _f.fdx, _l.fdx, segments_13, _l.fdt, _c.frq, _j.fdx,
_x.fdt, _d_1.del, _j.fdt, _x.fdx, _k.prx, _l.frq, _3.fnm, _e.fdx,
_y_1.del, _p.frq, _v.tis, _n.tis, _r.fnm, _o_1.del, _u.fnm, _k.nrm,
_e.fdt, _j.nrm, _q.tis, _n.tii, _1.tii, _j.prx, _e.nrm, _o.fdt,
_q.tii, _1.tis, _o.fdx, _s_1.del, _n.fdt, _9.fnm, _3_2.del, _n.fdx,
_m.nrm, _y.prx, _v.nrm, _d.prx, _r.prx, _d.fdx, _8.nrm, _d.fdt,
_o.nrm, _m.fdt, _v.tii, _m.fdx, _d.nrm, _6.fnm, _c.fnm, _j.frq,
_f.frq, _p.prx, _h.prx, _5.fdt, _r.tii, _a_1.del, _q.fdx, _4.fnm,
_z.fnm, _q.fdt, _o.tis, _1.fnm, _h.nrm, _8_1.del, _k.tii, _v.frq,
_5.tis, _w.tii, _9_1.del, _t.tis, _4_1.del, _0.prx, _n_1.del, _n.fnm,
_k.tis, _w.tis, _3.nrm, _f.nrm, _w.frq, _0.fnm, _t.tii, _a.frq,
_s.prx, _d.fnm, _3.prx, _s.frq, _5.tii, _1.prx, _8.fnm, _f.prx,
_u.prx, _o.tii, _t.nrm, _e.prx, _r.tis, _1.nrm, _i.prx, _i.nrm,
_3.frq, _10.fdt, _z.tii, _u_1.del, _l.fnm, _p.fnm, _9.nrm, _k.fdt,
_y.frq, _z.tis, _k.fdx, _m_1.del, _p_1.del, _10.fdx, _g.fnm, _z_1.del,
_w.nrm, _r.frq, _4.tis, _0.nrm, _4.tii, _v.fdt, _9.frq, _7.prx,
_s.fdx, _f.fnm, _j.fnm, _t.fdx, _5.fdx, _0.fdx, _10.nrm, _k.frq,
_i.fnm, _0.fdt]
2014-05-16_07:35:35.25077 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrDeletionPolicy updateCommits
2014-05-16_07:35:35.25078 INFO: newest commit = 1399982839679
2014-05-16_07:35:35.26603 May 16, 2014 7:35:35 AM
org.apache.solr.update.processor.LogUpdateProcessor finish
2014-05-16_07:35:35.26606 INFO: {add=[0000000000007c1093a019810992da7a]} 0 31
2014-05-16_07:35:35.26648 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrCore execute
2014-05-16_07:35:35.26650 INFO: [] webapp=/solr path=/update params={}
status=0 QTime=31

==> /var/log/chef-server/chef-expander/current <==
2014-05-16_07:35:35.26821 [Fri, 16 May 2014 07:35:35 +0000] INFO:
indexed node[0000000000007c1093a019810992da7a]
database[chef_00000000000000000000000000000000] transit,xml,solr-post
| 0,0.10456681251525879,0.14017462730407715 |

==> /var/log/chef-server/erchef/erchef.log.1 <==
2014-05-16T07:35:34Z erchef@127.0.0.1 INFO
req_id=I1u0R4xTNbOQrNCbQ19eCg==; status=200; method=GET;
path=/nodes/mynode; user=mynode; msg=[]; req_time=5; rdbms_time=0;
rdbms_count=2
2014-05-16T07:35:34Z erchef@127.0.0.1 INFO
req_id=BUGbBDUTtkSFO5WwvomZGg==; status=200; method=POST;
path=/environments/_default/cookbook_versions; user=mynode; msg=[];
req_time=7; rdbms_time=2; rdbms_count=4
2014-05-16T07:35:35Z erchef@127.0.0.1 INFO
req_id=DiEmZOzphC/ivnnOmhpvwg==; status=200; method=PUT;
path=/nodes/mynode; user=mynode; msg=[]; req_time=39; rdbms_time=13;
rdbms_count=3

On Fri, May 16, 2014 at 8:58 AM, Carlos Camacho
carlos.camacho@frontiersin.org wrote:

Daniel, i have the default iptables rules from rackspace.

It is a very long list and i jut run this to clean it a little bit.

iptables --policy INPUT ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy FORWARD ACCEPT
iptables -F INPUT
iptables -F OUTPUT
iptables -F FORWARD
iptables -F RS-RackConnect-INBOUND
iptables -X RS-RackConnect-INBOUND

Now the output is this.

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Also in windows i disabled the windows firewall (It is important to
tell that this problem only happens with Windows nodes).

Now the chef-client output changed a little bit…

This is now…

[2014-05-16T06:53:30+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-16T06:53:30+00:00] INFO: Chef-client pid: 3924
[2014-05-16T06:53:37+00:00] INFO: Run List is [recipe[frontiers_test]]
[2014-05-16T06:53:37+00:00] INFO: Run List expands to [frontiers_test]
[2014-05-16T06:53:37+00:00] INFO: Starting Chef Run for slwnone09
[2014-05-16T06:53:37+00:00] INFO: Running start handlers
[2014-05-16T06:53:37+00:00] INFO: Start handlers complete.
[2014-05-16T06:53:37+00:00] INFO: HTTP Request Returned 404 Object Not Found:
resolving cookbooks for run list: [“frontiers_test”]
[2014-05-16T06:53:38+00:00] INFO: Loading cookbooks [cookbook_test@0.1.0]
Synchronizing Cookbooks:

  • cookbook_test
    Compiling Cookbooks…
    Converging 1 resources
    Recipe:cookbook_test::default
  • directory[C:\hello_test] action create[2014-05-16T06:53:38+00:00]
    INFO: Processing directory[C:\hello_test
    ] action create (cookbook_test::default line 10)
    (up to date)

Running handlers:
[2014-05-16T06:53:38+00:00] ERROR: Running exception handlers
Running handlers complete
[2014-05-16T06:53:38+00:00] ERROR: Exception handlers complete
[2014-05-16T06:53:38+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.324711 seconds
[2014-05-16T06:53:38+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And before the output was…

Starting Chef Client, version 11.12.4
[2014-05-14T14:02:26+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-14T14:02:26+00:00] INFO: Chef-client pid: 2936

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-14T14:02:34+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.154057 seconds
[2014-05-14T14:02:34+00:00] FATAL: EOFError: end of file reached

So, it is really annoying not to have any help from rackspace, they
only tells me, it is a server problem, not network issue…

Daniel, if you have any idea im open minded!

Cheers!

On Thu, May 15, 2014 at 7:08 PM, Daniel DeLeo dan@kallistec.com wrote:

On Thursday, May 15, 2014 at 10:06 AM, Carlos Camacho wrote:

Daniel! Thanks for your answer,

The RST package it is being send from the chef server, but i don’t
know why, or the service which is failing.

Can you recommend me things to test?!?!

Thanks!

Is there a firewall on the server itself?


Daniel DeLeo


#15

Is there anything in the kernel messages (dmesg, /var/log/messages,
etc.) of the Chef server? Could it be that the kernel is sending the
TCP RST for some reason?

Windows nodes often send a LOT of data, so maybe that has something to
do with it…

  • Julian

On Fri, May 16, 2014 at 2:38 AM, Carlos Camacho
carlos.camacho@frontiersin.org 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

So im a little bit blind here…

This is the chef-server-ctl tail output when chef-client it is executed…

==> /var/log/chef-server/nginx/access.log <==
mynode - - [16/May/2014:07:35:34 +0000] "GET /nodes/mynode HTTP/1.1"
200 “0.007” 15767 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.007” “11.12.4” “algorithm=sha1;version=1.0;” “mynode”
“2014-05-16T07:35:38Z” “2jmj7l5rSw0yVb/vlWAYkK/YBwk=” 999
mynode - - [16/May/2014:07:35:34 +0000] “POST
/reports/nodes/mynode/runs HTTP/1.1” 404 “0.044” 173 “-” “Chef
Client/11.12.4 (ruby-1.9.3-p484; ohai-7.0.4; i386-mingw32;
+http://opscode.com)” “127.0.0.1:8000” “404” “0.001” "11.12.4"
“algorithm=sha1;version=1.0;” “mynode” “2014-05-16T07:35:38Z”
“XemsHTvp8BHcocDMY1kiYRTf0dg=” 1214
mynode - - [16/May/2014:07:35:34 +0000] “POST
/environments/_default/cookbook_versions HTTP/1.1” 200 “0.056” 864 “-”
“Chef Client/11.12.4 (ruby-1.9.3-p484; ohai-7.0.4; i386-mingw32;
+http://opscode.com)” “127.0.0.1:8000” “200” “0.009” "11.12.4"
“algorithm=sha1;version=1.0;” “mynode” “2014-05-16T07:35:39Z”
“oxopNq5HHhVWRiVIxCseXf3iHmU=” 1107
mynode - - [16/May/2014:07:35:35 +0000] "PUT /nodes/mynode HTTP/1.1"
200 “0.067” 15758 “-” “Chef Client/11.12.4 (ruby-1.9.3-p484;
ohai-7.0.4; i386-mingw32; +http://opscode.com)” “127.0.0.1:8000” "200"
“0.041” “11.12.4” “algorithm=sha1;version=1.0;” “mynode”
“2014-05-16T07:35:39Z” “AI4nEjYvOw1tAkONEqnxBehhvu8=” 124188

==> /var/log/chef-server/chef-solr/current <==
2014-05-16_07:35:35.25015 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrDeletionPolicy onInit
2014-05-16_07:35:35.25018 INFO: SolrDeletionPolicy.onInit: commits:num=1
2014-05-16_07:35:35.25018
commit{dir=/var/opt/chef-server/chef-solr/data/index,segFN=segments_13,version=1399982839679,generation=39,filenames=[_9.tis,
_7_1.del, _8.tis, _v.fdx, _q.prx, _d.tii, _9.tii, _3.fdt, _c.tii,
_k.fnm, _7.fnm, _7.tis, _4.frq, _c.tis, _h.fdt, _10.tii, _y.nrm,
_h.fdx, _k_1.del, _d.tis, _w.fnm, _u.tii, _10.tis, _a.prx, _g.fdt,
_2.prx, _g.fdx, _u.tis, _5_2.del, _7.tii, _8.frq, _9.fdt, _2.frq,
_h.frq, _9.fdx, _1.fdx, _10.prx, _8.tii, _g.nrm, _1.fdt, _0.frq,
_6.fdt, _t.fdt, _a.fnm, _2.nrm, _0_4.del, _r.nrm, _y.tis, _6.fdx,
_u.fdx, _t.frq, _y.tii, _r_1.del, _6.tis, _x_1.del, _r.fdt, _m.tis,
_w_1.del, _r.fdx, _p.tii, _v.prx, _i.fdx, _m.tii, _y.fnm, _i.fdt,
_2_2.del, _g.prx, _x.fnm, _p.tis, _c_3.del, _z.prx, _i.frq, _10.frq,
_6.tii, _4.nrm, _l_1.del, _5.frq, _g.frq, _2.fnm, _3.fdx, _b.frq,
_x.prx, _a.nrm, _f.tis, _0.tis, _g.tis, _p.fdx, _5.prx, _p.fdt,
_m.prx, _4.prx, _c.fdx, _4.fdx, _c.fdt, _i.tis, _o.prx, _q_1.del,
_p.nrm, _5.nrm, _t_1.del, _g.tii, _7.frq, _i.tii, _s.nrm, _f.tii,
_m.fnm, _e.fnm, _o.fnm, _h.fnm, _j_1.del, _h.tis, _j.tis, _u.nrm,
_1_2.del, _0.tii, _h.tii, _j.tii, _u.fdt, _q.fnm, _6.nrm, _h_1.del,
_z.fdt, _x.nrm, _3.tii, _t.fnm, _z.fdx, _6.frq, _u.frq, _s.fnm,
_a.fdt, _b.nrm, _e.tis, _w.prx, _t.prx, _a.fdx, _s.tii, _e.tii,
_l.tis, _l.tii, _n.nrm, _10.fnm, _5.fnm, _n.prx, _b.prx, _x.frq,
_4.fdt, _b.tis, _b.tii, _8.prx, _s.tis, _f_1.del, _6.prx, _b.fnm,
_b.fdt, _8.fdx, _b.fdx, _8.fdt, _3.tis, _s.fdt, _z.frq, _1.frq,
_a.tii, _m.frq, _e.frq, _2.tii, _y.fdt, _v_2.del, _7.nrm, _y.fdx,
_n.frq, _e_1.del, _q.nrm, _c.nrm, _v.fnm, _g_1.del, _x.tis, _o.frq,
_a.tis, _l.nrm, _d.frq, _w.fdt, _9.prx, _l.prx, _w.fdx, _q.frq,
_c.prx, _2.fdt, _7.fdx, _x.tii, _6_1.del, _2.fdx, _z.nrm, _7.fdt,
_f.fdt, _2.tis, _f.fdx, _l.fdx, segments_13, _l.fdt, _c.frq, _j.fdx,
_x.fdt, _d_1.del, _j.fdt, _x.fdx, _k.prx, _l.frq, _3.fnm, _e.fdx,
_y_1.del, _p.frq, _v.tis, _n.tis, _r.fnm, _o_1.del, _u.fnm, _k.nrm,
_e.fdt, _j.nrm, _q.tis, _n.tii, _1.tii, _j.prx, _e.nrm, _o.fdt,
_q.tii, _1.tis, _o.fdx, _s_1.del, _n.fdt, _9.fnm, _3_2.del, _n.fdx,
_m.nrm, _y.prx, _v.nrm, _d.prx, _r.prx, _d.fdx, _8.nrm, _d.fdt,
_o.nrm, _m.fdt, _v.tii, _m.fdx, _d.nrm, _6.fnm, _c.fnm, _j.frq,
_f.frq, _p.prx, _h.prx, _5.fdt, _r.tii, _a_1.del, _q.fdx, _4.fnm,
_z.fnm, _q.fdt, _o.tis, _1.fnm, _h.nrm, _8_1.del, _k.tii, _v.frq,
_5.tis, _w.tii, _9_1.del, _t.tis, _4_1.del, _0.prx, _n_1.del, _n.fnm,
_k.tis, _w.tis, _3.nrm, _f.nrm, _w.frq, _0.fnm, _t.tii, _a.frq,
_s.prx, _d.fnm, _3.prx, _s.frq, _5.tii, _1.prx, _8.fnm, _f.prx,
_u.prx, _o.tii, _t.nrm, _e.prx, _r.tis, _1.nrm, _i.prx, _i.nrm,
_3.frq, _10.fdt, _z.tii, _u_1.del, _l.fnm, _p.fnm, _9.nrm, _k.fdt,
_y.frq, _z.tis, _k.fdx, _m_1.del, _p_1.del, _10.fdx, _g.fnm, _z_1.del,
_w.nrm, _r.frq, _4.tis, _0.nrm, _4.tii, _v.fdt, _9.frq, _7.prx,
_s.fdx, _f.fnm, _j.fnm, _t.fdx, _5.fdx, _0.fdx, _10.nrm, _k.frq,
_i.fnm, _0.fdt]
2014-05-16_07:35:35.25077 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrDeletionPolicy updateCommits
2014-05-16_07:35:35.25078 INFO: newest commit = 1399982839679
2014-05-16_07:35:35.26603 May 16, 2014 7:35:35 AM
org.apache.solr.update.processor.LogUpdateProcessor finish
2014-05-16_07:35:35.26606 INFO: {add=[0000000000007c1093a019810992da7a]} 0 31
2014-05-16_07:35:35.26648 May 16, 2014 7:35:35 AM
org.apache.solr.core.SolrCore execute
2014-05-16_07:35:35.26650 INFO: [] webapp=/solr path=/update params={}
status=0 QTime=31

==> /var/log/chef-server/chef-expander/current <==
2014-05-16_07:35:35.26821 [Fri, 16 May 2014 07:35:35 +0000] INFO:
indexed node[0000000000007c1093a019810992da7a]
database[chef_00000000000000000000000000000000] transit,xml,solr-post
| 0,0.10456681251525879,0.14017462730407715 |

==> /var/log/chef-server/erchef/erchef.log.1 <==
2014-05-16T07:35:34Z erchef@127.0.0.1 INFO
req_id=I1u0R4xTNbOQrNCbQ19eCg==; status=200; method=GET;
path=/nodes/mynode; user=mynode; msg=[]; req_time=5; rdbms_time=0;
rdbms_count=2
2014-05-16T07:35:34Z erchef@127.0.0.1 INFO
req_id=BUGbBDUTtkSFO5WwvomZGg==; status=200; method=POST;
path=/environments/_default/cookbook_versions; user=mynode; msg=[];
req_time=7; rdbms_time=2; rdbms_count=4
2014-05-16T07:35:35Z erchef@127.0.0.1 INFO
req_id=DiEmZOzphC/ivnnOmhpvwg==; status=200; method=PUT;
path=/nodes/mynode; user=mynode; msg=[]; req_time=39; rdbms_time=13;
rdbms_count=3

On Fri, May 16, 2014 at 8:58 AM, Carlos Camacho
carlos.camacho@frontiersin.org wrote:

Daniel, i have the default iptables rules from rackspace.

It is a very long list and i jut run this to clean it a little bit.

iptables --policy INPUT ACCEPT
iptables --policy OUTPUT ACCEPT
iptables --policy FORWARD ACCEPT
iptables -F INPUT
iptables -F OUTPUT
iptables -F FORWARD
iptables -F RS-RackConnect-INBOUND
iptables -X RS-RackConnect-INBOUND

Now the output is this.

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Also in windows i disabled the windows firewall (It is important to
tell that this problem only happens with Windows nodes).

Now the chef-client output changed a little bit…

This is now…

[2014-05-16T06:53:30+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-16T06:53:30+00:00] INFO: Chef-client pid: 3924
[2014-05-16T06:53:37+00:00] INFO: Run List is [recipe[frontiers_test]]
[2014-05-16T06:53:37+00:00] INFO: Run List expands to [frontiers_test]
[2014-05-16T06:53:37+00:00] INFO: Starting Chef Run for slwnone09
[2014-05-16T06:53:37+00:00] INFO: Running start handlers
[2014-05-16T06:53:37+00:00] INFO: Start handlers complete.
[2014-05-16T06:53:37+00:00] INFO: HTTP Request Returned 404 Object Not Found:
resolving cookbooks for run list: [“frontiers_test”]
[2014-05-16T06:53:38+00:00] INFO: Loading cookbooks [cookbook_test@0.1.0]
Synchronizing Cookbooks:

  • cookbook_test
    Compiling Cookbooks…
    Converging 1 resources
    Recipe:cookbook_test::default
  • directory[C:\hello_test] action create[2014-05-16T06:53:38+00:00]
    INFO: Processing directory[C:\hello_test
    ] action create (cookbook_test::default line 10)
    (up to date)

Running handlers:
[2014-05-16T06:53:38+00:00] ERROR: Running exception handlers
Running handlers complete
[2014-05-16T06:53:38+00:00] ERROR: Exception handlers complete
[2014-05-16T06:53:38+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.324711 seconds
[2014-05-16T06:53:38+00:00] FATAL: EOFError: end of file reached
PS C:\Users\Administrator>

And before the output was…

Starting Chef Client, version 11.12.4
[2014-05-14T14:02:26+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-14T14:02:26+00:00] INFO: Chef-client pid: 2936

================================================================================
Chef encountered an error attempting to load the node data for “mynode”

Unexpected Error:

EOFError: end of file reached

[2014-05-14T14:02:34+00:00] FATAL: Stacktrace dumped to
c:/chef/cache/chef-stacktrace.out
Chef Client failed. 0 resources updated in 10.154057 seconds
[2014-05-14T14:02:34+00:00] FATAL: EOFError: end of file reached

So, it is really annoying not to have any help from rackspace, they
only tells me, it is a server problem, not network issue…

Daniel, if you have any idea im open minded!

Cheers!

On Thu, May 15, 2014 at 7:08 PM, Daniel DeLeo dan@kallistec.com wrote:

On Thursday, May 15, 2014 at 10:06 AM, Carlos Camacho wrote:

Daniel! Thanks for your answer,

The RST package it is being send from the chef server, but i don’t
know why, or the service which is failing.

Can you recommend me things to test?!?!

Thanks!

Is there a firewall on the server itself?


Daniel DeLeo


[ Julian C. Dunn jdunn@aquezada.com * Sorry, I’m ]
[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]
[ gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]


#16

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.


#17

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… :slight_smile:

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 lamont@opscode.com 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.


#18

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
carlos.camacho@frontiersin.org 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… :slight_smile:

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 lamont@opscode.com 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.


#19

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:carlos.camacho@frontiersin.org]
Sent: Monday, May 19, 2014 2:10 AM
To: chef@lists.opscode.com
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
carlos.camacho@frontiersin.org 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… :slight_smile:

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 lamont@opscode.com
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.


#20

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.