Use the Audit Entries to learn the mechanics and basic process for standard troubleshooting efforts.
Table of Contents
After obtaining a fundamental understanding of what Audit Entries are and how to view them, this tutorial manufacturers a fairly common glitch while launching a Server, and follows the Audit Entries as part of a basic troubleshooting effort. It is important to get the basic mechanics down first. Specific troubleshooting and debugging is tied to your Deployment configuration, application information, database, etc.
To demonstrate how you can use Audit Entries for troubleshooting purposes, the following steps will lead you through a common troubleshooting scenario—a “stranded” Server. In the first part of the tutorial, you will purposely strand a Server by modifying one of its Input parameters. In the second part, you will demonstrate how to use the audit entries to help diagnose the cause of the problem.
You should see entries that worked ok, and eventually one that fails. Does it align with what you expected to see? This is a fairly basic example, but it's a very common mistake. Entering an improper Input value is usually one of the main reasons why a Server will become stranded. It's important to realize that one of the first places you should look when you experience problems stranded servers or scripts that failed to run properly is the Audit Entries. Understanding how to read Audit Entries will be a critical part of any troubleshooting effort.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.