Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Report > Audit Entries > Actions > Basic Troubleshooting using Audit Entries

Basic Troubleshooting using Audit Entries

Objective

Use the Audit Entries to learn the mechanics and basic process for standard troubleshooting efforts.

 

Table of Contents

Prerequisites

Completion of the Audit Entries tutorial from the Reports section of the the Dashboard Users Guide.

Background

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.

Steps

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.

  1. Import the “Mephisto all-in-one” ServerTemplate from the MultiCloud Marketplace
  2. Add a Server to an existing Deployment using the imported “Mephisto all-in-one” ServerTemplate.
  3. Launch the Server
  4. Before you confirm the Server launch, change the value for the ‘SVN_APP_REPOSITORY’ Input. Enter a bogus value (e.g. blah-blah) and click Launch.
  5. After a few minutes, the Server will become “stranded” because the Server will not be able to find and download the web application.
  6. Click on the Audit Entries tab (or you can click the link in the Events pane).
  7. Click on the ‘stranded’ link to view more detailed information about the error.
  8. Next, you’ll see the detailed audit entry. Scroll down to the bottom and expand the details of the action that failed.

 

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.

 

You must to post a comment.
Last modified
22:50, 16 May 2013

Tags

Classifications

This page has no classifications.

Announcements

None


© 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.