Failing "underlying SSH library" #509

michaelpporter · 2016-03-10T16:32:11Z

I am unable to build new boxes now. I am working on setup base configs for our team. I started seeing this issue on a brand new mac it has ansible 2.0.1.0 and vagrant 1.81.

Since I had it working on my system I downloaded a fresh copy of Drupal VM, changed the IP and ran in to the same issues I recently upgraded to Vagrant 1.8.1 (was 1.7.X) and ansible 2.1.0

==> drupalvm: [vagrant-hostsupdater] 192.168.88.87 dashboard.drupalvm.dev # VAGRANT: d64d789cabcb9fcfdf063adb87e96f6f (drupalvm) / d7e8c3b6-129a-475c-b7f1-02ddcdc8c6c9
==> drupalvm: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> drupalvm: Setting hostname...
**An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating**

geerlingguy · 2016-03-10T16:38:46Z

I haven't noticed this issue on either of my Macs (just brought up two new Drupal VM instances this morning, a few minutes ago, for testing); it sounds like it could be a networking issue, or even a permissions issue... can you try to restart your Mac and run vagrant up again, and failing that, also see some of the notes from this issue: hashicorp/vagrant#6854

Other potential hints:

timeout during server version negotiating puphpet/puphpet#2070
Vagrant up takes long time after installing guest additions manually in centos box hashicorp/vagrant#6812

michaelpporter · 2016-03-11T15:38:47Z

Mind sharing what version of vagrant and ansible you are running?

geerlingguy · 2016-03-11T15:43:03Z

$ vagrant --version
Vagrant 1.8.1

$ ansible --version
ansible 2.0.1.0

michaelpporter · 2016-03-14T12:59:07Z

FWTW: I have VirtualBox 5.0.16; I also noticed a fresh install of vagrant gets VirtualBox 5.0.10. The issue was solved by adding "vagrant-vbguest".

vagrant plugin install vagrant-vbguest

geerlingguy · 2016-03-14T13:08:09Z

Ah, so that fix strikes again! Annoying,,, also, I just updated all the base boxes so they have the 5.0.16 guest additions by default; you can run vagrant box update geerlingguy/ubuntu1404 to get the latest version.

michaelpporter · 2016-03-16T15:14:14Z

FYI, I have discovered that the issues I am having have to do with the ZyWall Firewall we have at work. I can build and destroy over and over again at home, go to the office and it fails. I tested this by hardwiring to the firewall, failed; then to the Comcast Gateway, worked.

I will be looking over the settings in the firewall to see if I can get it to pass. It seems that google DNS is trying to ping back a fail on the hostname setup and the firewall is blocking it, just a guess based on the logs.

javasavvy · 2016-06-22T22:02:02Z

I'm currently having this same issue on my windows 10 machine. I tried adding the vagrant-vbguest plugin as mentioned above but no luck.

geerlingguy · 2016-06-22T23:18:09Z

@javasavvy - It seems this problem was caused in the past by network issues. Can you try again on a different network/location?

javasavvy · 2016-06-23T00:17:34Z

Unfortunately, I need it to work on my current network or it's not usable for me.
Your probably right though as I'm using a VMware VM as the host machine (So essentially a virtualbox vm within a vmware vm).

I got past this by setting natdnshostresolver1 to off in the Vagrantfile. reference here:
hashicorp/vagrant#6812

I immediately hit another issue though so It seems I won't be able to use this vagrant vm. (My first time working with vagrant and it's been a bit ruff). The next issue appears to be an vagarant 1.8.1 problem itself. I'm getting the "stdin: is not a tty". and vagarant fails..
Found a reference for a fix here:
hashicorp/vagrant#1673

But I was not able to get it working.

scott-cornwell · 2016-08-18T01:15:33Z

Same issue here. Can't bring up any VMs :(

Sukhada11 · 2016-08-23T14:43:57Z

Same issue here too..Windows 10

cloud9business · 2016-09-05T22:13:21Z

Thank you @michaelpporter . I've been struggling with this issue on my iMac for the last 2 years. vagrant plugin install vagrant-vbguest
seems to have solved it.

Mich-b · 2016-11-27T07:57:29Z

Same issue

Mich-b · 2016-11-27T12:12:26Z

Update: just checking the box 'cable connected' in network settings of VirtualBox solved the issue ;)

geerlingguy · 2016-11-27T15:56:01Z

@Mich-b - Also consider installing the vbguest plugin; that might help make sure this kind of error doesn't happen again.

Mich-b · 2016-11-27T16:09:06Z

Had to modify some other things as well:

