github.com/aspring/packer@v0.8.1-0.20150629211158-9db281ac0f89/website/source/docs/other/debugging.html.markdown (about) 1 --- 2 layout: "docs" 3 page_title: "Debugging Packer" 4 description: |- 5 Packer strives to be stable and bug-free, but issues inevitably arise where certain things may not work entirely correctly, or may not appear to work correctly. In these cases, it is sometimes helpful to see more details about what Packer is actually doing. 6 --- 7 8 # Debugging Packer 9 10 Packer strives to be stable and bug-free, but issues inevitably arise where 11 certain things may not work entirely correctly, or may not appear to work 12 correctly. In these cases, it is sometimes helpful to see more details about 13 what Packer is actually doing. 14 15 Packer has detailed logs which can be enabled by setting the `PACKER_LOG` 16 environmental variable to any value. This will cause detailed logs to appear 17 on stderr. The logs contain log messages from Packer as well as any plugins 18 that are being used. Log messages from plugins are prefixed by their application 19 name. 20 21 Note that because Packer is highly parallelized, log messages sometimes 22 appear out of order, especially with respect to plugins. In this case, 23 it is important to pay attention to the timestamp of the log messages 24 to determine order. 25 26 In addition to simply enabling the log, you can set `PACKER_LOG_PATH` in order 27 to force the log to always go to a specific file when logging is enabled. 28 Note that even when `PACKER_LOG_PATH` is set, `PACKER_LOG` must be set in 29 order for any logging to be enabled. 30 31 If you find a bug with Packer, please include the detailed log by using 32 a service such as [gist](http://gist.github.com).