Job Management Partner 1/Performance Management - Agent Option for Platform Description, User's Guide and Reference

8.2.1 Setting up or starting a service

This section explains how to handle errors related to setup and service startup.

Organization of this subsection

(1) Performance Management program service does not start

(2) It takes a long time between a service startup request and the actual service startup

(3) When another program begins a service immediately after a Performance Management program service has been stopped, communication cannot be correctly executed

(4) After the message "The disk capacity is insufficient." is issued, the Master Store service or Agent Store service stops

(1) Performance Management program service does not start

The possible causes and how to handle them are described below.

PFM - Manager is stopped
When PFM - Manager and PFM - Agent are on the same host, if PFM - Manager is stopped, the PFM - Agent service cannot start. Make sure the PFM - Manager service is running. If the PFM - Manager service is not running, start it. For details about how to start a service, see the chapter explaining how to start and stop Performance Management in the manual Job Management Partner 1/Performance Management User's Guide.

The same port number is specified for multiple services of a Performance Management program
If the same port number is specified for multiple services of a Performance Management program, the service of the Performance Management program cannot start. By default, port numbers are automatically assigned, and thus no duplication occurs. If you specified a fixed port number for the service of a Performance Management program when setting up Performance Management, check the port number settings. If the same port number is specified for multiple services of a Performance Management program, specify different port numbers. For details about how to specify port numbers, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

A directory specified for storing the Store database is invalid
If any of the directories listed below is specified in an inaccessible or nonexistent directory, the Agent Store service cannot start. Check the directory name and attributes and correct them if necessary.

Store database storage destination directory

Store database backup directory

Store database partial backup directory

Store database export destination directory

Store database import destination directory

If any of these directories is specified for multiple Agent Store services, the Agent Store services cannot start. Check the directory settings and correct them if necessary.

The machine's host name was modified using a method other than the specified method
For details about how to change a machine's host name, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide. If the machine's host name is modified using a method other than the specified method, the service of a Performance Management program may not start in some cases.

(2) It takes a long time between a service startup request and the actual service startup

It may take a long time after the jpcpm start (jpcstart) command is executed or a service is started using the Service icon before the service actually starts. If the startup takes a long time because of any of the causes listed below, the time it takes for the service startup is shortened during subsequent service startup operations.

If you start a service in stand-alone mode, service startup may take a long time.

If a service is started by restarting the system without specifying that the service be automatically stopped when the system is stopped, the Store database index may be rebuilt. In this case, service startup may take a long time.

When the service is started after a new agent is added, the Store database index is created only during the initial startup. As a result, service startup may take a long time.

If the Store service cannot be terminated normally because of a power failure, for example, the Store database index is rebuilt during a restart, and as a result, service startup may take a long time.

(3) When another program begins a service immediately after a Performance Management program service has been stopped, communication cannot be correctly executed

Immediately after a Performance Management program service has been stopped, if the port number that was used by this service is used by another program to start a service, communication may not be correctly executed. To avoid this condition, specify one of the following:

Specify fixed port numbers for assignment to the services of the Performance Management program.
Assign fixed port numbers for the individual services of the Performance Management program. For details about how to specify port numbers, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

Specify the TCP_TIMEWAIT value
Use the TCP_TIMEWAIT value to set the connection waiting time.
On HP-UX and AIX, specify as follows to set the connection waiting time to be at least 75 seconds:

HP-UX: tcp_time_wait_interval:240000

AIX: tcp_timewait:5

For Windows and Solaris, use the default (4 minutes) setting.
For Linux, the default connection waiting time (60 seconds) cannot be changed. Specify fixed port numbers for assignment to the services of the Performance Management program.

(4) After the message "The disk capacity is insufficient." is issued, the Master Store service or Agent Store service stops

If the disk used by the Store database does not have sufficient free space, storing of data in the Store database is halted. In this case, the message The disk capacity is insufficient. is issued and the Master Store service or Agent Store service stops.

When this message is issued, take one of the following steps:

Allocate sufficient disk capacity
Estimate the disk space requirement for the Store database, and change the Store database storage destination to a disk that has sufficient capacity. For details about how to estimate the disk space requirement for the Store database, see A. Estimating System Requirements. For details about how to change the Store database storage destination, see 2.4 Changing the operation of PFM - Agent for Platform.

Change the saving conditions for the Store database
Change the saving conditions for the Store database and adjust the upper limit for the data volume in the Store database. For details about how to change the saving conditions for the Store database, see the chapter explaining management of operation monitoring data in the manual Job Management Partner 1/Performance Management User's Guide.

If the Master Store service or Agent Store service still does not start even after one of these steps has been taken, an unrecoverable logical conflict has occurred in the Store database. In this case, first restore the Store database from backup data and then start the Master Store service or Agent Store service. If there is no available backup data, first initialize the Store database and then start the Master Store service or Agent Store service. To initialize the Store database, delete all of the following files, which are located in the Store database destination directory:

Files with the extension .DB

Files with the extension .IDX

For details about the Store database destination directory, see the chapter explaining installation and setup in the manual Job Management Partner 1/Performance Management Planning and Configuration Guide.

[Contents][Back][Next]

[Trademarks]