Debugging and Troubleshooting Guide
Important
The AWS OpsWorks Stacks service reached end of life on May 26, 2024 and has been disabled for both new and existing customers.
We strongly recommend customers migrate their workloads to other solutions as soon as possible. If you have questions about migration, reach out to the AWS Support Team on AWS re:Post
If you need to debug a recipe or troubleshoot a service issue, the best approach generally is to work through the following steps, in order:
-
Check Common Debugging and Troubleshooting Issues for your specific issue.
-
Search the AWS OpsWorks Stacks Forum
to see if the issue has been discussed there. The Forum includes many experienced users and is monitored by the AWS OpsWorks Stacks team.
-
For issues with recipes, see Debugging Recipes.
-
Contact AWS OpsWorks Stacks support or post your issue on the AWS OpsWorks Stacks Forum
.
The following section provides guidance for debugging recipes. The final section describes common debugging and troubleshooting issues and their solutions.
Note
Each Chef run produces a log, which provides a detailed description of the run and is
a valuable troubleshooting resource. To specify the amount of detail in the log, add a
Chef::Log.level:info. The following example
shows how to set the Chef log level to :debug, which provides the most
detailed description of the run.
Chef::Log.level = :debug
For more information about viewing and interpreting Chef logs, see Chef Logs.
