Appendix C. Troubleshooting and Debugging
While thousands of companies and many more thousands of individuals worldwide use Vagrant everyday and praise Vagrant for being stable, there are issues that come up here and there. Vagrant is a complex software package built up of many moving pieces, so while we strive for perfection, this is hopefully understandable.
Luckily, there are multiple resources available for getting help.
When using any of the available Vagrant support resources, have a debug log ready showing the problem you may be running into. The debug log can be enabled by setting the
VAGRANT_LOG environmental variable to
debug. This will cause the output from Vagrant to be extremely loud. Copy this output and paste it into any code sharing website, such as a Gist.
If you feel confident in attempting to solve the problem yourself prior to asking for help, you can also tweak the debug log to be slightly less loud to try to identify errors. The
info level is usually best to get started.
On Linux systems, the environmental variable can be set by prepending Vagrant commands with it:
$ VAGRANT_LOG=debug vagrant up ...
On Windows systems, you must use
set to set the environmental variable prior to running Vagrant commands:
> set VAGRANT_LOG=debug > vagrant up ...
Internet Relay Chat (IRC) is a protocol for live chat messaging with a group of people. Vagrant has an active IRC channel with hundreds of users. You can often get a response to your issues by chatting in the IRC channel. ...