2017-03-22 8 views
17

Laravel環境やWindows 10の一部が更新されているうちに、私は最近いくつかのエラーがあったので、試行錯誤を繰り返した結果、すべてを削除してから始めます。 。今は新しいVirtualBox、Vagrant、Laravel/Homesteadボックス、Homestead自体があります。Laravelの不具合がうまくいかない - Errno :: EADDRNOTAVAIL

しかし、私はこのエラーを取得する実行します。以下より約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について何かを読んでいましたが、私はそれを解決することはできませんでした。

新しい放浪1.9.3の問題のように見える
+0

ホストファイルを更新しましたか?また、私は '0.0.0.0'のIPは動作しないと思いますが、それは事実に基づくステートメントよりもメモリです – Loek

+0

何に更新されましたか?私はすべてを再インストールする前の状態にしておきました。 – Norgul

+0

代理人は割り当てられたIP( '0.0.0.0')が利用できないと訴えています。 Homestead.yamlを '192.168.10.10'のような別のIPに変更し、そのIPアドレスを反映するようにhostsファイルを更新してみてください。 – Loek

答えて

28

ファイルを編集することができ、いくつかは、ホームステッドのために

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 
+0

ああ男...私はあなたに金メダルを与え、あなたにビールのトラックの負荷を購入します。私はVagrantを1.9.0に格下げしました。 3日間続いたすべての問題はなくなりました。ありがとうございます – Norgul

+3

ありがとう私はビールを取るでしょう:) –

+0

ダブルは1.9.3から1.9.0へのダウングレードも私のためにこれを解決しました。 https://releases.hashicorp.com/vagrant/1.9.0/( '.msi'が必要です) – MECU

関連する問題