upgrading to 1.5.4 problem: vagrant up gives error downloading file #3589
Comments
lmcardle
changed the title
|
On Thu, May 1, 2014 at 8:57 AM, Liam notifications@github.com wrote:
whats the actual full command you typed? can you try like vagrant box add name http:// ? |
|
I can not do something simple like this: That looks good...however, when I run vagrant up, this is what I get: $ vagrant up |
|
Can you please attach a debug log? |
|
Ah. |
|
Any box I do that to causes the same error |
|
You need to do |
|
Still getting an error, when not using a URL: $ vagrant init myBox ~/Downloads/my_base_box.box $ vagrant up |
|
Similar thing happens when I try to add a box to vagrant: $ vagrant box add ~/Downloads/my_base_box.box --name MyNewBox |
|
Debug log |
|
vagrant up --debug DEBUG box_add: Deleting temporary box: INFO warden: Beginning recovery process... INFO warden: Beginning recovery process... INFO warden: Beginning recovery process... INFO warden: Beginning recovery process...
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/downloader.rb:179:in An error occurred while downloading the remote file. The error INFO interface: Machine: error-exit ["Vagrant::Errors::DownloaderError", "An error occurred while downloading the remote file. The error\nmessage, if any, is reproduced below. Please fix this error and try\nagain.\n\n"] |
|
You're getting this weirdness: That is odd. You tried removing all of |
|
I did...tried reinstalling earlier version as well as latest version...no change. |
|
Yea, I just tried it again...removed the whole /Applications/Vagrant folder, removed the /usr/bin/vagrant file. Then I downloaded a new version of Vagrant, installed it, and I still get the error. It is really odd, as I have been using vagrant for over a year and never any problems like this. |
|
Super weird. What version of OS X is this? |
|
10.9.2 |
|
Totally frustrating. I tried downloading a brand new box (http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-10.04_chef-provisionerless.box) and get the same issue $ vagrant box add opscode_ubuntu-10.04_chef-provisionerless.box --name OpscodeUbuntu $ vagrant box add opscode_ubuntu-10.04_chef-provisionerless.box --name OpscodeUbuntu --debug DEBUG box_add: Deleting temporary box: INFO warden: Beginning recovery process...
ERROR vagrant: /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.4/lib/vagrant/util/downloader.rb:179:in INFO interface: error: An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again. An error occurred while downloading the remote file. The error INFO interface: Machine: error-exit ["Vagrant::Errors::DownloaderError", "An error occurred while downloading the remote file. The error\nmessage, if any, is reproduced below. Please fix this error and try\nagain.\n\n"] |
|
Another interesting note, vagrant box add and vagrant up after initing this way also does not work: vagrant init OpscodeUbuntu1004 http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-10.04_chef-provisionerless.box |
|
I have now 3 other people having issues. One differerence I see is within /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/subprocess.rb, on line 79. One computers where it is working, @command[0] is equal to: /usr/bin/VBoxManage. On the machines where it is not working, @command[0] is equal to /Applications/Vagrant/bin/../embedded/bin/curl. |
|
Why would command[0] be different? It seems like it can not find an environment variable. |
|
Another similar issue is that it works on Mac 10.9, but not on 10.9.2. The issue appears as soon as a user installs the Security Update 2014-002 (http://support.apple.com/kb/HT6207) |
|
@lmcardle Pretty strange, but in terms of command[0] being differnet it sounds like they're just executing different executables. One is executing VBoxManage and one is executing cURL. |
|
Fixed. If you remove this if block, from within /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.2/lib/vagrant/util/subprocess.rb, everything ends up working: if @command[0].downcase.include?(installer_dir) |
|
Hm, so that is there for a very important reason. If there are conflicting libraries between the installer and the system, it prioritizes the installer libraries over non-installer libraries. I wonder why that is causing you problems and how we can make it work in both cases. |
|
Apple's Security Update 2014-002 contains these two changes that affect Ruby. These are likely the cause: Ruby Ruby |
|
We are now at about a dozen people, all who install Apple's security fix, who get this issue. So we are manually commenting out that line. There has to be a better way to fix this. |
|
We area also affected by this issue. Commenting out the ruby line above fixed it. We are on 10.9.2 as well |
ghost
mentioned this issue
|
Still no word on this? Removing those lines from subprocess.rb didn't workout for me. |
|
Commenting out the ruby block worked to solve this problem for me too on Mavericks. |
|
I just hit this problem today too. Here's my setup: Any updates on this?? Thanks! |
|
Getting the same error on OSX 10.9.5... |
|
Why hello everyone! You can read more of my explanation on #3972, but I was able to reproduce this by:
I was able to fix it by:
Unfortunately I do not see a better option, and I do not think this is something Vagrant core core even address. The issue is happening with linked files at install time, not runtime. |
|
Edit: It appears this issue is caused by the corporate image of OSX I received I just got a new laptop and I was experiencing this same issue with OSX 10.10.3, and Vagrant 1.7.2. I did some digging and found a couple of LD environment variables that can be set to get some extra info. So I ran the following: export DYLD_PRINT_LIBRARIES_POST_LAUNCH=true
export DYLD_PRINT_ENV=true
export VAGRANT_LOG=debugThen I ran a vagrant up, and saw this in the logs The important bits seems to be this: I did some quick google searching but I couldn't find much about that file or what it is. However, after running the following command, I was able to successfully start a box download: I tried just unsetting the environment variable, but that did not work. This seems to be a better compromise than commenting out the line from |
|
Following command fixed the problem with vagrant 1.7.2
|
ghost
locked and limited conversation to collaborators
I have been using vagrant with no issues for a long time. All of a sudden though, I am not able to run vagrant up, right after running vagrant init . When I run vagrant up I get the error:
"An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again."
No other error message is given.
Everything works fine with boxes that are already added to vagrant. however, even that, I get the same error when I try to add new boxes to vagrant: i.e vagrant box add --name someName
Any thoughts on what might have gone wrong? The only change I made was upgrading to the latest version of vagrant, 1.5.4. I tried uninstalling and re-installing an earlier version, but I still have the same issue. I never had this issue prior to installing 1.5.4.
The text was updated successfully, but these errors were encountered: