Vagrant up forces shutdown of VM #8520
Comments
|
Same here on Vagrant 1.9.4, Windows 10 Home x64 and VirtualBox 5.1.20 with box ubuntu/xenial64 (v20170424.0.0). |
|
I had the same error here (Vagrant 1.9.4, Windows 7 x64, VB 5.1.20 with box ubuntu/xenial64). It looks like an exception As a workaround, I added |
|
@clamb Did that work very well? |
|
Same error for me. I've downgraded to 1.9.3. Works OK. |
|
Same thing for me for both Vagrant 1.9.3 and 1.9.4, Win 7 and VirtualBox 5.1.20 |
|
Is any fix coming? I am stuck and can't launch any VM since tow days 😞 |
|
@bbkane I was able to provision my machine a couple of time, but I am unaware of side effects. |
In some cases the SSH connection may be aborted while waiting for setup. This includes aborted connections in the list of applicable exceptions to retry on while waiting for the connection to become available. Fixes hashicorp#8520
|
@chrisroberts Thanks for fixing the issue! I noticed you put it on the 1.9.5 milestone. Pardon my ignorance, but how soon will this change be reflected on the Downloads page? |
|
Update: Following is no longer needed: For example in windows, those files are located in
replace them with new en.yml, errors.rb and communicator.rb Then you are good to go. It worked on my Windows 10 machine. One gotcha is in Windows, you have to change folder permission of the directory to edit or create new files. |
|
@joelhandwell Thank you!!! |
|
Me too, after replacing 3 files everything goes right. Thanks! |
|
The same for me: Windows 10 x64, VirtualBox Version 5.1.22 , Vagrant 1.9.4. Thanks a lot! |
|
sorry i have windows 8 i can't fix this problem....can you help me? |
|
This is my error C:\lab>vagrant up |
|
I have this error with the current version (1.9.4) with C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) |
|
Same problem (Version 1.9.4) |
|
I am getting the same error - C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/serv c:\Tools\rkt\rkt>vagrant version You're running an up-to-date version of Vagrant! Windows Version 7 |
|
to fix this kind of problem you could replace 3 files like above: For example in windows, those files are located in C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/templates/locales/en.yml and then try vagrant halt vagrant provision \ vagrant destroy vagrant up |
|
Thank you. The fix has worked in windows 8.1 pro. |
|
You can also back to 1.9.3 until 1.9.5 is out. Both solutions worked for me
on w7
Regards.
El sáb., 6 may. 2017 6:58, ksunilsurya <notifications@github.com> escribió:
… Thank you. The fix has worked in windows 8.1 pro.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8520 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQs54ZXIRwm9w2Vd2t6fEH2pqf-PFDQ9ks5r2_3rgaJpZM4NHCZL>
.
|
|
@joelhandwell Thank you so much! You really saved my day! I really owe you one! |
|
@NaruAna all the credit should go @chrisroberts who fixed this issue with #8526 . I'm not the one who spend time and effort for debugging. Thank you @chrisroberts, you saved my day, and all others who arrived this issue. Also if Vagrant is written in golang like terraform and released as binary, this fix was not possible. So this fix was possible with the scripting language called Ruby. |
|
@joelhandwell thank you! The 3 file substitution fix resolved my Vagrant issue with Hyperledger Fabric. |
|
Still doesn't work for me. Setup: Windows 10 + VirtualBox 5.1.22 + Vagrant 1.9.4 Tried:
Still getting errors. Any chance of an expedited fix or another workaround? This prevents me from being able to work. |
|
Thanks @joelhandwell ! the 3 files fix the problem. |
|
Fixed by uninstalling v1.9.4 and installing v1.9.3. |
|
Thank's @joelhandwell, your suggestion resolved my problem. |
|
@chrisroberts Thanks! It worked for me on Win10, VM 5.1.18, Vagrant 1.9.4, |
|
@joelhandwell Thank you so much! I have hearattack already comming ;) |
|
@joelhandwell Replacing the three files fixed it. |
|
Thank's @joelhandwell <3 |
|
@joelhandwell Thank you so much! |
|
@joelhandwell Thank you so much man! |
|
Thank you! @joelhandwell |
|
I had same problem of attempting to "vagrant up" with latest version of Vagrant v1.9.4 while attempting vagrant based setup of Mesosphere DC/OS with Windows 10 and VirtualBox. The VM setup kept shutting down at these lines: default: SSH auth method: private key Tried several times then found this report from "dnsmichi" at https://monitoring-portal.org/index.php?thread/40651-icinga2-vagrant-problem-up-ing-on-windows-10-machine/ Indeed reverting from Vagrant v1.9.4 back to v1.9.3 fixed the problem. |
|
do 1.9.5 fix this? |
|
Yes, it does:
|
|
@joelhandwell Thank you! |
|
I'm getting this issue after a fresh install of Windows 10, Virtual Box |
|
check @joelhandwell answer. Have the same setup and fixed it. |
|
@joelhandwell Yes it did solve the issue. Thanks man! |
|
Getting same issue with Win10, Vagrant 1.9.7 and Virtualbox 5.1.24 |
|
I'm getting the error as well on Vagrant 1.9.7 and VirtualBox 5.0.6 & 5.1.24 (tried upgrading) |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
and others
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
Vagrant 1.9.4
Host operating system
Windows 7
Guest operating system
bento/centos-7.3
Vagrantfile
Debug output
https://gist.github.com/bbkane/8a207e5fd0a33e5ad9caca0e3ec3c230
Expected behavior
I should have gotten a box
Actual behavior
I got the error messages linked to above
Steps to reproduce
vagrant upNotes
config.vm.boot_timeoutbut that didn't helpTruncated Error
For Github searchability
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
vagrant sharefails with `read_nonblock': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED) #7832 look kind of similar (read_nonblockinstead ofreadpartialandvagrant shareinstead ofvagrant up)The text was updated successfully, but these errors were encountered: