6.4 Messages

This section explains the messages that are output by PFM - RM for Virtual Machine and the action to be taken by the user. The list of PFM - RM for Virtual Machine messages follows.

• KAVL20000-I

  Remote Monitor Collector has stopped. (host=<host-name>, service=<service-ID>)

  The Remote Monitor Collector service terminated normally.

  (S)

  Terminates processing of the Remote Monitor Collector service.

• KAVL20001-E

  Remote Monitor Collector failed to start.

  The Remote Monitor Collector service failed to start.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Check the previous message that was output to the common message log, and take the action indicated in that message.

• KAVL20002-I

  Remote Monitor Collector started. (host=<host-name>, service=<service-ID>)

  Startup of the Remote Monitor Collector service is complete.

  (S)

  Starts the performance data collection process of the Remote Monitor Collector service.

• KAVL20004-E

  An attempt to read the service startup information file has failed.

  During startup processing of the Remote Monitor Collector service, the service startup initialization file could not be loaded.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  If this message is output repeatedly, delete the instance environment and then re-create the instance. 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 JP1/Performance Management User's Guide.

• KAVL20005-E

  Remote Monitor Collector will now stop because an error occurred.

  The Remote Monitor Collector service is about to stop because an error has occurred.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Check the previous message that was output to the common message log, and take the action indicated in that message. 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 JP1/Performance Management User's Guide.

• KAVL20006-E

  Memory allocation failed.

  Memory allocation failed.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Increase the amount of free memory.

• KAVL20007-W

  Memory allocation failed. (RecordType=<record-type>)

  Memory allocation failed. If UNKNOWN is output in record-type, this means that memory allocation failed for multiple record IDs.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Increase the amount of free memory.

• KAVL20008-W

  An attempt to collect the record failed. (Instance=<instance-name>, Target=<monitoring-target-name>, RecordType=<record-type>)

  The record indicated by record-type could not be collected.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20009-W

  An invalid value or a value outside the range was specified for the property of the Remote Monitor Collector service. (Instance=<instance-name>, Target=<monitoring-target-name>, property=<property-name>, value=<range-value>)

  An invalid value or a value outside the range was specified for a property of the Remote Monitor Collector service.

  (S)

  Invalidates the specified value and continues processing of the Remote Monitor Collector service. The item value remains unchanged.

  (O)

  Check whether the value that is specified is acceptable. If not, specify an appropriate value.

• KAVL20010-E

  An error occurred in the function. (function=<function-name>, en=<error-code>, arg1=<argument-1>, arg2=<argument-2>, arg3=<argument-3>)

  An error occurred during execution of the function indicated by function-name.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20011-W

  The collector process failed to start.

  A collection process failed to start.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20013-W

  A performance data file is invalid. (Instance=<instance-name>, Target=<monitoring-target-name>)

  The content of a performance data storage file is invalid.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20014-W

  A collector process was forcefully terminated because performance data collection did not end in the specified period of time. (Instance=<instance-name>, Target=<monitoring-target-name>)

  A collection process was forcibly terminated because performance data collection did not end within the specified period of time.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check the following items:

  • Whether the monitoring-target host has started

  • Whether the connection settings on the virtualization system side are correct

  • Whether the PFM - RM host and the virtualization system are in a temporary high load state

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    - If the default certificate of VMware is used, confirm whether the Update Root Certificate functions affect the operation. For details, see 2.5.1 For VMware.

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service has started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses logical partitioning feature:

    - Whether the IP address (VM_Host) is correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

    If the monitoring target uses Docker environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether Port has been set to a correct value other than 0

    If the monitoring target uses Podman environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

  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 JP1/Performance Management User's Guide.

• KAVL20015-I

  The records were successfully saved onto the Store database. (Instance=<instance-name>, RecordType=<record-type>, count=<record-count>)

  The process of saving the record(s) indicated by record-type in the Store database is complete.

  (S)

  Continues processing of the Remote Monitor Collector service.

• KAVL20016-W

  The initialization of interprocess communication failed. (Instance=<instance-name>)

  Initialization of communications between the Remote Monitor Collector service and a collection process failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Opening of or writing to a work file may have failed. Check to make sure that there is no disk space shortage.

  If disk space is not a problem, 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 JP1/Performance Management User's Guide.

• KAVL20017-W

  An error occurred during collection of the record. (Instance=<instance-name>, Target=<monitoring-target-name>)

  An error occurred during collection of the record.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20018-W

  Account authentication failed. (Instance=<instance-name>)

  Account authentication failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the following items that were specified during setup of the instance environment are correct:

  • HostUserID

  • HostPassword

  • HostDomain

• KAVL20201-W

  The system could not connect to the monitored virtual environment. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  The system could not connect to the monitored virtual environment.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check the following items:

  • Whether the monitoring-target host has started

  • Whether the connection settings on the virtualization system side are correct

  • Whether the PFM - RM host and the virtualization system are in a temporary high load state

  • (If there is a firewall between PFM - RM for Virtual Machine and the monitoring-target host) Whether the ports used for communication are properly set in the firewall

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service has started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses logical partitioning feature:

    - Whether the IP address (VM_Host) is correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

    If the monitoring target uses Docker environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether Port has been set to a correct value other than 0

    If the monitoring target uses Podman environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

  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 JP1/Performance Management User's Guide.

• KAVL20202-W

  An attempt to authenticate the monitored virtual environment has failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  The monitored virtual environment could not be authenticated.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Make sure that the host of the virtual environment is active. Furthermore, make sure that the following items, which were specified during setup of the monitoring-target, are correct:

  • UserID

  • Password

• KAVL20203-W

  Initialization of the collector process log file failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  Initialization of a collection process log failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Opening of or writing to a work file may have failed. Check to make sure there is no disk space shortage.

  If disk space is not a problem, 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 JP1/Performance Management User's Guide.

• KAVL20204-W

  Initialization of the collector process failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  Initialization of a collection process failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20205-W

  A certificate is not installed or a certificate is not correct. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  No certificate is installed or an incorrect certificate is installed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Install a CA-signed certificate.

  If the problem is not resolved even after a CA-signed certificate is installed, check the following items in the installed certificate:

  • Effective period

  • Issuing destination (whether it is the same as the host name)

  • Validity of the certificate (has verification been completed successfully?)

  If the monitoring target uses VMware:

  If there is a problem with the certificate, re-create a certificate and then re-install it. For details about how to create a certificate, see the VMware documentation.

  If the default certificate of VMware is used for operation, ignore this message.

  For details about a certificate, see 2.5.1 For VMware.

  If the monitoring target uses Docker environment:

  For details about a certificate, see 2.5.4 For Docker environment.

• KAVL20206-W

  A certificate is not correct. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  The certificate is not trusted.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Configure the certificate installed on the monitoring target so that it can be trusted.

  If the problem is not resolved even after the certificate is configured to be trusted, check the following items in the certificate:

  If the problem is not resolved even after the certificate is configured to be trusted, check the following items in the certificate:

  • Effective period

  • Issuing destination (whether it is the same as the host name)

  • Validity of the certificate (has verification been completed successfully?)

  If there is a problem with the certificate, re-create a certificate and then re-install it.

  If the monitoring target uses VMware:

  For details about how to create a certificate, see the VMware documentation.

  For details about a certificate, see 2.5.1 For VMware.

  If the monitoring target uses Docker environment:

  For details about a certificate, see 2.5.4 For Docker environment.

• KAVL20300-W

  It failed to occur JP1 system event or Agent event.

  A JP1 system event or agent event could not be issued.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20301-W

  It failed to issue JP1 system event or Agent event, because Memory is insufficient.

  A JP1 system event or agent event could not be issued.

  (S)

  Continues processing of the Remote Monitor Collector.

  (O)

  Increase the amount of free memory.

• KAVL20505-E

  An attempt to read the target information file has failed. (Target=<monitoring-target-name>)

  The monitoring target information file could not be loaded while the Remote Monitor Collector service was being started.

  (S)

  Stops the Remote Monitor Collector service.

  (O)

  Delete the relevant monitoring target, and then re-create it.

