Vagrant Up installation errors?

[lydia...@alumni.utoronto.ca]

Hi all: 

I am experiencing a problem when trying to install Vagrant Up. Any ideas what is wrong? Here is what I see in command prompt:

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Lydia>mkdir atom-vagrant && cd atom-vagrant

A subdirectory or file atom-vagrant already exists.

C:\Users\Lydia>vagrant init artefactual/atom

A `Vagrantfile` has been placed in this directory. You are now

ready to `vagrant up` your first virtual environment! Please read

the comments in the Vagrantfile as well as documentation on

`vagrantup.com` for more information on using Vagrant.

C:\Users\Lydia>cd atom-vagrant

C:\Users\Lydia\atom-vagrant>vagrant init artefactual/atom

`Vagrantfile` already exists in this directory. Remove it before

running `vagrant init`.

C:\Users\Lydia\atom-vagrant>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Box 'artefactual/atom' could not be found. Attempting to find and i

nstall...

    default: Box Provider: virtualbox

    default: Box Version: >= 0

==> default: Loading metadata for box 'artefactual/atom'

    default: URL: https://atlas.hashicorp.com/artefactual/atom

==> default: Adding box 'artefactual/atom' (v2.3.0.0) for provider: virtualbox

    default: Downloading: https://atlas.hashicorp.com/artefactual/boxes/atom/ver

sions/2.3.0.0/providers/virtualbox.box

==> default: Box download is resuming from prior download progress

    default: Progress: 100% (Rate: 451k/s, Estimated time remaining: --:--:--)

==> default: Successfully added box 'artefactual/atom' (v2.3.0.0) for 'virtualbo

x'!

==> default: Importing base box 'artefactual/atom'...

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "C:/Users/Lydia/.vagrant.d/boxes/artefactual-VAGRANTSLASH-at

om/2.3.0.0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "packer-virtualbox-ov

f-1455163771_1455651262488_654", "--vsys", "0", "--unit", "7", "--disk", "C:\\Us

ers\\Lydia\\VirtualBox VMs\\packer-virtualbox-ovf-1455163771_1455651262488_654\\

packer-virtualbox-ovf-1455163771-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Interpreting C:\Users\Lydia\.vagrant.d\boxes\artefactual-VAGRANTSLASH-atom\2.3.0

.0\virtualbox\box.ovf...

OK.

0%...

Progress state: VBOX_E_FILE_ERROR

VBoxManage.exe: error: Appliance import failed

VBoxManage.exe: error: Could not create the imported medium 'C:\Users\Lydia\Virt

ualBox VMs\packer-virtualbox-ovf-1455163771_1455651262488_654\packer-virtualbox-

ovf-1455163771-disk1.vmdk'.

VBoxManage.exe: error: VMDK: cannot write allocated data block in 'C:\Users\Lydi

a\VirtualBox VMs\packer-virtualbox-ovf-1455163771_1455651262488_654/packer-virtu

albox-ovf-1455163771-disk1.vmdk' (VERR_DISK_FULL)

VBoxManage.exe: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component A

pplianceWrap, interface IAppliance

VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleImportAppliance(s

truct HandlerArg *)" at line 877 of file VBoxManageAppliance.cpp

C:\Users\Lydia\atom-vagrant>

[Dan Gillean]

Hi Lydia,

A couple of brief checks before I ask a developer to take a look at this thread.
 

First, have you double-checked the requirements we list? You'll need to make sure that your version of Vagrant is 1.6 or higher, and that you're using Virtualbox 4.3 or newer. Some package managers will install lower versions by default (e.g. Ubuntu 14.04 will install Vagrant 1.4.3), so it's worth checking :)

• https://www.accesstomemory.org/docs/2.3/admin-manual/installation/vagrant/

