vagrant box add fails with cygwin on windows

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

vagrant box add fails with cygwin on windows

David Reed
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.


Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

John Barney
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Mitchell Hashimoto
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

John Barney
https://gist.github.com/johnb0011/4733013

On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="MlHaRkrjzycJ">john...@...> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="MlHaRkrjzycJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Mitchell Hashimoto
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

John Barney
That idea worked like a charm. I've added a pull request here:

https://github.com/mitchellh/vagrant/pull/1366

On Thursday, February 7, 2013 6:23:02 PM UTC-8, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="4DOr7_aq0tMJ">john...@...> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="4DOr7_aq0tMJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Christopher Hopper
In reply to this post by Mitchell Hashimoto
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

# vagrant box add centos-6.3-64bit http://packages.vstone.eu/vagrant-boxes/centos/6.3/centos-6.3-64bit-puppet-vbox.4.2.4.box
Downloading with Vagrant::Downloaders::HTTP...
Downloading box: http://packages.vstone.eu/vagrant-boxes/centos/6.3/centos-6.3-64bit-puppet-vbox.4.2.4.box
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="4DOr7_aq0tMJ">john...@...> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="4DOr7_aq0tMJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Mitchell Hashimoto
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Hans K
Same problem under Cygwin.  Here's the gist:

https://gist.github.com/hanskellner/5192870

On Monday, March 18, 2013 6:15:24 PM UTC-7, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="m7GMy7Etc3YJ">christophe...@gmail.com> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="m7GMy7Etc3YJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Christopher Hopper
In reply to this post by Mitchell Hashimoto
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log

https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6 

Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="m7GMy7Etc3YJ">christophe...@gmail.com> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="m7GMy7Etc3YJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Ben Hirsch
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Samuel Brown
I'm experiencing the same issue using Git Bash with Vagrant v1.1.2 on Win7.  

On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Stephen Brown II
In reply to this post by Ben Hirsch
Another Me-too, with both 1.1.1 and 1.1.2.

here's my gist: https://gist.github.com/StephenBrown2/5205828

Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Christopher Hopper
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Stephen Brown II
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen


On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Mitchell Hashimoto
Chris or Stephen,

I think the issue has been fixed. Can you try modifying your Vagrant bash file that is being executed with these changes to see if the issue is fixed:


Best,
Mitchell


On Wed, Mar 20, 2013 at 7:02 PM, Stephen Brown II <[hidden email]> wrote:
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen



On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Stephen Brown II
Thanks! That worked for me, though I simply put the export line in the existing if [ "${OS}" = "Cygwin" ]; block. You won't be needing that PATH if @operatingsystem != "windows", and I don't like unnecessary code blocks. :-p



On Thursday, March 21, 2013 1:27:34 AM UTC-4, Mitchell Hashimoto wrote:
Chris or Stephen,

I think the issue has been fixed. Can you try modifying your Vagrant bash file that is being executed with these changes to see if the issue is fixed:


Best,
Mitchell


On Wed, Mar 20, 2013 at 7:02 PM, Stephen Brown II <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="IjKPh7GHqwsJ">stephen...@...> wrote:
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen



On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="IjKPh7GHqwsJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Mitchell Hashimoto
Stephen

Heh, I actually want to just get rid of the erb block if I can. That means I should detect msys too I suppose.

Mitchell


On Thu, Mar 21, 2013 at 6:45 AM, Stephen Brown II <[hidden email]> wrote:
Thanks! That worked for me, though I simply put the export line in the existing if [ "${OS}" = "Cygwin" ]; block. You won't be needing that PATH if @operatingsystem != "windows", and I don't like unnecessary code blocks. :-p



On Thursday, March 21, 2013 1:27:34 AM UTC-4, Mitchell Hashimoto wrote:
Chris or Stephen,

I think the issue has been fixed. Can you try modifying your Vagrant bash file that is being executed with these changes to see if the issue is fixed:


Best,
Mitchell


On Wed, Mar 20, 2013 at 7:02 PM, Stephen Brown II <[hidden email]> wrote:
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen



On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

Stephen Brown II
Heh, well in that case yeah. I believe Git Bash uses mingw32, might want to check for that too.

On Thursday, March 21, 2013 12:21:41 PM UTC-4, Mitchell Hashimoto wrote:
Stephen

Heh, I actually want to just get rid of the erb block if I can. That means I should detect msys too I suppose.

Mitchell


On Thu, Mar 21, 2013 at 6:45 AM, Stephen Brown II <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="0ww0hEu8eckJ">stephen...@...> wrote:
Thanks! That worked for me, though I simply put the export line in the existing if [ "${OS}" = "Cygwin" ]; block. You won't be needing that PATH if @operatingsystem != "windows", and I don't like unnecessary code blocks. :-p



