Bootstrapping Chef to Windows Node failing -
i new chef , have chef server installed , chef dk installed on 1 windows 2008 r2 machine (the workstation), , trying bootstrap 2nd windows 2008 r2 machine workstation using:
knife bootstrap windows winrm ip_of_node -x administrator -p password --node-name node1 -v -v
and failing. have debug enabled , repeats following bunch of times before failing:
..debug: adding 192.168.0.101 debug: :session => :init debug: :relay_to_servers => echo . & echo response received. debug: :relayed => 192.168.0.101 debug: 192.168.0.101 => :run_command ..debug: adding 192.168.0.101 debug: :session => :init debug: :relay_to_servers => echo . & echo response received. debug: :relayed => 192.168.0.101 debug: 192.168.0.101 => :run_command ..debug: adding 192.168.0.101 debug: :session => :init debug: :relay_to_servers => echo . & echo response received. debug: :relayed => 192.168.0.101 debug: 192.168.0.101 => :run_command error: no response received remote node after 1.97 minutes, giving up. error: runtimeerror: command execution failed. ps c:\users\administrator\chef-repo>
i can telnet workstation node machine's port 5985 successfully.
what else might causing bootstrap fail?
thanks, jim
edit: btw, when netstat on node, listening on port 5985, i've seen references should listening on both 5985 , 5986? why failing (listening on 1 of ports)? if so, why not listening on both ports?
re. not being able run "winrm set" commands: found if go command prompt typing "cmd" while in powershell, run "winrm set" commands.
once able run "winrm set" commands ran following:
winrm set winrm/config '@{maxtimeoutms="1800000"}' winrm set winrm/config/service '@{allowunencrypted="true"}' winrm set winrm/config/service/auth '@{basic="true"}'
after that, "knife" worked , able bootstrap windows 2008 r2 node.
jim
Comments
Post a Comment