github.com/askholme/packer@v0.7.2-0.20140924152349-70d9566a6852/website/source/docs/other/debugging.html.markdown (about)

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