Hitachi

JP1 Version 11 JP1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference


13.2 Troubleshooting

This section explains how to conduct troubleshooting while you are using Performance Management products. When an error occurs while you are using a Performance Management product, you should first check to see if any of the events described in this section have occurred.

The following table lists the principal types of errors that may occur while you are using a Performance Management product.

Table 13‒1: Error types

Classification

Nature of problem

Section

Setting up or starting a service

  • A Performance Management program service does not start.

  • It takes a long time for a service to start after startup is requested.

  • Another program service is started immediately after a Performance Management program service has stopped, but communication is not performed correctly.

  • The Master Store or Agent Store service stops after display of the message The disk capacity is insufficient.

  • The Agent Collector service of PFM - Agent does not start.

See the chapter that explains troubleshooting in the JP1/Performance Management User's Guide.

Executing commands

  • When the jpctool service list command is executed, the names of services that are not operating are output.

  • When the jpctool db dump command is executed, data other than the specified Store data is output.

Report definitions

  • Information for some period of time is not displayed in historical reports.

Alarm definitions

  • The program defined for action execution does not function correctly.

  • Alarm events are not displayed.

Collecting and managing performance data

  • The size of the PFM - Agent's Store database is not reduced even though the data retention period was shortened.

  • The message Illegal data was detected in the Store database is output to the common message log.

Measuring Web transactions

  • No Web transaction file is found

  • The user does not have access permissions to the Web transaction file

  • The Web transaction file contains a format error

  • The Web transaction file contains a definition error

  • The transaction specified in the Web transaction file does not exist

  • The monitored machine is not operating (or communications do not reach it)

  • The Web service (such as Apache HTTP Server) is not running

  • The resource specified in the URL does not exist (an HTTP 404 error occurs)

  • Invalid certificate (self-signed certificate)

  • A basic authentication error (missing password) occurs

  • A basic authentication error (incorrect password) occurs

  • A response determination error occurs

  • An option specification error occurs during measurement test command execution

  • A duplicate command execution error occurs during measurement test command execution

13.2.1

For details about error handling in PFM - Agent for Service Response, see 13.8 Error handling procedure for each problem.

Organization of this section