installed vbguest
checked 'cable connected' in virtualbox network settings
replaced https://download.jetbrains.com/idea/ideaIC-2016.2.4.tar.gz with https://download.jetbrains.com/idea/ideaIC-2016.2.5.tar.gz in vagrant_provisioning.sh (as the 2.4 version is not available anymore)
included branch in clone command (Vagrantfile) :"git clone --branch 7.1 https://github.com/WebGoat/WebGoat.git "

Working now. Thanks for the help

javasavvy · 2016-11-27T17:36:47Z

Sorry about that last e-mail. It was a mistake.

…

On Nov 27, 2016 12:56 AM, "Justin Fleming" ***@***.***> wrote: go have fun with your self On Jun 22, 2016 4:18 PM, "Jeff Geerling" ***@***.***> wrote: > @javasavvy <https://github.com/javasavvy> - It seems this problem was > caused in the past by network issues. Can you try again on a different > network/location? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#509 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe/AFBU1sM43IWCzIgs06W_hW8Tvb1ekouJks5qOcK0gaJpZM4Ht5xY> > . >

geerlingguy · 2016-11-27T19:04:56Z

:)

wjz2047 · 2017-02-06T13:05:29Z

@michaelpporter , same issue here:works fine at home, fails at office. can you give me some suggestion?

xenomedia-deploy · 2017-02-06T14:39:07Z

@wjz2047 We just removed the ZyWall from part of our network; it was used so the office manager could VPN. Apologies, I can not offer more help.

wjz2047 · 2017-02-07T00:32:10Z

@xenomedia-deploy ,thanks anyway

numediaweb · 2017-11-25T08:00:01Z

what worked for me was:

vagrant halt
vagrant up --provision

totymedli · 2017-12-30T18:23:35Z

For me, the hanging happened because the bootloader was waiting for an input. I did the following:

Stop the VM (I did it in the VirtualBox GUI).
vagrant up
During booting, press Enter a few times. This can be done via the GUI or the command line. Just follow what this answer suggested.

geerlingguy added the question label Mar 10, 2016

geerlingguy added mac upstream labels Mar 10, 2016

geerlingguy closed this as completed Mar 10, 2016

geerlingguy mentioned this issue Jan 19, 2017

Vagrant Up stuck at SSH (Win8) #1129

Closed

jtsternberg mentioned this issue Feb 28, 2017

An error occurred in the underlying SSH library that Vagrant uses. hashicorp/vagrant#7965

Closed

blakemorgan mentioned this issue May 18, 2019

Error with underlying SSH library (Windows 10 and Cmder) #1930

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failing "underlying SSH library" #509

Failing "underlying SSH library" #509

michaelpporter commented Mar 10, 2016

geerlingguy commented Mar 10, 2016

michaelpporter commented Mar 11, 2016

geerlingguy commented Mar 11, 2016

michaelpporter commented Mar 14, 2016

geerlingguy commented Mar 14, 2016

michaelpporter commented Mar 16, 2016

javasavvy commented Jun 22, 2016

geerlingguy commented Jun 22, 2016

javasavvy commented Jun 23, 2016

scott-cornwell commented Aug 18, 2016

Sukhada11 commented Aug 23, 2016

cloud9business commented Sep 5, 2016

Mich-b commented Nov 27, 2016

Mich-b commented Nov 27, 2016

geerlingguy commented Nov 27, 2016

Mich-b commented Nov 27, 2016 •

edited

javasavvy commented Nov 27, 2016 via email

geerlingguy commented Nov 27, 2016

wjz2047 commented Feb 6, 2017

xenomedia-deploy commented Feb 6, 2017

wjz2047 commented Feb 7, 2017

numediaweb commented Nov 25, 2017

totymedli commented Dec 30, 2017

Failing "underlying SSH library" #509

Failing "underlying SSH library" #509

Comments

michaelpporter commented Mar 10, 2016

geerlingguy commented Mar 10, 2016

michaelpporter commented Mar 11, 2016

geerlingguy commented Mar 11, 2016

michaelpporter commented Mar 14, 2016

geerlingguy commented Mar 14, 2016

michaelpporter commented Mar 16, 2016

javasavvy commented Jun 22, 2016

geerlingguy commented Jun 22, 2016

javasavvy commented Jun 23, 2016

scott-cornwell commented Aug 18, 2016

Sukhada11 commented Aug 23, 2016

cloud9business commented Sep 5, 2016

Mich-b commented Nov 27, 2016

Mich-b commented Nov 27, 2016

geerlingguy commented Nov 27, 2016

Mich-b commented Nov 27, 2016 • edited

javasavvy commented Nov 27, 2016 via email

geerlingguy commented Nov 27, 2016

wjz2047 commented Feb 6, 2017

xenomedia-deploy commented Feb 6, 2017

wjz2047 commented Feb 7, 2017

numediaweb commented Nov 25, 2017

totymedli commented Dec 30, 2017

Mich-b commented Nov 27, 2016 •

edited