Skip to content

Instantly share code, notes, and snippets.

@psaitu
Created March 25, 2015 16:51
Show Gist options
  • Select an option

  • Save psaitu/60510a4b6ce12ee3802d to your computer and use it in GitHub Desktop.

Select an option

Save psaitu/60510a4b6ce12ee3802d to your computer and use it in GitHub Desktop.
Bringing machine 'blimp' up with 'virtualbox' provider...
==> blimp: Importing base box 'ubuntu-12.04-amd64-daily'...
==> blimp: Matching MAC address for NAT networking...
==> blimp: Setting the name of the VM: blimp_blimp_1427302184848_68078
==> blimp: Clearing any previously set forwarded ports...
==> blimp: Clearing any previously set network interfaces...
==> blimp: Preparing network interfaces based on configuration...
blimp: Adapter 1: nat
blimp: Adapter 2: hostonly
==> blimp: Forwarding ports...
blimp: 3000 => 3000 (adapter 1)
blimp: 9200 => 9200 (adapter 1)
blimp: 22 => 2222 (adapter 1)
==> blimp: Running 'pre-boot' VM customizations...
==> blimp: Booting VM...
==> blimp: Waiting for machine to boot. This may take a few minutes...
blimp: SSH address: 127.0.0.1:2222
blimp: SSH username: vagrant
blimp: SSH auth method: private key
blimp: Warning: Connection timeout. Retrying...
blimp: Warning: Connection timeout. Retrying...
blimp: Warning: Remote connection disconnect. Retrying...
blimp:
blimp: Vagrant insecure key detected. Vagrant will automatically replace
blimp: this with a newly generated keypair for better security.
blimp:
blimp: Inserting generated public key within guest...
blimp: Removing insecure key from the guest if its present...
blimp: Key inserted! Disconnecting and reconnecting using new SSH key...
==> blimp: Machine booted and ready!
==> blimp: Checking for guest additions in VM...
blimp: The guest additions on this VM do not match the installed version of
blimp: VirtualBox! In most cases this is fine, but in rare cases it can
blimp: prevent things such as shared folders from working properly. If you see
blimp: shared folder errors, please make sure the guest additions within the
blimp: virtual machine match the version of VirtualBox you have installed on
blimp: your host and reload your VM.
blimp:
blimp: Guest Additions Version: 4.1.12
blimp: VirtualBox Version: 4.3
==> blimp: Setting hostname...
==> blimp: Configuring and enabling network interfaces...
==> blimp: Mounting shared folders...
blimp: /vagrant => /Users/prabhusaitu/Documents/ClientProjects/BlimpDB/blimp
==> blimp: Running provisioner: ansible...
PYTHONUNBUFFERED=1 ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false ANSIBLE_SSH_ARGS='-o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s' ansible-playbook --private-key=/Users/prabhusaitu/Documents/ClientProjects/BlimpDB/blimp/.vagrant/machines/blimp/virtualbox/private_key --user=vagrant --connection=ssh --limit='blimp' --inventory-file=provision/inventory --sudo -vvvv provision/playbook.yml
PLAY [blimp] ******************************************************************
GATHERING FACTS ***************************************************************
<192.168.56.200>
<192.168.56.200>
<192.168.56.200> IdentityFile=/Users/prabhusaitu/Documents/ClientProjects/BlimpDB/blimp/.vagrant/machines/blimp/virtualbox/private_key ConnectTimeout=10 KbdInteractiveAuthentication=no PasswordAuthentication=no UserKnownHostsFile=/dev/null User=vagrant ControlPath=/Users/prabhusaitu/.ansible/cp/ansible-ssh-%h-%p-%r PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey StrictHostKeyChecking=no ControlMaster=auto Port=22 ControlPersist=60s
fatal: [blimp] => SSH encountered an unknown error. The output was:
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/prabhusaitu/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug1: auto-mux: Trying existing master
debug1: Control socket "/Users/prabhusaitu/.ansible/cp/ansible-ssh-192.168.56.200-22-vagrant" does not exist
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.56.200 [192.168.56.200] port 22.
debug2: fd 3 setting O_NONBLOCK
debug1: connect to address 192.168.56.200 port 22: Operation timed out
ssh: connect to host 192.168.56.200 port 22: Operation timed out
TASK: [make sure the system encoding is utf-8] ********************************
FATAL: no hosts matched or all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/Users/prabhusaitu/playbook.retry
blimp : ok=0 changed=0 unreachable=1 failed=0
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment