12.2.1 Setting up or starting a service

This subsection describes how to handle errors related to service setup and startup.

Organization of this subsection
(1) A Performance Management program service does not start
(2) It takes a long time for a service to start after startup is requested
(3) Another program service is started immediately after a Performance Management program service has stopped, but communication is not performed correctly
(4) The Master Store or Agent Store service stops after display of the message "The disk capacity is insufficient"
(5) The PFM - Agent Agent Collector service does not start

(1) A Performance Management program service does not start

Causes and solutions:

(2) It takes a long time for a service to start after startup is requested

It may take a considerable amount of time for a service to actually start after you execute the jpcspm start (jpcstart) command or choose the service's icon. If this is caused by any of the following reasons, the time required for the service to start will be reduced the second and subsequent times the service is started:

(3) Another program service is started immediately after a Performance Management program service has stopped, but communication is not performed correctly

If another program service is started immediately after a Performance Management program service has stopped and both services use the same port, communication may not be performed correctly. You can use either of the following techniques to avoid this problem:

(4) The Master Store or Agent Store service stops after display of the message "The disk capacity is insufficient"

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

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

If the Master Store or Agent Store service still won't start after taking one of these actions, an unrecoverable logical conflict may have occurred in the Store database. In such a case, restore the Store database from a backup and then start the Master Store or Agent Store service. If no backup is available, initialize the Store database, and then start the Master Store or Agent Store service. To initialize the Store database, you must delete all of the following files in the Store database's storage folder:

For details about the Store database's storage folder, see 2.4.1 Changing the performance data storage destination.

(5) The PFM - Agent Agent Collector service does not start

For the PFM - Agent host running in Windows, the Agent Collector service fails to start when PFM - Agent is started, and either of the following messages is output to the Windows event log when Windows is restarted.

Because this failure is due to the Windows service control manager timing out, the failure tends to occur when the communication load with PFM - Manager is high, and too much time is required to receive a response from PFM - Manager. This problem occurs when all the following conditions exist.

You can use either of the following operational techniques to avoid this problem: