2013-09-03 18:08:28 +00:00
|
|
|
---
|
2013-09-06 16:50:43 +00:00
|
|
|
page_title: "Debugging and Troubleshooting"
|
2013-09-03 18:08:28 +00:00
|
|
|
sidebar_current: "debugging"
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Debugging
|
|
|
|
|
|
|
|
|
|
As much as we try to keep Vagrant stable and bug free, it is inevitable
|
|
|
|
|
that issues will arise and Vagrant will behave in unexpected ways. In
|
|
|
|
|
these cases, Vagrant has amazing [support](http://www.vagrantup.com/support.html)
|
|
|
|
|
channels available to assist you.
|
|
|
|
|
|
|
|
|
|
When using these support channels, it is generally helpful to include
|
|
|
|
|
debugging logs along with any error reports. These logs can often help you
|
|
|
|
|
troubleshoot any problems you may be having.
|
|
|
|
|
|
|
|
|
|
To enable detailed logging, set the `VAGRANT_LOG` environmental variable
|
|
|
|
|
to the desired log level name, which is one of `debug` (loud), `info` (normal),
|
|
|
|
|
`warn` (quiet), and `error` (very quiet). When asking for support, please
|
|
|
|
|
set this to `debug`. When troubleshooting your own issues, you should start
|
|
|
|
|
with `info`, which is much quieter, but contains important information
|
|
|
|
|
about the behavior of Vagrant.
|
|
|
|
|
|
|
|
|
|
On Linux and Mac systems, this can be done by prepending the `vagrant`
|
|
|
|
|
command with an environmental variable declaration:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
$ VAGRANT_LOG=info vagrant up
|
|
|
|
|
...
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
On Windows, multiple steps are required:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
$ set VAGRANT_LOG=info
|
|
|
|
|
$ vagrant up
|
|
|
|
|
...
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
If you plan on submitting a bug report, please submit debug-level logs
|
|
|
|
|
along with the report using [gist](https://gist.github.com/) or
|
|
|
|
|
some other paste service.
|
