12.2.1 Setting up or starting a service
(1) A Performance Management program service does not start
Causes and solutions:
- 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 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 Job Management Partner 1/Performance Management Planning and Configuration Guide.
- The folder specified for storing the Store database is invalid.
If any of the folders listed below is specified in an inaccessible or nonexistent folder, the Agent Store service cannot start. Check the folder name and attributes and correct them if necessary:
- Store database storage destination folder
- Store database backup folder
- Store database partial backup folder
- Store database export destination folder
- Store database import destination folder
If any of these folders is specified for multiple Agent Store services, the Agent Store services cannot start. Check the folder 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 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.
- An error occurred in the service control manager.
When the jpcspm start (jpcstart) command is executed in Windows, the message An error occurred in the Windows service control manager. may be displayed and the service startup may fail. If this condition occurs, re-execute the jpcspm start (jpcstart) command. If the same condition occurs frequently, change the retry interval and the number of retries to be used for service startup during the execution of the jpcspm start (jpcstart) command by editing the jpccomm.ini file. For details about how to change the retry interval and the number of retries, see the chapter explaining how to start and stop Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- Startup of the service is not set in the Probe action condition definition file
If you do not define the setting to start the IE Probe service from Windows services in the Probe action condition definition file, the IE Probe service does not start from Windows services. Check the settings in the Probe action condition definition file.
- The programs required for the IE Probe Daemon are not installed
If you do not install the required programs for the IE Probe Daemon in advance, the IE Probe Daemon does not start. Check whether the required programs are installed.
(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:
- If you start a service by restarting the system without having specified the setting for stopping the service automatically during system shutdown, it may be necessary for the indexes of the Store database to be rebuilt. When this happens, it takes extra time for the service to start.
- During initial startup after a new Agent has been added, the indexes of the Store database must be rebuilt, resulting in extra time for the service to start.
- If the Store service is unable to perform normal termination processing after a power failure, it may take extra time for a service to start because the indexes of the Store database have to be rebuilt during the restart.
(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:
- Specify fixed port numbers for assignment to the services of the Performance Management program.
Assign a fixed port number to each Performance Management program service. For details about how to set port numbers, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Set the TCP_TIMEWAIT value.
In setting the TCP_TIMEWAIT value, you specify a connection wait time.
Set the connection wait time to the default in the TCP_TIMEWAIT value. Use the following default value:
- In Windows Server 2003 and Windows Server 2008: 2 minutes
(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:
- Provide sufficient disk space
Determine the required disk capacity for the Store database, and change the Store database storage location to a disk with sufficient capacity. For details about how to determine the disk capacity required for the Store database, see A. Estimating System Requirements. For details about how to change the Store database storage location, see the chapter that describes installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Change the data retention condition for the Store database
Change the Store database's data retention condition and adjust the maximum data capacity. For details about how to change the Store database's data retention condition, see the chapter that describes management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.
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:
- Files with extension .DB
- Files with extension .IDX
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.
- The service-name service stops at the startup.
- The service-name service is hung up at the start.
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.
- The load from communication with JP1/PFM - Manager is high.
For example, this condition can arise when multiple PFM - Agent startup processes are being executed simultaneously.
- In the Services applet of Windows, Startup Type of each PFM - Agent service is set to Automatic.
- The OS is restarted.
You can use either of the following operational techniques to avoid this problem:
- If you start a service at the same time you restart the OS, do so by executing the jpcspm start command instead of starting the service from the Windows service control manager.
- Specify the following settings on the PFM - Agent host to reduce the startup time of PFM - Agent.
These settings reduce reconnection processing when connection to PFM - Manager cannot be established at PFM - Agent service startup. In this case, the PFM - Agent service tends to start in stand-alone mode.
To reduce the startup time of PFM - Agent, change the NS Init Retry Count label of Agent Collector x Section# and Agent Store x Section# in the startup information file jpccomm.ini from 2 to 1.
- #
- x represents the product ID of PFM - Agent. For details about the product ID, see B. List of Identifiers. When multiple PFM - Agent products have been installed on the same host, set the value of the NS Init Retry Count label for each product ID.
The following is the storage location of the startup information file jpccomm.ini:
- When the PFM - Agent host is a physical host:
- installation-folder\jpccomm.ini
- When the PFM - Agent host is a logical host:
- environment-directory#\jp1pc\jpccomm.ini
- #
- This is a directory on a shared disk specified when the logical host was created.