search

hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.27k stars 4.43k forks source link

sh_exchange_identification: Connection closed by remote host #443

Closed grimen closed 12 years ago

grimen commented 13 years ago

This happens very often, and last time it happened was even after a successful Chef Soli provisioning in OS X (what I use):

[core] [Thu, 28 Jul 2011 21:54:42 +0000] INFO: template[/etc/fail2ban/fail2ban.conf] sending restart action to service[fail2ban] (delayed)
: stdout
[core] [Thu, 28 Jul 2011 21:54:42 +0000] INFO: Processing service[fail2ban] action restart (fail2ban::default line 33)
: stdout
[core] [Thu, 28 Jul 2011 21:54:44 +0000] INFO: service[fail2ban] restarted
: stdout
[core] [Thu, 28 Jul 2011 21:54:44 +0000] INFO: template[/etc/init/redis.conf] sending restart action to service[redis] (delayed)
: stdout
[core] [Thu, 28 Jul 2011 21:54:44 +0000] INFO: Processing service[redis] action restart (redis::init line 41)
: stdout
[core] [Thu, 28 Jul 2011 21:54:45 +0000] INFO: service[redis] restarted
: stdout
[core] [Thu, 28 Jul 2011 21:54:45 +0000] INFO: Chef Run complete in 1544.090589 seconds
[Thu, 28 Jul 2011 21:54:45 +0000] INFO: Running report handlers
[Thu, 28 Jul 2011 21:54:45 +0000] INFO: Report handlers complete
: stdout
grimen@grimen-macbook-pro:merchii/merchii-core ‹feature/vagrant-provisioning*›$ vagrant ssh
ssh_exchange_identification: Connection closed by remote host

Sometimes it solves by destroying the VM (didn't work for "lucid32" box), but recompiling a chef solo stack everytime sucks real hard.

Is this related? Seems like it related to 0.8 as it requires VirtualBox 4.1.

$ vagrant up     
[core] Importing base box 'base'...
[core] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.0.6
VirtualBox Version: 4.1.0
[core] Preparing host only network...
mitchellh commented 13 years ago

There has been some weirdness with guest additions 4.0.6 and 4.1.0. The lucid32/lucid64.box on files.vagrantup.com are now 4.1.0 boxes. Could you try those and let me know if the issue still occurs?

Best, Mitchell

grimen commented 13 years ago

Thanks, I will try it tonight and get back.

hedgehog commented 13 years ago

@grimen, can you take a look at issue #391, particularly the output from netstat -an, or lsof -i :222 in the the working/not-working cases. Please add your failing and passing configuration details to this page

The VirtualBox GuestAdditions issue can be resolved along these lines

If this issue is as described in issue #391 could you close this issue?

grimen commented 13 years ago

@hedgehog Conclusion after some more debugging today: "lucid32" and "lucid64" don't work (for me). This one worked now: talifun-ubuntu-11.04-server-i386.box

I've decided to postpone any more debugging of Vagrant to the future as I spent a day on it already debugging, and I'm working against a deadline in mid august (site launch) so gotta focus on coding. I'll get back when I got some spare time, hope that's cool.

P.S. lsof -i :222 didn't give me much.

Thanks for the hint on guest additions, will fix those on the "talifun" box.

mitchellh commented 12 years ago

Related to #391. Please continue any discussion there.