2017-03-22 12 views
17

मुझे हाल ही में कुछ त्रुटियां हुई हैं जबकि लैरवेल पर्यावरण या विंडोज 10 का एक हिस्सा अपडेट किया गया है, इसलिए कई परीक्षणों और त्रुटियों के बाद मैंने सबकुछ हटाने और खरोंच से शुरू करने का फैसला किया है । तो अब मेरे पास नया वर्चुअलबॉक्स, वाग्रेंट, लैरावेल/होमस्टेड बॉक्स और होमस्टेड है। निम्नलिखित नीचे के बारे में 100 से लाइनों के साथलैरवेल योनि काम नहीं कर रहा है - एरर्नो :: ईएडीडीआरएनओटीएवल

$ vagrant up 
Bringing machine 'homestead-7' up with 'virtualbox' provider... 
==> homestead-7: Importing base box 'laravel/homestead'... 
==> homestead-7: Matching MAC address for NAT networking... 
==> homestead-7: Checking if box 'laravel/homestead' is up to date... 
==> homestead-7: Setting the name of the VM: homestead-7 
==> homestead-7: Destroying VM and associated drives... 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `initialize': The requested address is not valid in its context. - connect(2) for "0.0.0.0" port 8000 (Errno::EADDRNOTAVAIL) 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `new' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:21:in `block in is_port_open?' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch' 
     from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/util/is_port_open.rb:19:in `is_port_open?' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:248:in `port_check' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:121:in `[]' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:121:in `block in handle' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:257:in `block in with_forwarded_ports' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:253:in `each' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:253:in `with_forwarded_ports' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:98:in `handle' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:42:in `block in call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/environment.rb:567:in `lock' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:41:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/env_set.rb:19:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builtin/provision.rb:80:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/set_name.rb:50:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/warden.rb:34:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/builder.rb:116:in `call' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/action/runner.rb:66:in `block in run' 
     from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.3/lib/vagrant/unil/busy.rb:19:in `busy' 

:

हालांकि, मैं इस त्रुटि मिलती है। क्या आपको पता है कि समस्या क्या है और इसे कैसे हल किया जाए? मैं RoR के बारे में कुछ पढ़ रहा था, लेकिन मैंने इसे हल करने का प्रबंधन नहीं किया।

+0

क्या आपने अपनी मेजबान फ़ाइल अपडेट की है? साथ ही, मुझे नहीं लगता कि '0.0.0.0' का आईपी काम करता है, लेकिन यह तथ्य आधारित आधार – Loek

+0

से अधिक स्मृति है जो अद्यतन किया गया है? मैंने इसे छोड़ दिया है क्योंकि इससे पहले कि मैं सब कुछ पुनर्स्थापित कर दूं – Norgul

+0

वग्रेंट शिकायत कर रहा है कि आपका असाइन किया गया आईपी ('0.0.0.0') अनुपलब्ध है। अपने Homestead.yaml को किसी अन्य आईपी में '192.168.10.10' जैसे बदलने का प्रयास करें और आईपी – Loek

उत्तर

28

यह नया आवारा 1.9.3 के साथ कोई समस्या प्रतीत होता है (https://github.com/mitchellh/vagrant/issues/8395 देखें)

कुछ

I managed to make the 1.9.3 version working by rewritten all my Vagrantfile(s) and adding the host_ip: "127.0.0.1" parameter for each of the "forwarded_port" network configuration.

E.g.: config.vm.network "forwarded_port", guest: 22, host: 1022, host_ip: "127.0.0.1", id: 'ssh'

Homestead के लिए निम्नलिखित के साथ fix करने में सक्षम थे, आप फ़ाइल को संपादित कर सकते हैं Homestead/scripts/homestead.rb

# Use Default Port Forwarding Unless Overridden 
    unless settings.has_key?("default_ports") && settings["default_ports"] == false 
     default_ports.each do |guest, host| 
      unless settings["ports"].any? { |mapping| mapping["guest"] == guest } 
       config.vm.network "forwarded_port", guest: guest, host: host, host_ip: "127.0.0.1", auto_correct: true 
      end 
     end 
    end 

    # Add Custom Ports From Configuration 
    if settings.has_key?("ports") 
     settings["ports"].each do |port| 
      config.vm.network "forwarded_port", guest: port["guest"], host: port["host"], protocol: port["protocol"], host_ip: "127.0.0.1", auto_correct: true 
     end 
    end 
+0

ओह आदमी ... मैं आपको एक स्वर्ण पदक दूंगा और आपको एक ट्रक लोड बियर खरीदूंगा। मैंने वग्रेंट को 1.9.0 तक घटा दिया है। और 3 दिनों के लिए चल रहे सभी मुद्दे चले गए हैं। धन्यवाद – Norgul

+3

धन्यवाद मैं बीयर ले जाऊंगा :) –

+0

1.9.3 से 1.9.0 तक डाउनग्रेड करने की डबल पुष्टि मेरे लिए भी हल हो गई। https://releases.hashicorp.com/vagrant/1.9.0/ (आप '.msi' चाहते हैं) – MECU

संबंधित मुद्दे