I feel like I’m missing something….but, I’m not seeing a “Windows Service” wrapper for chef-client anywhere…

Does this exist? How else can we force chef-client to check-in periodically on Windows?

Hi
I’m following the opscode tutorial to learn chef, and trying to bootstrap a node with the following command:
knife bootstrap localhost —ssh-user vagrant -ssh-password -ssh-port 2222 —run-list “recipe[apt],recipe[aliases],recipe[apache2],recipe[networking_basic]” —sudo but get this networking error ERROR: Network Error: No connection could be made because the target machine actively refused it. – connect(2) check your knife configuration and network settings

Can anyone help? Thanks

Last night I found that a Chef run failed because Hosted Chef responded with a 403 when Chef was attempting to run a cookbook_file resource. Here’s the stack trace:

[ec2-user@ip-10-83-22-235 ~]$ cat /var/chef/cache/chef-stacktrace.out Generated at Wed Apr 04 00:34:41 +0000 2012 Net::HTTPServerException: cookbook_file[/etc/init.d/product] (Product::default line 210) had an error: Net::HTTPServerException: 403 "Forbidden" /usr/lib/ruby/1.8/net/http.rb:2105:in `error!' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/rest.rb:281:in `streaming_request' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/rest.rb:296:in `retriable_rest_request' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/rest.rb:259:in `streaming_request' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/rest.rb:112:in `get_rest' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/cookbook/remote_file_vendor.rb:63:in `get_filename' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/cookbook_version.rb:659:in `preferred_filename_on_disk_location' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/provider/cookbook_file.rb:64:in `file_cache_location' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/provider/cookbook_file.rb:36:in `action_create' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource.rb:440:in `send' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource.rb:440:in `run_action' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/runner.rb:45:in `run_action' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/runner.rb:81:in `converge' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/runner.rb:81:in `each' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/runner.rb:81:in `converge' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection.rb:94:in `execute_each_resource' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection/stepable_iterator.rb:116:in `call_iterator_block' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection/stepable_iterator.rb:85:in `step' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection/stepable_iterator.rb:104:in `iterate' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection/stepable_iterator.rb:55:in `each_with_index' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/resource_collection.rb:92:in `execute_each_resource' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/runner.rb:76:in `converge' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/client.rb:312:in `converge' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/client.rb:160:in `run' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/application/client.rb:239:in `run_application' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/application/client.rb:229:in `loop' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/application/client.rb:229:in `run_application' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/../lib/chef/application.rb:67:in `run' /usr/lib64/ruby/gems/1.8/gems/chef-0.10.8/bin/chef-client:26 /usr/bin/chef-client:19:in `load'

This happened on two nodes. Today, executing a Chef run on the same nodes with no changes to cookbooks does not produce that error. What gives?

I have a node which is registered to chef server when its first time run the chef-client, so I can see the node in the web interface.

But I can’t run knife ssh to it, return error

“Net::SSH::AuthenticationFailed”

So, in this case, what is the best way to copy the ssh key?

I need to mount a network drive on a windows vm. I am currently using chef solo to automate the process.

This is what I have in my recipe file:

mount "W:" do
  action :mount
  device "\\\\blazer\\INTAPPS"
end

This does not work and I get the following error messages:

Unable to detect IP6Address ...
chef-client does not have administrator priviledges on node BESTVM.ms.otpp.net. This might cause unexpected resource failures....

I can manually map the drive on the windows vm, but then I need to provide a domain-name-qualified user name and password. Is there a way I can provide the domain name, user name, password to the mount resource? is there an alternate way to mount the drive using chef?

I also tried the following command (as suggested in http://docs.opscode.com/ctl_chef_client.html)

runas /user:my_user_name "cmd /C chef-client"

After I entered password, a window appears and then dissapears. So I don’t exactly know what is happenning in it.

I am an absolute new by to chef, so a detailed answer would be very much appreciated.

Thanks.

Hi,

I have recently tried to use the IIS cookbook (link text) on a new Windows 2008 R2 install.

I have Chef-client installed and setup, I have the PEM’s in place, and the listed cookbook dependencies are available on my Chef server.

I add the getting-started recipe and the iis recipe to the run list of the node, and then on the node I ran the chef-client.

The first run, the getting started recipe did what it needed and worked fine, then I got an error about rubyzip not being installed and it failed. I thought that is an easy fix, so i ran “gem install rubyzip” manually and that succeeded.

I then ran the chef-client again, and i get the following error:

---- Begin output of C:\webpi\WebpiCmdLine.exe /products:IIS7 /suppressreboot /accepteula ----
STDOUT:
STDERR: The system cannot find the path specified.
---- End output of C:\webpi\WebpiCmdLine.exe /products:IIS7 /suppressreboot /accepteula ----

I gather that from the error message, i am missing the webpi application, however, I have the webpi Cookbook.

I was under the impression that I would be able to run chef-client and it would install all the required parts of the IIS as long as I had the cookbooks for it.

Am I under the wrong impression, and I actually need to install some supporting applications first, or is this some other error because I am missing a cookbook or some other configuration?

Thanks

Allan