Erro ao subir máquina virtual

161 views
Skip to first unread message

Carlos Groups

unread,
Apr 27, 2014, 1:26:46 PM4/27/14
to livro-devop...@googlegroups.com
Ao rodar o comando "vagrant up" acontece o seguinte erro:


If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

ERROR warden: Error occurred: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.


If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.


If you're using a custom box, make sure that networking is properly

working and you're able to connect to the machine. It is a common

problem that networking isn't setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.


If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.

 INFO warden: Beginning recovery process...

 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001014fd2e0>

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001014a4d48>

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Calling recover: #<Vagrant::Action::Builtin::Call:0x000001014a4dc0>

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO warden: Beginning recovery process...

 INFO warden: Recovery complete.

 INFO environment: Running hook: environment_unload

 INFO runner: Preparing hooks for middleware sequence...

 INFO runner: 1 hooks defined.

 INFO runner: Running action: #<Vagrant::Action::Builder:0x0000010117ffa0>

ERROR vagrant: Vagrant experienced an error! Details:

ERROR vagrant: #<Vagrant::Errors::VMBootTimeout: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.


If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.


If you're using a custom box, make sure that networking is properly

working and you're able to connect to the machine. It is a common

problem that networking isn't setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.


If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.>

ERROR vagrant: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.


If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.


If you're using a custom box, make sure that networking is properly

working and you're able to connect to the machine. It is a common

problem that networking isn't setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.


If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.

ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/wait_for_communicator.rb:72:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/customize.rb:40:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/boot.rb:18:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/customize.rb:40:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/sane_defaults.rb:49:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/set_hostname.rb:16:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/forward_ports.rb:31:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/network.rb:121:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/clear_network_interfaces.rb:26:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/prepare_nfs_settings.rb:15:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/synced_folders.rb:76:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/prepare_nfs_valid_ids.rb:12:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/handle_forwarded_port_collisions.rb:118:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:30:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/env_set.rb:19:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/provision.rb:76:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/clear_forwarded_ports.rb:15:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/set_name.rb:19:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/clean_machine_folder.rb:17:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/check_accessible.rb:18:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/call.rb:51:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/call.rb:51:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/call.rb:51:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/box_check_outdated.rb:65:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/call.rb:57:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builtin/call.rb:57:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/plugins/providers/virtualbox/action/check_virtualbox.rb:17:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/action/runner.rb:69:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/machine.rb:157:in `action'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/batch_action.rb:72:in `block (2 levels) in run'

 INFO interface: error: Timed out while waiting for the machine to boot. This means that

Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.


If you look above, you should be able to see the error(s) that

Vagrant had when attempting to connect to the machine. These errors

are usually good hints as to what may be wrong.


If you're using a custom box, make sure that networking is properly

working and you're able to connect to the machine. It is a common

problem that networking isn't setup properly in these boxes.

Verify that authentication configurations are also setup properly,

as well.


If the box appears to be booting properly, you may want to increase

the timeout ("config.vm.boot_timeout") value.



Não consegui descobrir o motivo do erro, tem alguma ideia?

Alan Martins

unread,
Apr 27, 2014, 2:18:38 PM4/27/14
to livro-devop...@googlegroups.com
Oi Carlos, qual é a parte do livro?

Você instalou o maven?

Veja se esta questão do Maurício não é a mesma que a sua. https://groups.google.com/forum/#!topic/livro-devops-na-pratica/pEaZWc_ytaY

Abraço,
Alan

Danilo Sato

unread,
Apr 27, 2014, 7:47:45 PM4/27/14
to Alan Martins, livro-devop...@googlegroups.com
Oi Carlos,

Esse parece ser um erro do Vagrant/VirtualBox. Pela mensagem, o Vagrant ficou esperando a máquina virtual subir e deu um timeout pois não ouviu nada de volta do VirtualBox.

Algumas ideias para debuggar isso:

* Se você abrir o VirtualBox, a máquina virtual subiu? Você consegue acessá-la por lá? Se sim, aumentar o timeout do Vagrant conforme a mensagem de erro sugere, pode ajudar. Se não, pode ser que tenha algum problema com a instalação do VirtualBox ou da box precise32 que você instalou.

* Tenta rodar o comando do vagrant up com a opção "--debug", isso dará um pouco mais de informações sobre onde o Vagrant está empacando.

Assim que tentar essas coisas, manda um update aqui na lista para todos saberem como resolver se encontrarem um problema parecido.

Abraços,
Danilo



--
Você recebeu essa mensagem porque está inscrito no grupo quot;Livro "Devops na Prática"" dos Grupos do Google.
Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie um e-mail para livro-devops-na-p...@googlegroups.com.
Para mais opções, acesse https://groups.google.com/d/optout.



--

alandr...@gmail.com

unread,
Mar 7, 2017, 9:36:02 PM3/7/17
to Livro "Devops na Prática"
Conseguiram entender porque na subida da maquina fica:

  db: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.


Da impressão que esta tentando fazer negociação de SSH e não esta conseguindo. Porque no Windows não temos este problema?  

Sobre o parametro:

config.vm.boot_timeout") value
Como poderiamos seta-lo: Seria no Vagrantfile?  como podemos setar este timeout? Se tiver pendencia de negociação SSH, nao vai adiantar.
Enfim acessei a console do virtualbox, e a maquina subiu..
Reply all
Reply to author
Forward
0 new messages