• KAVL20513-W

  The collector process failed to start.

  The collection process could not be started.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  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 JP1/Performance Management User's Guide.

• KAVL20516-W

  Performance data was not saved to the Store database because it is the same as previous performance data. (Instance=<instance-name>, Target=<monitoring-target-name>, RecordType=<record-type>)

  Performance data was not saved in the Store database because the data was the same as the previously collected data.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Make sure that the collection process execution interval does not exceed the record collection interval.

  If this problem frequently occurs when the collection process execution interval does not exceed the record collection interval, increase the value of the record collection interval or decrease the number of hosts monitored in the instance environment.

  Note

  If this message is output repeatedly, see Appendix N. What to Do When the Message KAVL20516-W Is Output Repeatedly.

• KAVL20517-W

  The record build failed because there is no performance data. (Instance=<instance-name>, Target=<monitoring-target-name>)

  An attempt to build records failed because there was no performance data.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  This alert might occur immediately after startup because no performance data has been collected.

  If this alert continues to occur after the first collection finishes, check the following items:

  • Whether the monitoring-target host has started

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service is started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses logical partitioning feature:

    - Whether the IP address (VM_Host) is correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

    - Whether the SSH_Client value specified during instance setup is correct

    If the monitoring target uses Docker environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed

    - Whether Port has been set to a correct value other than 0

    If the monitoring target uses Podman environment:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the SSH_Type and SSH_Client values are correct

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

  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 JP1/Performance Management User's Guide.

• KAVL20521-I

  A collector process will restart because the system detected that it stopped. (Instance=<instance-name>)

  The collection process will be restarted because its stoppage was detected.

  (S)

  Continues processing of the Remote Monitor Collector service.

• KAVL20524-W

  There are no SSH client execution modules. (Instance=<instance-name>)

  The value set as the SSH client execution module (SSH_Client) is incorrect. Make sure that you specify a correct value when monitoring KVM or Podman environment.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the value of the following property that was set during setup of the instance environment is correct:

  • SSH_Client

• KAVL20526-W

  There are no private keys. (Instance=<instance-name>, Target=<monitoring-target-name>)

  The private key file to be used for SSH public key encryption is not correctly set (Private_Key_File). Make sure that you specify a correct value when monitoring KVM or Podman environment.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the value of the following property that was set during setup of the monitoring target is correct:

  • Private_Key_File

• KAVL20527-W

  An attempt to read the user record define information file has failed. (Instance=<instance-name>, Line=<line-number>, message=<detailed-message>)

  During startup processing of the Remote Monitor Collector service, the user-defined record definition file could not be loaded.

  (S)

  Continues processing of the Remote Monitor Collector service.

  Does not collect the user defined record of the record type with the error.

  (O)

  Check the detailed message to make sure the user-defined record definition file is correct.

  • File open error.

    The user-defined record definition file exists but failed to open.

  • Ignoring duplicate [[SECTION NAME]].

    [[SECTION NAME]] specified for [RECORD ID] is duplicated.

  • XXXXX is required.

    XXXXX needs to be specified.

  • XXXXX is not correct.

    The specified XXXXX is incorrect.

  • The specified order is not correct.

    The items are specified in the wrong order.

  • Unknown parameter.

    An unknown parameter is specified.

• KAVL20528-I

  User record collection enabled. (Instance=<instance-name>, RecordType=<record-type>)

  Performance data is collected as specified in the user-defined record definition file.

  (S)

  Continues processing of the Remote Monitor Collector service.

• KAVL20529-W

  An attempt to read the settings information file has failed.

  Failed to read the PFM - RM for Virtual Machine setup file while the Remote Monitor Collector service was starting up.

  (S)

  Continues processing of the Remote Monitor Collector service using default settings.

  (O)

  If this message is output with changes made to the default settings, first enable reading of the PFM - RM for Virtual Machine setup file (save the file and ensure it can be read) then restart the service of the instance environment.

  If operating with the default settings, you do not have to restart the service of the instance environment. Continue processing using the default settings.

To Page Top