7.2.5 Performance data collection and management

This subsection describes troubleshooting related to performance data collection and management procedures of Performance Management.

Organization of this subsection

(1) Even though a short data retention period was set, the size of the PFM - RM for Virtual Machine Store database is not reduced
(2) The message "Illegal data was detected in the Store database" is output to the common message log
(3) No performance data is collected even when PFM - RM for Virtual Machine is started
(4) There is a large time difference between Record Time and Sampling Time

(1) Even though a short data retention period was set, the size of the PFM - RM for Virtual Machine Store database is not reduced

If the file capacity of the Store database has already reached its limit, setting a shorter data retention period will not reduce the file size. In this case, set a shorter retention period first, back up the Store database, and then restore it.

For details about how to set the data retention period, see the chapter that explains management of operation monitoring data in the Job Management Partner 1/Performance Management User's Guide. For details about how to back up and restore the Store database, see the chapter that explains backup and restoration in the Job Management Partner 1/Performance Management User's Guide.

To Page Top

(2) The message "Illegal data was detected in the Store database" is output to the common message log

It is suspected that an unexpected service stoppage or machine shutdown generated invalid data in the Store database. Take the following actions:

If the Store database has been backed up, restore it.
If the Store database has not been backed up, first stop Remote Monitor Store, delete the corresponding database files (*.DB and *.IDX files), and then restart the service.

To Page Top

(3) No performance data is collected even when PFM - RM for Virtual Machine is started

The items to check and the actions to be taken are described below for each monitored virtual environment.

(a) For VMware

If you are monitoring information of a virtual machine running on VMware, check the following items:
- Make sure that VMware Tools is running on the monitored virtual machine.
- If you change the time on a physical server on which VMware is running. performance data may not be collected in some cases. In such cases, start the mgmt-vmware service.

If the Status field value of a PD record shows ERROR, take an action based on the value in the Reason field. The table below shows the actions to be taken.

Table 7‒2: Reason field value and actions to be taken
Reason field value	Explanation	Action
Connection failed	An attempt to connect to the target virtual environment failed.	Check whether the host of the virtual environment is active. Check whether the following items, which were specified during setup of the instance environment, are valid:^# - `VM_Type` Check whether the following items, which were specified during setup of the monitoring target, are valid:^# - `Target Host` - `VM_Host` - `Security` - `Port` - `UserID` - `Password` Check whether the host name (`Target Host` or `VM_Host`), which was specified during setup of the monitoring target, can be resolved. If SSL is used for communication with the virtual environment (`1` is set in `Security`), check whether a certificate has been embedded. For PFM - RM for Virtual Machine, a certificate must be installed for each monitoring target. Check whether the communication method that was specified for `Security` during setup of the monitoring target is permitted on the virtual environment side. For example, if `Security=1` (to use SSL) is specified, HTTPS connection must be permitted on the virtual environment side. In some cases, the virtual environment side can be set to redirect HTTP connection to HTTPS connection (`httpsWithRedirect` for VMware). If redirecting is enabled, HTTPS connection will succeed, but HTTP connection will fail. Therefore, specify `Security=1` (use SSL) in the monitoring target settings to use an HTTPS connection. For details about how to set a communication method for a virtual environment, see the VMware documentation. Make sure that the user ID that was specified for `UserID` during setup of the monitoring target has at least read-only permissions for VMware roles. For details about how to check permissions, see the VMware documentation.
Authorization failed	Authorization failed at the target virtual environment.	Check whether the host of the virtual environment is active. Check whether the following items, which were specified during setup of the monitoring target, are valid:^# - `UserID` - `Password` - `Domain`
Timeout	Performance data collection did not end within the specified time.	Check whether the host of the virtual environment is active. Check whether the following items, which were specified during setup of the instance environment, are valid:^# - `VM_Type` Check whether the following items, which were specified during setup of the monitoring target, are valid:^# - `Target Host` - `VM_Host` - `Security` - `Port` - `UserID` - `Password` Check whether the host name (`Target Host` or `VM_Host`) which was specified during setup of the monitoring target, can be resolved. If SSL is being used for communication with the virtual environment (`1` is set in `Security`), make sure that a certificate has been embedded. For PFM - RM for Virtual Machine, a certificate must be installed for each monitoring target. If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
Collection Error	A collection error occurred.	Check whether the following items that were specified during setup of the instance environment are correct:^# - `HostUserID` - `HostPassword` - `HostDomain` If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

#: To check an item that has been set, execute the jpcconf command. Alternatively, on PFM - Web Console, view the Remote Monitor Configuration properties from the Remote Monitor Collector service of PFM - RM for Virtual Machine.

In all other cases, collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
If the OS of the monitoring-target host is Windows, take action by checking the application event log.

(b) For Hyper-V

If the Status field value of a PD record shows ERROR, take action as indicated by the value in the Reason field. The table below shows the actions to be taken.

