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

[Contents][Glossary][Index][Back][Next]


7.2.1 Setting up or starting services

This subsection describes how to handle problems that are related to service setup or service startup.

Organization of this subsection
(1) A Performance Management program service does not start
(2) It takes too long for a service to start once startup is requested
(3) Communication is not performed properly when a program service starts immediately after a Performance Management program service has stopped
(4) The message "The disk capacity is insufficient" is displayed, and then the Master Store service or the Remote Monitor Store service stops

(1) A Performance Management program service does not start

The following describes the possible causes and the resolutions.

(2) It takes too long for a service to start once startup is requested

It might take a long time for a service to actually start once you execute the jpcspm start command or you start a service by choosing the Services icon. If this is caused by either of the reasons listed below, the time required for starting the service will be reduced for subsequent startups of the service.

(3) Communication is not performed properly when a program service starts immediately after a Performance Management program service has stopped

Immediately after a Performance Management program service has stopped, another program service may be started using the same port that the stopped service was using. In such a case, communication might not be performed properly. You can prevent this problem by doing the following:

(4) The message "The disk capacity is insufficient" is displayed, and then the Master Store service or the Remote Monitor Store service stops

Data storage in the Store database is interrupted when there is not enough free space on the disk used by the Store database. In such a case, the message The disk capacity is insufficient is displayed and the Master Store service or the Remote Monitor Store service stops.

If this message is displayed, take one of the following actions:

If the Master Store service or the Remote Monitor Store service will not start after you have taken these actions, an unrecoverable logical conflict has occurred in the Store database. In such a case, restore the Store database from a backup and then start the Master Store service or the Remote Monitor Store service. If no backup is available, initialize the Store database and then start the Master Store service or the Remote Monitor Store service. To initialize the Store database, you must delete all the following files from the storage directory for the Store database:

For details about the storage directory for the Store database, see 2.6.1 Changing performance data storage locations.

[Contents][Back][Next]


[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.