Running into an error that I cannot resolve . . . Any ideas would be 
appreciated as I am running out of ideas on this one . . .

I'm running hosted Chef and running into the following after I run "vagrant 
up"

*/Users/xxxxxxxxx/.vagrant.d/gems/gems/vagrant-chef-zero-2.0.0/lib/vagrant-chef-zero/server_helpers.rb:102:in
 
`initialize': getaddrinfo: nodename nor servname provided, or not known 
(SocketError)*


My Vagrant file looks like this:









*Vagrant.configure("2") do |config|  config.vm.box = "ubuntu-14.04"  
config.omnibus.chef_version = :latest  config.vm.provision :chef_client do 
|chef|    chef.provisioning_path = "/etc/chef"    chef.node_name = 
"server"    chef.chef_server_url = 
"https://api.chef.io/organizations/myorg:443";    chef.validation_key_path = 
".chef/*
*myorg-validator.pem"    chef.validation_client_name = "*

*myorg-validator"  endend*

I found that the following line is the which is causing the problem:
*chef.chef_server_url = "https://api.chef.io/organizations/**myorg:443"*  

I had to add the port number to this string in order to get past this 
error:  `initialize': service name too long (33) (ArgumentError)

$ *vagrant plugin list*
vagrant-berkshelf (4.1.0)
vagrant-chef-zero (2.0.0)
vagrant-omnibus (1.4.1)
vagrant-share (1.1.5, system)


*$ vagrant --version*
Vagrant 1.8.5



-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/be4823c9-4201-4dd2-ab78-5e83341491c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to