Pages

Showing posts with label Vagrant. Show all posts
Showing posts with label Vagrant. Show all posts

Friday, May 1, 2015

Warning: Connection timeout. Retrying... in Vagrant

I got this error when trying to ssh connect to Vagrant instance.

slave01: SSH auth method: private key
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying...
    slave01: Warning: Connection timeout. Retrying…

This is how I resolved that.

Check the running VMs using the command below:
vboxmanage list runningvms

"Cluster_master_1425452823416_28694" {5b4505cb-2b48-45c1-a941-8e4b2d36f29b}
"Cluster_slave01_1425452852606_67792" {740aa005-6666-43e0-9631-a2f2d6e4caa5}
"Cluster_slave02_1425452882392_41607" {888cf959-1978-4474-86ef-ddfaaf3491f5}

Provide the required keyboard input (enter in this case) using following command:
vboxmanage controlvm Cluster_slave01_1425452852606_67792 keyboardputscancode 1c

Progress state: NS_ERROR_FAILURE in Vagrant

I got the following error when trying to start Vagrant instance.

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...

Progress state: NS_ERROR_FAILURE

VBoxManage: error: Failed to create the host-only adapter

VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory

VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterface, interface IHostNetworkInterface

VBoxManage: error: Context: "int handleCreate(HandlerArg*, int, int*)" at line 68 of file VBoxManageHostonly.cpp

I could get this resolved by following action.

I have set up Vagrant cluster and there was one VM that is not running on Vagrant opened and running in VirtualBox. Issue might be due to that as well.

Restart Virtualbox using the following command:

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

Tuesday, March 10, 2015

How to scp Vagrant?

from VM to local:

vagrant scp (name of the Vagrant environment:Vagrant path in the box) (local folder path - from the directory from which Vagrant is loaded)

vagrant scp default:/home/vagrant/jayani jayani

from local to VM:
vagrant scp  (local folder path - from the directory from which Vagrant is loaded) (name of the Vagrant environment:Vagrant path in the box)

vagrant scp jayani /home/vagrant

if you have multiple Vagrant environment precede with the name of the Vagrant environment.
vagrant scp master:jayani /home/vagrant

How to find the name of the Vagrant environment?

execute the following command:
vagrant global-status

id       name    provider   state   directory                                   
---------------------------------------------------------------------------------
894ce03  default virtualbox running /Users/jwithanawasam/
cbb0745  master  virtualbox running /Users/jwithanawasam/
c296e12  slave01 virtualbox running /Users/jwithanawasam/
3c6e261  slave02 virtualbox running /Users/jwithanawasam/

VBoxManage: error: Failed to create the host-only adapter VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open

After configuring some network settings as given below, I got the following error. I have mentioned how I resolved it here.

master.vm.network :private_network, ip: "33.33.33.10"
Vagrant up or Vagrant reload command

Error:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory

VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterface, interface IHostNetworkInterface
VBoxManage: error: Context: "int handleCreate(HandlerArg*, int, int*)" at line 68 of file VBoxManageHostonly.cpp

Solution:

  1. First power off all the VMs running in virtual box
  2. Then run the following command: (For Mac)
sudo /Library/StartupItems/VirtualBox/VirtualBox restart
  1. Then start required VMs