Second: I noticed that when you initially tried to create the atom-vagrant directory, your command prompt returned that such a subdirectory already existed - meaning it did not at that time make a new one, or switch you to it - you are still at C:\Users\Lydia> at the time that you ran vagrant init  - then you seem to realize this, and switched into the existing directory, and tried to run the init command again, but the command prompt responds that there is already an init file in there, which you must remove before you can run it again. I'm guessing that you tried to follow the installation more than once, and there were perhaps some remnants from previous attempts - or from earlier versions of the vagrant box? I don't see the older init being removed, so when you ran vagrant up, I think Vagrant was trying to boot up whatever was in there previously, not the most recent download - the most recent one got placed in C:\Users\Lydia>. So it's possible that something went wrong with your first attempt, and then with this attempt, you were inadvertently using the remnants of the first installation attempt?

I would suggest first fully removing all current remnants from both C:\Users\Lydia>, including the current atom-vagrant directory, and trying it again - I'm hopeful it might just work. I'll also check with our developers to see if they have any further suggestions.

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/dd372f6c-e14b-4417-9dd0-306a2f87e7cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dan Gillean]

Hi again Lydia,

Missed this before, but I am guesing this is actually the source of the issue:

(VERR_DISK_FULL)

As in: your disk is full :) If you make more space (we recommend 8GB's of disk space minimum on the Vagrant instructions page), things will probably go smoother.

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

[lydia...@alumni.utoronto.ca]

Hi Dan:

Thanks for pointing this out! Do you know if it's possible for me to install Vagrant and run it using an external hard drive? I don't have 8GB available on my computer, unfortunately. 

[Dan Gillean]

Hello again Lydia,

I've not tried this myself, but it does look like it should be possible. See:

• https://www.virtualbox.org/manual/ch10.html

In 10.1, "Where Virtualbox stores its files," there is a note at the end of 10.1.1:

You can change the default machine folder by selecting "Preferences" from the "File" menu in the VirtualBox main window. Then, in the window that pops up, click on the "General" tab. Alternatively, use VBoxManage setproperty machinefolder; see Section 8.27, “VBoxManage setproperty”.

Let us know how it goes!

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/00131b50-5021-447f-9820-2bd130a261a1%40googlegroups.com.

[lydia...@alumni.utoronto.ca]

Hi Dan:

I managed to clear up additional hard drive space on my machine, but am facing some other mysterious errors now. When I "vagrant up" in command prompt, this is what I get:

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Lydia>cd atom-vagrant

C:\Users\Lydia\atom-vagrant>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Checking if box 'artefactual/atom' is up to date...

==> default: Clearing any previously set forwarded ports...

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

    default: Adapter 1: nat

    default: Adapter 2: hostonly

==> default: Forwarding ports...

    default: 80 (guest) => 8000 (host) (adapter 1)

    default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Running 'pre-boot' VM customizations...

==> default: Booting VM...

==> default: Waiting for machine to boot. This may take a few minutes...

The guest machine entered an invalid state while waiting for it

to boot. Valid states are 'starting, running'. The machine is in the

'poweroff' state. Please verify everything is configured

properly and try again.

If the provider you're using has a GUI that comes with it,

it is often helpful to open that and watch the machine, since the

GUI often has more helpful error messages than Vagrant can retrieve.

For example, if you're using VirtualBox, run `vagrant up` while the

VirtualBox GUI is open.

The primary issue for this error is that the provider you're using

is not properly configured. This is very rarely a Vagrant issue.

C:\Users\Lydia\atom-vagrant>

I can go to my Oracle VM VirtualBox and start atom-vagrant manually, which results in this:

It is not clear to me if the box should be black like that. I have tried using my local browser to access http://10.10.10.10 at this point, but it doesn't connect.

[David Juhasz]

Hi Lydia,

If you click on the black screen of the virtualbox instance, do you get a login prompt? The default credentials are vagrant/vagrant.  if you can login, you may be able to get some clue as to why vagrant up is failing.

You could also try re-provisioning the vagrant box, if you can't get a login prompt. On the command line do:

C:\Users\Lydia>cd atom-vagrant

C:\Users\Lydia\atom-vagrant>vagrant provision

After the box is re-provisioned, you can try "vagrant up" again.

Best regards,

David

--

David Juhasz
Director, AtoM Technical Services

Artefactual Systems Inc.
www.artefactual.com

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/7846b965-8428-4421-92ef-b4107bd839e5%40googlegroups.com.

[lydia...@alumni.utoronto.ca]

Hi David:

There is no log-in prompt when I click on the black screen. It seems unresponsive when I click on it. 

I tried to use vagrant provision, but there doesn't seem to be a big change. After I "vagrant up" the second time, after provisioning, it does say this:

C:\Users\Lydia\atom-vagrant>vagrant provision

C:\Users\Lydia\atom-vagrant>vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Checking if box 'artefactual/atom' is up to date...

==> default: VirtualBox VM is already running.

C:\Users\Lydia\atom-vagrant>

I still can't open 10.10.10.10 though, nor can I ssh into it.

[David Juhasz]

Hi Lydia,

Hmm, was the virtual machine running already when you did "vagrant provision"?  I would try shutting down the VM via the Virtualbox interface, then run "vagrant provision" again.  You may not need to run "vagrant up" after provisioning, I can't remember, but it won't hurt to try.  After that try "vagrant ssh" again and see if you can connect to the VM.

Cheers,

David

--

David Juhasz
Director, AtoM Technical Services

Artefactual Systems Inc.
www.artefactual.com

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/e440f3be-0569-4638-8d6a-850139e7e7ae%40googlegroups.com.

[Dan Gillean]

Hi Lydia,

I think I know what's happening - I've run into this myself recently, and figured it out by digging deep in some of Virtualbox's user forums. Close down vagrant and virtualbox first.

It looks like you're trying to do this on a Windows machine? Windows, particularly in newer versions, seems to have this annoying habit of automatically turning off certain adapter settings needed for the Vagrant box to work. You should be able to turn these on via the Network and Sharing Center in windows. You can get there through the Control Panel, or by right-clicking on the connection icon in you tool tray.

When you have the Network and Sharing Center open, click on "Change adapter settings." Find your Virtualbox network adapter connection, and then use the "Change the settings of this connection" option in the header. It will open a menu - make sure the Virtualbox NDIS6 Bridged Networking Driver option is selected, and save your changes.

Now, hopefully, you should be able to boot everything up!

This setting seems to periodically turn off for me - once in a while Windows will decide to create a new Virtualbox Host-only Network, instead of reusing the existing one - and then I have to go enable this setting for the new connection as well. So be sure to check this first if you run into a similar issue again.

And let me know if this works! I captured the above screenshot because I've been thinking about adding a note to our documentation for Windows users. If this does in fact resolve your issue,  I'll try to prioritize doing this soon, so others can avoid this pitfall.

Cheers,

​

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, Feb 18, 2016 at 10:40 AM, <lydia...@alumni.utoronto.ca> wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/e440f3be-0569-4638-8d6a-850139e7e7ae%40googlegroups.com.

[lydia...@alumni.utoronto.ca]

Hi David:

When I tried to run it without the VM running, I got this message:

C:\Users\Lydia\atom-vagrant>vagrant provision

==> default: VM is not currently running. Please, first bring it up with `vagrant up` then run this command.

C:\Users\Lydia\atom-vagrant>

[lydia...@alumni.utoronto.ca]

Hi Dan:

I followed the instructions/screenshot above, and the box for Virtualbox NDIS6 Bridged Networking Driver  was already checked off, so I'm not sure that this is the problem?

[David Juhasz]

Hi Lydia,

Sorry, that's my bad - I haven't provisioned a vagrant box in a while.  From the docs and help file it looks like "vagrant up --provision" is the correct command for provisioning a VM that's not running [https://www.vagrantup.com/docs/provisioning/index.html#vagrant_up].

Cheers,

David

--

David Juhasz
Director, AtoM Technical Services

Artefactual Systems Inc.
www.artefactual.com

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/1fdb14e5-801f-4f76-b474-b34ceaaa3d1f%40googlegroups.com.

[lydia...@alumni.utoronto.ca]

Hi David:

Provisioning didn't seem to have an effect.

By the way, is it okay to use Ubuntu 32-bit? When I load up the VirtualBox, the first screen asks me to confirm Ubuntu 32. Then when I hit "enter", it goes to that black screen.

[Dan Gillean]

Hi Lydia,

The box is apparently built using 64-bit, so it's possible that selecting 32-bit is causing issues. If you've double-checked that all Virtual Box connections have the Virtualbox NDIS6 Bridged Networking Driver option enabled (e.g. that Windows is not creating new ones every time you try to boot, where this is not enabled).... then, hmmm.

I don't think this is specific to the AtoM vagrant box. I've looked at some online forums, searching for your answer. Sounds like many people were able to resolve the issue by either:

• First disabling, and then re-enabling, the Virtualbox NDIS6 Bridged Networking Driver option - so even if it was already on, try disabling it, saving, then re-enabling, saving, and try the Vagrant box again, or:
  
• Updating your version of Virtualbox. Some users who were using 4.3.14 solved it by either downgrading to 4.3.12 or upgrading to 4.3.16; some using 4.3.16 solved it by upgrading to 5.x, etc.
  
• For some users, they had to modify their computer BIOS settings to enable VT-x. I found a post that helps explain how to do this - I've never had to do this myself, so I can't personally recommend it - proceed with caution! http://www.howtogeek.com/213795/how-to-enable-intel-vt-x-in-your-computers-bios-or-uefi-firmware/

In general, if these don't work I'd recommend doing some searching on this error, and/or posting in a Vagrant or Virtualbox forum. This sounds more like a configuration issue than something specific with the AtoM Vagrant box.

Let us know if any of the above 3 solutions work for you!

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/24f6a2f3-013a-4fc3-b191-c4becfc1d1d0%40googlegroups.com.

[David Juhasz]

Hi Lydia,

I'm pretty sure the vagrant box should be Ubuntu 64bit - mine is when I look at it in the Virtualbox control panel.  I haven't run into these problems with vagrant before, so I'm guessing here at the problem, but my best guess at this point is your vagrant box was corrupted by running out of disk space during download. I would try downloading a clean vagrant box with "vagrant box add --clean artefactual/atom"



If doing the "add --clean" doesn't clear the problem up, then I would remove the box altogether and start again. :(



Cheers,


David


--

David Juhasz
Director, AtoM Technical Services

Artefactual Systems Inc.
www.artefactual.com

On Thu, Feb 18, 2016 at 12:21 PM, <lydia...@alumni.utoronto.ca> wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/24f6a2f3-013a-4fc3-b191-c4becfc1d1d0%40googlegroups.com.

[lydia...@alumni.utoronto.ca]

Hi Dan and David:

We were able to get a little further now and the atom-vagrant virtualbox seems to be running. The black screen is now asking me for a "vagrant login." I can't connect to 10.10.10.10

Any idea what should be put into "vagrant login"?

Here is a screenshot:

[Sara Allain]

Hi Lydia,

As per the documentation, the username and password should both be vagrant. Let me know if that doesn't work!

Cheers,

Sara Allain

Systems Archivist

Artefactual Systems, Inc.

[lydia...@alumni.utoronto.ca]

Hi Sara:

The new screen looks good, but I still cannot connect to 10.10.10.10. It says it times out?

Here is what my Virtualbox looks like. Seems promising, but not sure what is stopping the connection to 10.10.10.10?

[Sara Allain]

Hi,

I did a bit of googling and vagrant/virtualbox timeouts can be caused by a lot of things - there are several suggestions on this thread that might be helpful, even though the thread itself is a few years old. Wiping your current install and starting fresh with the settings changes that Dan and David helped you with might be a good place to start. If that doesn't work, it might be best if you sought help on the VirtualBox forums - unfortunately, no one here is a VirtualBox expert and none of our wise developers have any further ideas.

Sorry we couldn't be more help! Best of luck.