On Thursday, March 21, 2013 1:27:34 AM UTC-4, Mitchell Hashimoto wrote:
Chris or Stephen,

I think the issue has been fixed. Can you try modifying your Vagrant bash file that is being executed with these changes to see if the issue is fixed:


Best,
Mitchell


On Wed, Mar 20, 2013 at 7:02 PM, Stephen Brown II <[hidden email]> wrote:
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen



On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="0ww0hEu8eckJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: vagrant box add fails with cygwin on windows

wenlock
Yep, it does.  Uses a different variation of uname as well.

Thanks,
Edward

On Thursday, March 21, 2013 12:45:27 PM UTC-7, Stephen Brown II wrote:
Heh, well in that case yeah. I believe Git Bash uses mingw32, might want to check for that too.

On Thursday, March 21, 2013 12:21:41 PM UTC-4, Mitchell Hashimoto wrote:
Stephen

Heh, I actually want to just get rid of the erb block if I can. That means I should detect msys too I suppose.

Mitchell


On Thu, Mar 21, 2013 at 6:45 AM, Stephen Brown II <[hidden email]> wrote:
Thanks! That worked for me, though I simply put the export line in the existing if [ "${OS}" = "Cygwin" ]; block. You won't be needing that PATH if @operatingsystem != "windows", and I don't like unnecessary code blocks. :-p



On Thursday, March 21, 2013 1:27:34 AM UTC-4, Mitchell Hashimoto wrote:
Chris or Stephen,

I think the issue has been fixed. Can you try modifying your Vagrant bash file that is being executed with these changes to see if the issue is fixed:


Best,
Mitchell


On Wed, Mar 20, 2013 at 7:02 PM, Stephen Brown II <[hidden email]> wrote:
Silly me, expecting 'set' to work in Cygwin.

I've updated my gist with the proper output: https://gist.github.com/StephenBrown2/5205828

And on a cursory glance, it looks like it can't find the actual box file after it extracts it? But I could be mistaken.

Thanks,
Stephen



On Wednesday, March 20, 2013 6:26:19 PM UTC-4, Christopher Hopper wrote:
Stephen,

Which environment are you in, Cygwin or a Windows cmd.exe prompt?

To set the Vagrant debug flag for Cygwin bash, use the Linux method like this:

# export VAGRANT_LOG=debug

To set the Vagrant debug flag for a Windows cmd.exe or MS-DOS prompt, use the the SET command. 

> SET VAGRANT_LOG=debug

To save the Vagrant debug output to a file, in Cygwin, pipe the output of STDERR to a file pointer like this:

# vagrant list 2> ~/vagrant-debug.log

Christopher.

On Thursday, 21 March 2013 03:09:37 UTC+11, Stephen Brown II wrote:
Another Me-too, with both 1.1.1 and 1.1.2.


Though setting VAGRANT_LOG=debug or DEBUG doesn't appear to affect the output, like with https://gist.github.com/chopp3r/7e52512f976f0c1fb4a6


On Monday, March 18, 2013 10:04:53 PM UTC-4, Ben Hirsch wrote:
I am getting the same error in cygwin.

On Monday, March 18, 2013 9:35:58 PM UTC-4, Christopher Hopper wrote:
Thanks for the quick reply, as usual, Mitchell.

Here's the stderr output from the command:

# export VAGRANT_LOG=debug
# vagrant box add precise64 http://files.vagrantup.com/precise64.box 2> ~/vagrant-box-add.debug.log


Let me know how I can help with the debug.

Christopher.

On Tuesday, 19 March 2013 12:15:24 UTC+11, Mitchell Hashimoto wrote:
Christopher,

> set VAGRANT_LOG=debug

Then run the command. Please gist the output.

I have an idea what it is already though... but lets see the log.

Best,
Mitchell


On Mon, Mar 18, 2013 at 6:13 PM, Christopher Hopper <[hidden email]> wrote:
I'm having a similar issue to the one described, using vagrant box add in Cygwin. Can you tell me how to get a debug level log output so I can find out what is wrong and suggest a fix?

Here's the output of my vagrant box add call:

