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

7.2.1 Setup and service startup

This subsection describes troubleshooting related to setup and service startup.

Organization of this subsection

(1) If a Performance Management program service does not start

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

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

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

(1) If a Performance Management program service does not start

Factors that may be preventing the service of a Performance Management program from starting and the actions that can be taken are described below.

PFM - Manager is stopped
When PFM - Manager and PFM - Agent are on the same host, the PFM - Agent service cannot start if PFM - Manager is stopped. Check whether PFM - Manager is active. If it is not, start it. For details about how to start a service, see the chapter that explains startup and termination of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

The same port number is set for multiple services of a Performance Management program
If the same port number is set for multiple services of a Performance Management program, a Performance Management service cannot start. By default, port numbers are automatically assigned, and thus will not be duplicated. If you set fixed port numbers for Performance Management program services during setup of Performance Management, check the port number settings. If the same port number is set up for multiple services of a Performance Management program, specify different port numbers. For details about how to set port numbers, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

The storage folder settings in the Store database are invalid
If any of the folders listed below is located in an inaccessible or nonexistent folder, an Agent Store service cannot start. Check the folder name and attribute settings, and correct them if they are invalid.

Store database storage folder

Store database backup folder

Store database partial backup folder

Store database export folder

Store database import folder

Additionally, if any of these folders is set up for multiple Agent Store services, an Agent Store service cannot start. Check the folder settings and correct them if they are invalid.

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

An error occurred in the service control manager
When the jpcspm start command is executed in Windows, the message An error occurred in the Windows service control manager may be output and service startup may fail. If this occurs, re-execute the jpcspm start command. If the same event occurs frequently, change the interval and count for retrying service startup during execution of the jpcspm start command by editing the jpccomm.ini file. For details about how to change the retry interval and count, see the chapter that explains startup and termination of Performance Management in the Job Management Partner 1/Performance Management User's Guide.

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

After you have executed the jpcspm start command or have started a service using the Services icon, it may take a while before the service actually starts. If any of the factors listed below is delaying startup, the service startup time will be shorter when the service is started the second time and thereafter.

When a service is being started in stand-alone mode, it may take a while to start.

If you have not set the system to automatically stop services when the system stops, and if you restart the system and try to start a service, the Store database index is rebuilt in some cases. In such cases, service startup may take a while.

If you start a service after having added a new agent, the Store database index is created during the initial startup only. Consequently, service startup may take a while.

If the Store service could not perform normal termination processing because of a power outage or other such problem, the Store database index is rebuilt during a restart, with the consequence that it might take a while for a Store service to start.

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

Immediately after a Performance Management program service has stopped, if another program starts a service using the port number that was being used by the first service, communication may not be established correctly. To prevent this from happening, take one of the following actions:

Assign fixed port numbers to the services of Performance Management programs
Assign fixed port numbers to the services of Performance Management programs. For details about how to assign port numbers, see the chapter that explains installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.

Set the TCP_TIMEWAIT value
Set the connection wait time of the TCP_TIMEWAIT value to the default. The default is as follows:

In Windows Server 2003 and Windows Server 2008: 2 minutes

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

If the disk being used by the Store database has insufficient free space, the operation of storing data in the Store database stops. In this case, after the message The disk capacity is insufficient is output, the Master Store service or Agent Store service stops.

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

Secure sufficient disk capacity
Estimate the amount of disk space the Store database is using, and then switch the Store database storage destination to a disk that has sufficient capacity. For details about how to estimate the amount of disk space the Store database is using, see A. Estimating System Requirements. For details about how to switch the Store database storage destination, see 2.4.1 Changing the performance data storage destination.

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

If a Master Store service or Agent Store service still does not start even after these actions have been taken, a non-recoverable logical conflict has occurred in the Store database. In this case, restore the Store database from a backup, and then start the Master Store service or Agent Store service. If there is no backup data that can be used, 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 from the Store database storage folder:

Files with the .DB extension

Files with the .IDX extension

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

[Contents][Back][Next]

[Trademarks]