Is Chef-client server down?


#1

Hi,

I’ve been having problems trying to bootstrap chef-client most of today.

Earlier it was just timing out, but now I’m seeing this when I try to do a previously-working bootstrap:

192.168.0.102 C:\Users\Administrator>SET "PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System
32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
192.168.0.102
192.168.0.102 C:\Users\Administrator>chef-client -c c:/chef/client.rb -j c:/chef/first-boot.json -E _default
DEBUG: :relay_error_from_backend => [“192.168.0.102”, “‘chef-client’ is not recognized as an internal or external comman
d,\r\noperable program or batch file.\r\n”]
192.168.0.102 ‘chef-client’ is not recognized as an internal or external command,

When I try to point a browser to the URL that is used for the msi client download, I can connect, but get like 0 bytes/sec.

I posted about this on stackoverflow but no responses there, so I’ve subscribed here.

Is something going wrong?

Also, now that this is happening, can I somehow point knife on my Workstation to a local copy of the .msi in cases like that?

Thanks,
Jim


#2

Jim,

Not sure if there was an issue with getting the installer a few days ago,
but I haven’t had any issues today.

Regarding how to prevent this in the future; you can use custom bootstrap
templates to change the location that the bootstrap pulls the chef-client
from: https://docs.chef.io/knife_bootstrap.html#custom-templates

On Thu, Jun 11, 2015 at 6:25 PM, o haya ohaya@yahoo.com wrote:

Hi,

I’ve been having problems trying to bootstrap chef-client most of today.

Earlier it was just timing out, but now I’m seeing this when I try to do a
previously-working bootstrap:

192.168.0.102 C:\Users\Administrator>SET
"PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System

32\WindowsPowerShell\v1.0;C:\ruby\bin;C:\opscode\chef\bin;C:\opscode\chef\embedded\bin"
192.168.0.102
192.168.0.102 C:\Users\Administrator>chef-client -c c:/chef/client.rb -j
c:/chef/first-boot.json -E _default
DEBUG: :relay_error_from_backend => [“192.168.0.102”, “‘chef-client’ is
not recognized as an internal or external comman
d,\r\noperable program or batch file.\r\n”]
192.168.0.102 ‘chef-client’ is not recognized as an internal or external
command,

When I try to point a browser to the URL that is used for the msi client
download, I can connect, but get like 0 bytes/sec.

I posted about this on stackoverflow but no responses there, so I’ve
subscribed here.

Is something going wrong?

Also, now that this is happening, can I somehow point knife on my
Workstation to a local copy of the .msi in cases like that?

Thanks,
Jim


Galen