włóczęga up - ERRNO :: EADDRNOTAVAIL wersji Vagrant 1.9.3

I zostały próbuje zainstalować laravel Homestead i śledzę różne tutoriale, ale zawsze kiedy dotrzeć do punktu, gdzie mam wykonać vagrant up I recive ten błąd:włóczęga up - ERRNO :: EADDRNOTAVAIL wersji Vagrant 1.9.3

$ 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': La direcci▒n solicitada no es v▒lida en este contexto. - 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'

Część, która mówi: La direcci▒n solicitada no es v▒lida en este contexto oznacza the requested address is not valid in this context w języku hiszpańskim. Rzeczy are to tylko samogłoski ó i á.

To mój Homestead.yaml file:

--- 
ip: "192.168.10.10" 
memory: 2048 
cpus: 1 
provider: virtualbox 

authorize: ~/.ssh/id_rsa.pub 

keys: 
    - ~/.ssh/id_rsa 

folders: 
    - map: C:\laravel-projects 
     to: /home/vagrant/Code 

sites: 
    - map: erpsoftware.app 
     to: /home/vagrant/Code/erpsoftware/public 

databases: 
    - homestead 

# blackfire: 
#  - id: foo 
#  token: bar 
#  client-id: foo 
#  client-token: bar 

# ports: 
#  - send: 50000 
#  to: 5000 
#  - send: 7777 
#  to: 777 
#  protocol: udp

Katalog C:\laravel-projects istnieć, ja już dodane 192.168.10.10 erpsoftware.app w pliku C:\Windows\System32\drivers\etc\hosts i pobiegł ssh-keygen -t rsa -b 4096 -C "[email protected]" (oczywiście, zastępując '[email protected]' z mojego aktualnego adresu e-mail).

Czy brakuje mi czegoś?

Źródło

2017-03-22 thingNumber2

Możliwy duplikat [Laravel vagrant up not working] (http://stackoverflow.com/questions/42955086/laravel-vagrant-up-work-working) –

Za duplikat, obniżenie poziomu Vagrant z 1.9.3 do 1.9. 0 rozwiązało to dla mnie. – MECU

mam wiele problemów z wersją 1.9.3 Co Vagrant Zrobiłem to ponownie w wersji 1.9.2 to wszystko działało dobrze.

Źródło

2017-03-24 02:29:38 Envil

Staje się to dziś dla mnie rutyną. Zaktualizuj Vagrant, przełamuj wszystko. Cofnij. Powtórz. –

To zadziałało dla mnie :) – William

Twoja konfiguracja jest najprawdopodobniej w porządku. Wypróbowałbym te trzy rzeczy.

Najpierw zrestartuj komputer, jeśli właśnie zainstalowałeś włóczęgę.

Po drugie, wprowadź system BIOS (który wymaga ponownego uruchomienia na większości komputerów) i włącz wirtualizację sprzętu.

Po trzecie, wyłącz Hyper V w systemie Windows. To kłóci się z włóczęgą.

Należy się tym zająć.

Źródło

2017-03-22 16:16:57

miał ten sam problem, to jest rozwiązanie: https://github.com/mitchellh/vagrant/issues/8395#issuecomment-288379271

Zasadniczo trzeba dodać host_ip: "127.0.0.1" do pliku homestead.rb w wierszu 90

Źródło

2017-03-23 17:25:41

I naprawić jest tutaj: https://github.com/mitchellh/vagrant/pull/8399, powinien być zawarty w v1.9.3 –

włóczęga up - ERRNO :: EADDRNOTAVAIL wersji Vagrant 1.9.3

Odpowiedz

Powiązane problemy