There is an error when executing 'vagrant up'

[seifer08ms]

There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/seifer_08ms/.vagrant.d/boxes/trusty64/0/virtualbox/box.ovf", "--vsys", "0", "--vmname", "ubuntu-cloudimg-trusty-vagrant-amd64_1470816792537_67264", "--vsys", "0", "--unit", "6", "--disk", "/home/seifer_08ms/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1470816792537_67264/box-disk1.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/seifer_08ms/.vagrant.d/boxes/trusty64/0/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/home/seifer_08ms/VirtualBox VMs/ubuntu-cloudimg-trusty-vagrant-amd64_1470816792537_67264/box-disk1.vmdk'.
VBoxManage: error: VMDK: Compressed image is corrupted '/home/seifer_08ms/.vagrant.d/boxes/trusty64/0/virtualbox/box-disk1.vmdk' (VERR_ZIP_CORRUPTED)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 877 of file VBoxManageAppliance.cpp

[DruidSmith]

Looking into it - I originally built this using the 'trusty64' image - I just tried launching it now and vagrant came back and said "trusty64 could not be found' and then seems to be defaulting to what it says is a current trusty image. It may be that vagrant's trusty image is bad, but hopefully not.

[DruidSmith]

Ahhh... looks like it failed for me also, though I ended up with a different issue. Wondering if it's an issue with the trusty image on vagrant's server or alternatively, I found this blog post which suggests there may be a vagrant versioning thing as well - http://bradjr.info/posts/vagrant-error-finding-ubuntu-trusty64 Sorry I don't have a quick answer, will have to do a bit more digging. I will look at updating my version of vagrant and will try to rebuild the vagrant files as needed.

[seifer08ms]

Well, I tried "ubuntu/trusty64". It works fine for me with VirtualBox 5.0.26 and Vagrant 1.8.5 . I guess upgrading vagrant maybe the easiest solution.

[seifer08ms]

Another issue is about port forwarding.
When I tried vagrant up with 'ubuntu/trusty64', I have an another error :
"Vagrant cannot forward the specified ports on this VM, since they would collide with some other application that is already listening on these ports. The forwarded port to 8080 is already in use on the host machine."
There is postgres installed in my host ,but I can not find any program listening 8080 port in my host.
It seems that I must use different ports between guest and host. I have to change port manually or just adding "auto_correct: true" in the end of lines .

[DruidSmith]

I think I have the base box working now - along with upgrading to Geoserver 2.9.1 and openjdk 8 - though I haven't done anything where it comes to the port. If you don't think you have anything running on 8080 might it be possible there's more than one instance of the vagrant box running? You can check via virtualbox.

[seifer08ms]

Thanks a lot for taking a look at this. I'll certainly have a try with it.

[DruidSmith]

If you need to forward the default Geoserver 8080 port to another port on your host you could try modifying the vagrantfile entry:

config.vm.network "forwarded_port", guest: 8080, host: 8080

change host value from 8080 to desired port -

I haven't yet tried that but it may work...

[seifer08ms]

It works when I changed port or just adding "auto_correct: true" in the end of the lines . But It's wired I haven't found any running instance of vbox,vagrant and any listening 8080 port programs.