Laravel wagrant up not working - Errno :: EADDRNOTAVAIL

Laravel 환경 또는 Windows 10의 일부가 업데이트되는 동안 최근에 일부 오류가 발생했습니다. 많은 시행 착오 끝에 모든 것을 삭제하고 처음부터 다시 시작하기로 결정했습니다. . 이제는 새로운 VirtualBox, 방랑자, Laravel/Homestead 상자 및 Homestead 자체가 있습니다. 다음 아래에 약 100 개 라인으로Laravel wagrant up not working - Errno :: EADDRNOTAVAIL

$ 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에 대해 뭔가 읽었지만 해결할 수 없었습니다.

새로운 방랑 1.9.3에 문제가 될 것으로 보인다

출처

2017-03-22 Norgul

호스트 파일을 업데이트 했습니까? 또한 '0.0.0.0'의 IP는 작동하지 않는다고 생각하지만 사실 기반의 진술보다 메모리가 더 많습니다 – Loek

무엇으로 업데이트 되었습니까? 모든 것을 다시 설치하기 전에 그대로 두었습니다. – Norgul

방글라데시는 할당 된 IP ('0.0.0.0')를 사용할 수 없다고 불평하고 있습니다. Homestead.yaml을 '192.168.10.10'과 같은 다른 IP로 바꾸고 호스트 파일을 업데이트하여 해당 IP 주소를 반영하십시오. – Loek

파일을 편집 할 수 있습니다, 일부는 농가에 대한

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'

을 다음과 같이 fix 할 수 있었다

(https://github.com/mitchellh/vagrant/issues/8395 참조) 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

출처

2017-03-22 17:17:44

Oh man ... 나는 당신에게 금메달을주고 당신에게 트럭 트럭을 실어 줄 것이다. 방랑자를 1.9.0으로 격하 시켰습니다. 3 일 동안 계속되고 있던 모든 문제는 사라졌습니다. 고마워요 – Norgul

맥주를 가져 가겠습니다. 고마워요. –

1.9.3에서 1.9.0으로 내려가는 이중 확인은 나에게도 이것을 해결했습니다. https://releases.hashicorp.com/vagrant/1.9.0/ ('.msi'를 원함) – MECU

Laravel wagrant up not working - Errno :: EADDRNOTAVAIL

답변

관련 문제