7.2.1 Problems relating to the start and setup of services
(1) Performance Management program service does not start
Potential causes and actions to take are as follows:
- PFM - Manager is not running
If PFM - Manager and PFM - RM for Microsoft SQL Server are installed on the same host, PFM - Manager must be running before the PFM - RM for Microsoft SQL Server service can start. Check that the PFM - Manager service is running and start it if not. For details about how to start services, see the chapter on starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.
- The same port number is assigned to multiple services of Performance Management programs
You will be unable to start a Performance Management service if it is assigned the same port number as another Performance Management service. By default, port numbers are allocated automatically. This prevents the same port number from being assigned more than once. If you specified fixed port numbers for services of Performance Management programs during Performance Management setup, check the settings you made. If you assigned the same port number to more than one service of Performance Management programs, assign a different port number to each service. For details about setting port numbers, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- The storage directories for the Store database are set incorrectly
A Remote Monitor Store service cannot start if any of the following directories are nonexistent or inaccessible. Check the directory names and attributes, and fix any errors.
- Store database storage destination directory
- Store database backup destination directory
- Store database partial backup destination directory
- Store database export destination directory
- Store database import destination directory
Also, the service cannot start if the same directories are assigned to multiple Remote Monitor Store services. Check the directory settings, and fix any errors.
- An unspecified method was used to change a machine's host name
For details about how to change a machine's host name, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide. If you change a host name using a method other than that specified in the manual, Performance Management services may not start.
- An error occurred in the service control manager
When you execute the jpcspm start command in Windows, occasionally the system outputs the following message and fails to start the service: An error occurred in the Windows service control manager. In this case, re-execute the jpcspm start command. If this problem occurs frequently, you can change the number of retries and the retry interval for when the system fails to start a service by editing the jpccomm.ini file. For details about changing the number of retries and the retry interval, see the chapter on starting and stopping Performance Management in the Job Management Partner 1/Performance Management User's Guide.
(2) There is a delay from the time the start request is issued until the service starts
Occasionally, you may experience a delay after executing the jpcspm start command or clicking an icon in the Services window until the service actually starts. If this delay is caused by one of the following, the service will start more quickly next time.
- If you do not set the service to stop automatically when the system shuts down, the system may need to rebuild the Store database when you start the service after restarting the system. This may cause a delay in starting the service.
- When you start the service for the first time after adding a new instance, an index is created for the Store database. This may cause a delay in starting the service.
- If the Store service was unable to complete shutdown processing because the system was powered off, for example, the system will rebuild the index of the Store database the next time the Store service is started. This may cause a delay in starting the Store service.
(3) Communication fails when a second program starts a service immediately after a Performance Management program service is stopped
If another program starts a service that uses the same port number as a Performance Management program service that has recently stopped, communication may not be performed correctly. To prevent this from occurring, perform either of the following settings:
- Use a fixed port number for the Performance Management program service
Assign fixed port numbers to Performance Management program services. For details about how to set port numbers, see the chapter on installation and setup in the Job Management Partner 1/Performance Management Planning and Configuration Guide.
- Set the TCP_TIMEWAIT value
Use the TCP_TIMEWAIT option to specify how much time must elapse before a connection is closed.
In Windows, use the default connection wait time. The respective default values are as follows:
- In Windows Server 2003 and Windows Server 2008 : 2 minutes
(4) The following message is output and the Master Store service or Remote Monitor Store service stops: "The disk capacity is insufficient"
The system will stop recording data in the Store database if there is not enough space on the disk used by the database. In this case, the following message is output and the Master Store or Remote Monitor Store service stops: The disk capacity is insufficient.
If this message appears, take one of the following actions:
- Ensure that sufficient disk space is available
Estimate the disk space requirements of the Store database, and change the storage location of the Store database to a disk that has sufficient free space. For details about how to estimate the disk space requirements of the Store database, see A. Estimating System Requirements. For details about how to change the location of the Store database, see 2.4.1 Changing the storage location of performance data.
- Change the data retention conditions of the Store database
Change the data retention conditions of the Store database to adjust the maximum amount of data that can be stored in the Store database. For details about how to change the data retention conditions, see the chapter on management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide.
If the Master Store service or Remote Monitor Store service still does not start, an unrecoverable logic conflict has occurred in the Store database. In this case, restore the Store database from backup data, and then start the Master Store or Remote Monitor Store service. If no backup data is available, initialize the Store database and then start the Master Store or Remote Monitor Store service. You can initialize the Store database by deleting the following files from the Store database's storage directory:
- Files with the extension .DB
- Files with the extension .IDX
For details about the storage directory of the Store database, see 2.4.1 Changing the storage location of performance data.
(5) The PFM - RM Remote Monitor Collector service does not start
For the PFM - RM host running in Windows, the Remote Monitor Collector service fails to start when PFM - RM 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 - RM startup processes are being executed simultaneously.
- In the Services applet of Windows, Startup Type of each PFM - RM 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 - RM host to reduce the startup time of PFM - RM.
These settings reduce reconnection processing when connection to PFM - Manager cannot be established at PFM - RM service startup. In this case, the PFM - RM service tends to start in stand-alone mode.
To reduce the startup time of PFM - RM, 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 - RM. For details about the product ID, see B. List of Identifiers. When multiple PFM - RM 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 - RM host is a physical host:
- installation-folder\jpccomm.ini
- When the PFM - RM 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.