Downloading with Vagrant::Downloaders::HTTP...
Extracting box...8674312 / 398734848)
Cleaning up downloaded box...
C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:81:in `rescue in execute': The system cannot find the file specified. (2) (Vagrant::Util::Subprocess::LaunchError)
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:74:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/subprocess.rb:20:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:104:in `block in add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/box_collection.rb:99:in `add'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builtin/box_add.rb:35:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/warden.rb:34:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/builder.rb:109:in `call'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `block in run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/util/busy.rb:19:in `busy'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/action/runner.rb:61:in `run'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/add.rb:33:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/plugins/commands/box/command/root.rb:47:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/cli.rb:46:in `execute'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/lib/vagrant/environment.rb:406:in `cli'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/gems/vagrant-1.1.0/bin/vagrant:60:in `<top (required)>'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `load'
        from C:/Users/Public/development/provisioning/vagrant/embedded/gems/bin/vagrant:23:in `<main>'

Thanks,
Christopher.


On Friday, 8 February 2013 13:23:02 UTC+11, Mitchell Hashimoto wrote:
John,

Ah hah, I see the issue: 

 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/jbarney/.vagrant.d/boxes/precise64/box.ovf", "--dry-run"]

VBoxManage isn't a cygwin application so I need to call `cygpath` on it or something.

I'll look into this.

Best
Mitchell


On Thu, Feb 7, 2013 at 10:26 AM, John Barney <[hidden email]> wrote:
https://gist.github.com/johnb0011/4733013


On Thursday, February 7, 2013 8:25:08 AM UTC-8, Mitchell Hashimoto wrote:
John,

Can you get "DEBUG" level logs and gist them and post them here?

Best,
Mitchell


On Thu, Feb 7, 2013 at 2:40 AM, John Barney <[hidden email]> wrote:
I thought it might be helpful to show debug logs as I am hitting the same problem:

INFO interface: info: Progress: 99% (444825289 / 444832256)

 INFO warden: Calling action: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO interface: info: Extracting box...
[vagrant] Extracting box...
 INFO warden: Calling action: #<Vagrant::Action::Box::Verify:0x8050d6d0>
 INFO interface: info: Verifying box...
[vagrant] Verifying box...
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "--version"]
 INFO virtualbox: Using VirtualBox driver: Vagrant::Driver::VirtualBox_4_2
 INFO virtualbox_base: VBoxManage path: VBoxManage
 INFO subprocess: Starting process: ["VBoxManage", "import", "/home/John Barney/.vagrant.d/boxes/Berkshelf-CentOS-6.3-x86_64-minimal.box/box.ovf", "--dry-run"]
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
 INFO warden: Calling recover: #<Vagrant::Action::Box::Unpackage:0x8050d734>
 INFO warden: Calling recover: #<Vagrant::Action::Box::Download:0x80b01140>
 INFO interface: info: Cleaning up downloaded box...
[vagrant] Cleaning up downloaded box...
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR warden: Error occurred: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxVerificationFailed: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.>
ERROR vagrant: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
ERROR vagrant: /usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/verify.rb:15:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/unpackage.rb:30:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/box/download.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/general/check_virtualbox.rb:23:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/warden.rb:33:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/builder.rb:92:in `call'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `block in run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/util/busy.rb:19:in `busy'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/action/runner.rb:49:in `run'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/box_collection.rb:38:in `add'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box_add.rb:30:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/command/box.rb:31:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/cli.rb:42:in `execute'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:167:in `cli'
/usr/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:43:in `<top (required)>'
/usr/bin/vagrant:23:in `load'
/usr/bin/vagrant:23:in `<main>'
 INFO interface: error: The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

On Friday, February 1, 2013 6:46:23 PM UTC-8, David Reed wrote:
I'm trying to get vagrant running in Cygwin so I can use a decent
windows command line to boot a better operating system for
development. However I've tried adding some boxes and the ones I've
tried report the box as being invalid.

It seems (from the DEBUG logging) to be failing on the 'VBoxMange
import ~/.vagrant.d/boxes/precise64/box.ovf --dry-run'

Can anyone suggest what is wrong and/or how to fix the problem?

Original output
----

$ vagrant box add precise64 http://files.vagrantup.com/precise64.box
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://files.vagrantup.com/precise64.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
The box file you're attempting to add is invalid. This can be
commonly attributed to typos in the path given to the box add
command. Another common case of this is invalid packaging of the
box itself.

System Info
---

$ ruby --version
ruby 1.9.3p374 (2013-01-15 revision 38858) [i386-cygwin]

$ vagrant --version
Vagrant version 1.0.6

$ VBoxManage.exe --version
4.0.8r71778

$ uname
CYGWIN_NT-6.1-WOW64

$ systeminfo.exe | findstr.exe /B /C:"OS Name" /C:"OS Version"
OS Name:                   Microsoft Windows 7 Home Premium
OS Version:                6.1.7601 Service Pack 1 Build 7601

Detailed output
---
[Attached]

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
12