Table of Contents

Troubleshooting

Resource Manager provides you with methods for evaluating and troubleshooting problems.

The following sections are presented in this chapter:

• Error Message Format
  
  
• Process Status Features
  
  
• Troubleshooting a Process Problem
  
  

Error Message Format

Resource Manager displays two types of error messages:

• Interface error messages
  
  
• Back-end error messages stored in the syslog
  
  

Interface error messages are displayed in dialog boxes with descriptions of the probable causes and recommended corrective actions, if any. (See Figure 9-1.)

There are three types of interface error messages:

• USER—Indicates a user error or invalid input.
  
  
• SYSTEM—Indicates a system failure.
  
  
• INTERNAL—Indicates a product code issue.
  
  

Some interface error messages include a Details button. (See Figure 9-2.)

Click Details for additional information and recommended corrective action. An informational dialog box appears. (See Figure 9-3.)

Back-end error messages result from problems that occur in processes running on the Resource Manager server. Back-end error messages are stored in the syslog.

Refer to the appropriate Cisco Resource Manager Installation Guide for the location of the error message logs.

Figure 9-4 shows the syslog error message format.

Process Status Features

There are two interfaces for viewing and troubleshooting process problems:

• The Resource Manager interface
  
  
• The command-line interface
  
  

Use the Process Status, Start Process, and Stop Process features in the Resource Manager interface to view process status and troubleshoot process problems. Use the command-line interface for processes that cannot be monitored with the Resource Manager interface (for example, syslogd).

Table 9-1 shows the process features available in the Resource Manager interface and the equivalent command-line process features.

For a complete description of the Resource Manager interface processes, refer to the online help.

Process Failures

Several events can cause a process to fail. For example, the database engine might fail for one of the following reasons:

• On Solaris systems, the database uses a small amount of space in the /tmp file system. If this space fills up, the database can no longer accept connections from client code and therefore fails.
  
  
• The file system containing the database file is full.
  
  

If a Resource Manager process fails, examine your system to see whether any of these conditions or others have occurred and attempt to correct them.

Error Messages

Refer to the appropriateCisco Resource Manager Installation Guide for the location of the error message logs.

If you cannot solve a process problem, call Cisco Customer Service. Refer to the error log files to provide Customer Service with the information they need to help you solve the problem.

Troubleshooting a Process Problem

The following sections describe scenarios in which both the Resource Manager interface and command-line interface process features are used:

• Starting a Process
  
  
• Stopping a Process
  
  

Starting a Process

Scenario: You check process status and notice the DbServer process in the Process Status table indicates a state of "Failed to run." You attempt to restart the process.

Resource Manager Interface

To attempt a process restart, perform the following steps:

Step 1  
Log in with administrator privileges.

Step 2   Click Admin on the button bar, then select System Admin > Process Status.

The Process Status report appears showing the message "Failed to start."

Step 3   Select System Admin > Start Process.

The Start Process dialog box appears. (See Figure 9-5.)

Step 4   Click Process, select DbServer in the Process Name drop-down list, then click Finish.

The Process Status table appears.

Step 5   Check whether the process is now running properly.

If the status now reads "Running normally," you have solved the problem.

Step 6   If the process is still not running normally, call Cisco Customer Service for assistance. Customer Service will need to know the error log information to help you solve the problem.

Command-line Interface

To attempt a process restart, perform the following steps:

Step 1  
To check status, enter pdshow DbServer.

The following message appears:

Process= DbServer
State  = Failed to run
Pid    = 0
RC     = 0
Signo  = 0
Start  = 19:16:15 06/02/1997
Stop   = 11:28:40 06/03/1997
Core   = Not applicable
Info   = Application failed, or was registered incorrectly.
 

Step 2   Enter pdexec DbServer to attempt to restart the process.

Step 3   Enter pdshow DbServer again to see whether the process is operating properly.

If the process is operating properly, the following message appears:

Process= DbServer
State  = Running normally
Pid    = 21473
RC     = 0
Signo  = 0
Start  = 19:16:15 06/02/1997
Stop   = Not applicable
Core   = Not applicable
Info   = Data server (dbeng50) invoked.
 

Step 4   If the process is still not running normally, check the error log. If you cannot solve the problem, call Cisco Customer Service for assistance. Customer Service will need to know the error log information to help you solve the problem.

Stopping a Process

Scenario: You want to back up all the data you have stored on your hard drive, so you shut down the DbServer process.

Resource Manager Interface

To stop the DbServer process, perform the following steps:

Step 1  
Log in with administrator privileges.

Step 2   Click Admin on the button bar, then select System Admin > Stop Process.

The Stop Process dialog box appears. (See Figure 9-6.)

Step 3   Click the Process radio button.

Step 4   Select DbServer from the Process Name list, then click Finish.

The process stops and the Process Status table appears, displaying the message "Administrator has shut down this server."

Command-line Interface

To stop the DbServer process, perform the following steps:

Step 1  
Log in with administrator privileges.

Step 2   Enter pdterm DbServer.

Step 3   To check process status, enter pdshow DbServer.

The following status message appears, showing that the process has been stopped.

Process= DbServer
State  = Administrator has shut down this server
Pid    = 0
RC     = 0
Signo  = 0
Start  = 19:16:15 06/02/97
Stop   = 11:27:05 06/03/97
Core   = Not applicable
Info   = Not applicable