Hello Gerard.

If you are in windows, the command should be:

set VAGRANT_LOG=debug

not the capital

then when you run vagrant up will generate logs of log in the command line, is 
not that will generate a file

For Windows, check this package is installed:
https://www.microsoft.com/en-nz/download/details.aspx?id=5555 
<https://www.microsoft.com/en-nz/download/details.aspx?id=5555>

Then, the best way to troubleshoot is in the following order:

mkdir precise32
cd precise32
vagrant init -m hashicorp/precise32
vagrant up

If this VM fails, then the best will be reinstall virtualbox and vagrant, and 
reboot.

If this command works, then test a 64 bit box is the next step

cd ..
mkdir precise64
cd precise64
vagrant init -m hashicorp/precise64
vagrant up

If this command fails, the best is open Virtualbox, stop and star the VM here 
and see what the message is.


Let me know how you go with those 2 test.

Alvaro.


> On 12/03/2016, at 11:05 PM, Gerard Green <[email protected]> wrote:
> 
> Hello.
> 
> I am unable to SSH into my vagrant installation due to an SSH error. I want 
> to create a log file that I can post and ask for support on how to resolve 
> this issue.
> I need to understand what commands to use in a windows 7 command prompt 
> window to get the log to go to a file rather than just displaying on the 
> screen.
> I currently use these commands:
>  
> set vagrant_log=debug
> set stderr=vagrant.log
> vagrant up
> 
> I am unable to locate the vagrant.log file anywhere.
> 
> Can someone please provide suitable vagrant commands to create a log file of 
> my vagrant up command? Thanks.
> 
> 
> 
> -- 
> This mailing list is governed under the HashiCorp Community Guidelines - 
> https://www.hashicorp.com/community-guidelines.html 
> <https://www.hashicorp.com/community-guidelines.html>. Behavior in violation 
> of those guidelines may result in your removal from this mailing list.
>  
> GitHub Issues: https://github.com/mitchellh/vagrant/issues 
> <https://github.com/mitchellh/vagrant/issues>
> IRC: #vagrant on Freenode
> --- 
> 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 [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-up/80d93568-83a1-4960-b774-405d54cd9e6c%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/vagrant-up/80d93568-83a1-4960-b774-405d54cd9e6c%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/C8059C0D-D383-46F1-884E-4CB50A714C79%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to