Table 7‒3: Reason field value and actions to be taken
Reason field value	Explanation	Action
Connection failed	Attempt to connect to the target virtual environment failed.	Check whether the host of the virtual environment is active. Check whether the following items that were specified during setup of the instance environment are correct:^# - `VM_Type` Check whether the following items, which were specified during setup of the monitoring target, are valid:^# - `Target Host` - `VM_Host` - `UserID` - `Password` - `Domain` Check whether the host name (`Target Host` or `VM_Host`) that was specified during setup of the monitoring target can be resolved. Check whether the WMI connection has been set up correctly. For PFM - RM for Virtual Machine, WMI connection settings must be specified for each monitoring target.
Authorization failed	Authorization failed at the target virtual environment.	Check whether the host of the virtual environment is active. Check whether the following items that were specified during setup of the monitoring target are correct:^# - `UserID` - `Password` - `Domain`
Timeout	Performance data collection did not end within the specified time.	Check whether the host of the virtual environment is active. Check whether the following items that were specified during setup of the instance environment are correct:^# - `VM_Type` Check whether the following items, which were specified during setup of the monitoring target, are valid:^# - `Target Host` - `VM_Host` - `UserID` - `Password` - `Domain` Check whether the host name (`Target Host` or `VM_Host`) that was specified during setup of the monitoring target can be resolved. Check whether the WMI connection has been set up correctly. For PFM - RM for Virtual Machine, WMI connection settings must be specified for each monitoring target. If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
Collection Error	A collection error occurred.	Check whether the following items that were specified during setup of the instance environment are correct:^# - `HostUserID` - `HostPassword` - `HostDomain` If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

#: Use the jpcconf command to check what has been set for an item. Alternatively, the Remote Monitor Configuration properties from the Remote Monitor Collector service of PFM - RM for Virtual Machine can be viewed on PFM - Web Console.

In all other cases, collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
If the OS of the monitoring-target host is Windows, check the application event log.

(c) For KVM

If the Status field of the PD record stores the value ERROR, take action according to the value of the Reason field. The following table lists the values of the Reason field and describes the action to be taken for each value.

Table 7‒4: Action to be taken according to the value of the Reason field
Reason field value	Explanation	Action
Connection failed	Connection to the destination virtual environment failed.	Check whether the host in the virtual environment has started. Make sure that the following settings specified during instance environment setup are correct:^# - `VM_Type` - `SSH_Client` Make sure that the following settings specified during monitoring target setup are correct:^# - `Target Host` - `VM_Host` - `Port` - `UserID` - `Private_Key_File` Make sure that the host name specified (for `Target` `Host` and `VM_Host`) during monitoring target setup can resolve to an IP address. Make sure that the SSH connection settings are specified. For PFM - RM for Virtual Machine, these settings must be specified for each monitoring target.
Authorization failed	Authentication failed in the destination virtual environment.	Check whether the host in the virtual environment has started. Make sure that the following settings specified during instance environment setup are correct:^# - `HostUserID` - `HostPassword` - `HostDomain` Make sure that the following settings specified during monitoring target setup are correct:^# - `UserID`
Timeout	Performance data collection did not end within the specified length of time.	Check whether the host in the virtual environment has started. Make sure that the following settings specified during instance environment setup are correct:^# - `VM_Type` - `HostUserID` - `HostPassword` - `HostDomain` Make sure that the following settings specified during monitoring target setup are correct:^# - `Target Host` - `VM_Host` - `Port` - `UserID` - `Private_Key_File` Make sure that the host name specified (for `Target` `Host` and `VM_Host`) during monitoring target setup can resolve to an IP address. Make sure that the SSH connection settings are specified. For PFM - RM for Virtual Machine, these settings must be specified for each monitoring target. If the cause of the problem cannot be determined, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
Collection Error	A collection error occurred.	Make sure that the following settings specified during instance environment setup are correct:^# - `HostUserID` - `HostPassword` - `HostDomain` If the cause of the problem cannot be determined, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

#: To check the settings that have been specified, execute the jpcconf command. You can also check them from PFM - Web Console by referencing the Remote Monitor Configuration properties of the Remote Monitor Collector service of PFM - RM for Virtual Machine.

In any conditions other than the above condition, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter on troubleshooting in the Job Management Partner 1/Performance Management User's Guide.
If the OS of the monitoring-target host is Windows, check the application event log.

To Page Top

(4) There is a large time difference between Record Time and Sampling Time

Because Sampling Time is the time in the monitored virtual environment, a slight time deviation may occur in normal operations. If the time deviation is large enough to cause an operational problem, check the following items:

Is the time set on the RM host different from that set in the monitored virtual environment?

If they are different, they need to be synchronized. Before changing the time settings, carefully read the notes related to the OS of the RM host and the virtual environment software.
If SSL is being used for communication with the virtual environment, has a certificate been embedded?

If a certificate has not been embedded correctly, information collection may be delayed. See 2.5.1 For VMware, and correctly embed a certificate in the RM host. For details about how to embed a certificate in a monitored virtual environment, see the documentation for the virtual environment software.

To Page Top