4. Error messages

This chapter provides information on error messages you might encounter when operating EXPRESSCLUSTER X SingleServerSafe.

This chapter covers:

• 4.1. Messages reported by syslog, alert, mail, SNMP trap, and Message Topic

• 4.2. Driver syslog messages

• 4.3. Detailed information on activating and deactivating group resources

• 4.4. Details about monitor resource errors

• 4.5. JVM monitor resource log output messages

• 4.6. Details on checking cluster configuration data

4.1. Messages reported by syslog, alert, mail, SNMP trap, and Message Topic

If the "o" mark is shown in the alert column or the syslog column, the message on that row is output to the Alert logs of Cluster WebUI or syslog of OS, respectively.

If the "o" mark is shown in the mail column, the message on that row is reported when E-mail report function of Alert Service is enabled.

If the "o" mark is shown in the SNMP Trap column, the message on that row is reported when SNMP trap sending function of Alert Service is enabled.

For mail reporting and SNMP Trap transmission, refer to the Reference Guide.

If the "o" mark is shown in the Message Topic column, the message on that row is reported when Amazon SNS linkage function is enabled.

For details of Amazon SNS linkage function, see "EXPRESSCLUSTER X SingleServerSafe Configuration Guide" - "Details of other settings" - "Cluster properties" - "Cloud tab".

The table below lists EXPRESSCLUSTER X SingleServerSafe messages.

Note

Alert mail reporting messages are output to syslog with facility = daemon(0x00000018), identity = "expresscls". Event Type in the table below is equivalent to a syslog log level.

In the table below, each number indicates the following:

[1]alert, [2]syslog, [3]Mail Report, [4]SNMP Trap, [5]Message Topic

Module Type	Event Type	Event ID	Message	Explanation	Solution	1	2	3	4	5
sss	Error	8	Failed to update config file.	The configuration file could not be updated.	Check the configuration data.	o	o
sss	Info	10	Updated config file successfully.	The configuration file has been updated.	-		o
sss	Error	12	Information in config file is invalid.	The content of the configuration file is invalid.	Check the configuration data.		o
sss	Error	14	Failed to obtain server name.	The server name could not be acquired.	Memory or OS resources may not be sufficient. Check them.		o
sss	Info	16	Server name is updated.	The server name has been updated.	-	o	o
pm	Info	1	Starting the cluster daemon...	The EXPRESSCLUSTER daemon has been successfully started.	-	o	o
pm	Info	2	Shutting down the cluster daemon...	The EXPRESSCLUSTER daemon is now being shut down.	-	o	o
pm	Info	3	Shutdown monitoring is started...	Shutdown monitoring has been started.	-	o	o
pm	Error	10	The cluster daemon has already started.	The EXPRESSCLUSTER daemon has already been already started.	Check the EXPRESSCLUSTER daemon status.	o	o
pm	Error	11	A critical error occurred in the cluster daemon.	A critical error occurred in the EXPRESSCLUSTER daemon.	The user executing the operation does not have root privileges, or there is an insufficiency of memory or OS resources. Check them.	o	o	o	o	o
pm	Error	12	A problem was detected in XML library.	A problem was detected in the XML library.	Memory or OS resources may not be sufficient. Check them.	o	o
pm	Error	13	A problem was detected in cluster configuration data.	A problem was detected in configuration data.	Check the configuration data by using the Cluster WebUI.	o	o	o	o	o
pm	Error	14	No cluster configuration data is found.	The configuration data does not exist.	Create a server configuration by using the Cluster WebUI and upload it to the server.	o	o
pm	Error	15	No information about this server is found in the cluster configuration data.	This server was not found in the configuration data.	Check the configuration data by using the Cluster WebUI.	o	o
pm	Warning	16	The recovery action is configured to change from an OS stop to an OS restart.	Checking the configuration of cluster properties.	-	o	o
pm	Error	20	Process %1 was terminated abnormally.	Process %1 terminated abnormally.	Memory or OS resources may not be sufficient. Check them. The abend of the nm process, which does not affect the business operation, prevents you from stopping the cluster. To recover from it, restart the OS by using Cluster WebUI or the clpdown command.	o	o	o	o	o
pm	Error	21	The system will be stopped because the cluster daemon process terminated abnormally.	The system will now stop because the EXPRESSCLUSTER daemon process terminated abnormally.	Deactivation of group resources may be failed. Troubleshoot by following the group resource message.	o	o
pm	Error	22	An error occurred when initializing process %1.(return code:%2)	An initialization error occurred in process %1.	The event process might not be running.	o	o	o	o	o
pm	Info	23	The system will be stopped.	The system will now stop.	-	o	o
pm	Info	24	The cluster daemon will be stopped.	Stops the cluster daemon.	-	o	o
pm	Info	25	The system will be rebooted.	System will be rebooted.	-	o	o
pm	Info	26	Process %1 will be restarted.	Process %1 will now be restart.	-	o	o
pm	Info	30	Received a request to stop the system from %1.	A request to stop the system was received from %1.	-	o	o
pm	Info	31	Received a request to stop the cluster daemon from %1.	A request to stop the EXPRESSCLUSTER daemon was received from %1.	-	o	o
pm	Info	32	Received a request to reboot the system from %1.	A request to reboot the system was received from %1.	-	o	o
pm	Info	33	Received a request to restart the cluster daemon from %1.	A request to reboot the EXPRESSCLUSTER daemon was received from %1.	-	o	o
pm	Info	34	Received a request to resume the cluster daemon from %1.	A request to resume the server was received from %1.	-	o	o
pm	Info	35	Received a request to suspend the cluster daemon from %1.	A request to suspend the server was received from %1.	-	o	o
pm	Info	36	Received a request to panic by sysrq from %1.	A request for a panic by sysrq was received from %1.	-	o	o
pm	Info	37	Received a request to reset by keepalive driver from %1.	A request for a reset by the keepalive driver was received from %1.	-	o	o
pm	Info	38	Received a request to panic by keepalive driver from %1.	A request for a panic by the keepalive driver was received from %1.	-	o	o
pm	Info	39	Received a request to reset by BMC from %1.	A request for a reset by BMC was received from %1.	-	o	o
pm	Info	40	Received a request to power down by BMC from %1.	A request for a power down by BMC was received from %1.	-	o	o
pm	Info	41	Received a request to power cycle by BMC from %1.	A request for a power cycle by BMC was received from %1.	-	o	o
pm	Info	42	Received a request to send NMI by BMC from %1.	A request for NMI transmission by BMC was received from %1.	-	o	o
pm	Error	66	An attempt to panic by sysrq from %1 failed.	An attempt to perform a panic by sysrq from %1 failed.	Check whether the system is set up so that it can be used by sysrq.	o	o
pm	Error	67	An attempt to reset by keepalive driver from %1 failed.	An attempt to perform a reset by the keepalive driver from %1 failed.	Check whether the keepalive driver can be used in this environment.	o	o
pm	Error	68	An attempt to panic by keepalive driver from %1 failed.	An attempt to perform a panic by the keepalive driver from %1 failed.	Check whether the keepalive driver can be used in this environment.	o	o
pm	Error	69	An attempt to reset by BMC from %1 failed.	An attempt to perform a reset by BMC from %1 failed.	Check whether the ipmitool command can be used.	o	o
pm	Error	70	An attempt to power down by BMC from %1 failed.	An attempt to perform a power down by BMC from %1 failed.	Check whether the ipmitool command can be used.	o	o
pm	Error	71	An attempt to power cycle by BMC from %1 failed.	An attempt to perform a power cycle by BMC from %1 failed.	Check whether the ipmitool command can be used.	o	o
pm	Error	72	An attempt to send NMI by BMC from %1 failed.	An attempt to send NMI by BMC from %1 failed.	Check whether the ipmitool command can be used.	o	o
nm	Info	1	Server %1 has started.	Server %1 has started.	-	o	o
nm	Info	2	Server %1 has been stopped.	Server %1 has stopped.	-	o	o	o	o	o
nm	Info	3	Resource %1 of server %2 has started.	Resource %1 of server %2 has started.	-	o	o
nm	Info	4	Resource %1 of server %2 has stopped.	Resource %1 of server %2 has stopped.	-	o	o
nm	Info	5	Waiting for all servers to start.	Waiting for the server to start has started.	-	o	o
nm	Info	6	All servers have started.	The server has started.	-	o	o
nm	Info	7	Timeout occurred during the wait for startup of all servers.	Waiting for all servers to start resulted in a timeout.	-	o	o
nm	Error	8	Timeout occurred during the wait for startup of all servers. (Cannot communicate with some servers.)	Waiting for all servers to start resulted in a timeout. (Internal communication with some servers is not possible.)	Check that there is no error in the network adapter and the network is correctly connected.	o	o
nm	Info	9	Waiting for startup of all servers has been canceled.	Waiting for all servers to start has been canceled.	-	o	o
nm	Error	10	Status of resource %1 of server %2 is unknown.	Resource %1 of Server %2 is unknown.	Check whether the cable or network settings related to resource %1 are correct.	o	o	o	o	o
nm	Warning	11	NP resolution process at the cluster startup is disabled.	The NP resolution process at the cluster startup is disabled.	The NP resolution process at the cluster startup is disabled.	o	o
nm	Error	20	Process %1 was terminated abnormally.	Process %1 terminated abnormally.	Memory or OS resources may not be sufficient. Check them.	o	o	o	o	o
nm	Info	21	The system will be stopped.	The system will now stop.	-	o	o
nm	Info	22	The cluster daemon will be stopped.	Stops the cluster daemon.	-	o	o
nm	Info	23	The system will be rebooted.	System will be rebooted.	-	o	o
nm	Info	24	Process %1 will be restarted.	%1 process will be restarted.	-	o	o
nm	Error	30	Network partition was detected. Shut down the server %1 to protect data.	Network partition was detected. Shut down server %1 to protect data.	All heartbeat resources cannot be used. Check that there is no error in the network adapter and the network is correctly connected. If DISKHB is being used, check the shared disk status.	o	o
nm	Error	31	An error occurred while confirming the network partition. Shut down the server %1.	An error occurred in confirming the network partition. Shut down the server %1.	Check whether an error occurred in the network partition resolution resource.	o	o
nm	Error	32	Shut down the server %1. (reason:%2)	Shut down server %1. (Reason: %2)	No heartbeat can be used. Check that there is no error in the network adapter and the network is correctly connected. If DISKHB is being used, check the shared disk status.	o	o
nm	Error	33	Cluster service will be stopped. (reason:%1)	Stop the service. (reason: %1)	Check the cause following the message.	o	o
nm	Error	34	The combination of the network partition resources is invalid. (server name:%1)	The combination of the network partition resources is invalid. (erver name: %1)	Check the configuration data.	o	o
nm	Error	35	Failed to start the resource %1. Server name:%2	Starting resource %1 failed. (Server name: %2)	Check whether an error occurred in the network partition resolution resource.	o	o
nm	Info	36	The network partition %1 of the server %2 has been recovered to the normal status.	Network partition %1 of server %2 has been recovered to the normal status.	-	o	o
nm	Error	37	The network partition %1 of the server %2 has an error.	The network partition %1 of the server %2 has an error.	Check whether an error occurred in the network partition resolution resource.	o	o
nm	Error	38	The resource %1 of the server %2 is unknown.	The resource %1 of the server %2 is unknown.	Check the configuration data.	o	o
nm	Info	39	The server %1 canceled the pending failover.	The server %1 canceled the pending failover.	-	o	o
nm	Error	80	Cannot communicate with server %1.	Internal communication with server %1 is not possible.	Check that there is no error in the network adapter and the network is correctly connected.	o	o
nm	Info	81	Recovered from internal communication error with server %1.	Internal communication with server %1 has recovered from the abnormal status.	-	o	o
rc	Info	10	Activating group %1 has started.	The activation processing of group %1 has started.	-	o	o
rc	Info	11	Activating group %1 has completed.	The activation processing of group %1 has terminated.	-	o	o
rc	Error	12	Activating group %1 has failed.	The activation processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	15	Waiting for group %1 to start has started.	Waiting for the group to start has started.	-	o	o
rc	Info	16	Waiting for group %1 to start has been completed.	Waiting for the group to start has been normally completed.	-	o	o
rc	Error	17	Group start was canceled because waiting for group %1 to start was timed out.	Waiting for the group to start has timed out.	Check the status of the group waiting to start. If the group has not yet been started, re-perform the group operation after starting that group.	o	o
rc	Warning	18	Waiting for group %1 to start has timed out. However, group start continues.	Waiting for the group to start has timed out. However, group start continues.	-	o	o
rc	Info	20	Stopping group %1 has started.	The stop processing of group %1 has started.	-	o	o
rc	Info	21	Stopping group %1 has completed.	The stop processing of group %1 has terminated.	-	o	o
rc	Error	22	Stopping group %1 has failed.	The stop processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Warning	23	Server %1 is not in a condition to start group %2.	Server %1 cannot currently start group %2.	The server where a complete exclusion group is already active cannot start the group. Stop the complete exclusion group, and then re-execute the operation.	o	o
rc	Info	25	Waiting for group %1 to stop has started.	Waiting for the group to stop has started.	-	o	o
rc	Info	26	Waiting for group %1 to stop has been completed.	Waiting for the dependent group to stop has been normally completed.	-	o	o
rc	Error	27	Group stop has been canceled because waiting for group %1 to stop has timed out.	Waiting for the group to stop has timed out.	Check the status of the group waiting to stop. If the group has not yet been stopped, re-perform the group operation after stopping that group.	o	o
rc	Warning	28	Waiting for group %1 to stop has timed out. However, group stop continues.	Stop waiting has timed out. However, group stop continues.	-	o	o
rc	Info	30	Activating %1 resource has started.	The activation processing of resource %1 has started.	-		o
rc	Info	31	Activating %1 resource has completed.	The activation processing of resource %1 has terminated.	-		o
rc	Error	32	Activating %1 resource has failed.(%2 : %3)	The activation processing of resource %1 has failed.	See "Detailed information on activating and deactivating group resources".	o	o	o	o	o
rc	Info	40	Stopping %1 resource has started.	The stop processing of resource %1 has started.	-		o
rc	Info	41	Stopping %1 resource has completed.	The stop processing of resource %1 has terminated.	-		o
rc	Error	42	Stopping %1 resource has failed.(%2 : %3)	The stop processing of resource %1 has failed.	See "Detailed information on activating and deactivating group resources".	o	o	o	o	o
rc	Info	50	Moving group %1 has started.	The movement processing of group %1 has started.	-	o	o
rc	Info	51	Moving group %1 has completed.	The movement processing of group %1 has terminated.	-	o	o
rc	Error	52	Moving group %1 has failed.	The movement processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	55	Migrating group %1 has started.	The migration processing of group %1 has started.	-	o	o
rc	Info	56	Migrating group %1 has completed.	The migration processing of group %1 has terminated.	-	o	o
rc	Error	57	Migrating group %1 has failed.	The migration processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Warning	58	Server %1 is not in a condition to migrate group %2	The server %1 is not ready for the migration of the group %2.	Check the status of the migration destination server. No server name is output for %1 if there is no migration destination server.	o	o
rc	Info	60	Failover group %1 has started.	The failover processing of group %1 has started.	-	o	o
rc	Info	61	Failover group %1 has completed.	The failover processing of group %1 has terminated.	-	o	o
rc	Error	62	Failover group %1 has failed.	The failover processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Warning	63	Server %1 is not in a condition to move group %2.	Server %1 cannot currently move group %2.	Check the status of the movement destination server. If the movement destination server does not exist, the server name is not output to %1.	o	o
rc	Info	64	Server %1 has been set as the destination for the group %2 (reason: %3).	Server %1 has been set as the destination for the group %2 (reason: %3).	-	o	o
rc	Error	65	There is no appropriate destination for the group %1 (reason: %2).	There is no appropriate destination for the group %1 (reason: %2).	Check if any monitor resources detects an error on the other servers.	o	o
rc	Warning	66	Server %1 is not in a condition to start group %2 (reason: %3).	Server %1 is not in a condition to start group %2 (reason: %3).	Check if any monitor resource detects an error on the server.	o	o
rc	Info	67	Server %1 in the same server group (%2) has been set as the destination for the group %3.	The destination found in the same server group.	-	o	o
rc	Info	68	Server %1 not in the same server group (%2) has been set as the destination for the group %3.	The destination found in the other server group.	-	o	o
rc	Warning	69	Can not failover the group %1 because there is no appropriate destination in the same server group %2.	The destination not found in the same server group.	Check if other servers in the same server group are stopped.	o	o
rc	Info	70	Restarting group %1 has started.	The restart processing of group %1 has started.	-	o	o
rc	Info	71	Restarting group %1 has completed.	The restart processing of group %1 has terminated.	-	o	o
rc	Error	72	Restarting group %1 has failed.	The restart processing of group %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	74	Failback group %1 has started.	Failback group %1 has started.	-	o	o
rc	Info	75	Failback group %1 has completed.	Failback group %1 has been completed.	-	o	o
rc	Error	76	Failback group %1 has failed.	Failback group %1 has failed.	Take appropriate action according to the group resource message.	o	o
rc	Info	80	Restarting resource %1 has started.	The restart processing of resource %1 has started.	-	o	o
rc	Info	81	Restarting resource %1 has completed.	The restart processing of resource %1 has terminated.	-	o	o
rc	Error	82	Restarting resource %1 has failed.	The restart processing of resource %1 has failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	83	Starting a single resource %1.	Resource %1 is being started alone.	-	o	o
rc	Info	84	A single resource %1 has been started.	Starting resource %1 alone has been completed.	-	o	o
rc	Error	85	Failed to start a single resource %1.	Starting resource %1 alone has failed.	Troubleshoot according to the group resource message.	o	o
rc	Warning	86	Server %1 is not in a condition to start a single resource %2.	Server %1 cannot currently start resource %2 alone.	Check the server and group status.	o	o
rc	Info	87	Stopping a single resource %1.	Resource %1 is being stopped alone.	-	o	o
rc	Info	88	A single resource %1 has been stopped.	Stopping resource %1 alone has been completed.	-	o	o
rc	Error	89	Failed to stop a single resource %1.	Stopping resource %1 alone has failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	90	All the servers in the cluster were shut down.	All the servers have been shut down.	-	o	o
rc	Info	91	The server was shut down.	All the servers have been shut down.	-	o	o
rc	Warning	100	Restart count exceeded the maximum value %1. Final action of resource %2 will not be executed.	The restart count exceeded the maximum value %1. The final action of resource %2 will not be taken.	Troubleshoot according to the group resource message.	o	o
rc	Info	160	Script before final action upon activation failure in resource %1 started.	The script executed before the final action when an activation failure occurs for resource %1 has been started.	-	o	o
rc	Info	161	Script before final action upon activation failure in resource %1 completed.	The script executed before the final action when an activation failure occurs for resource %1 has been completed.	-	o	o
rc	Info	162	Script before final action upon deactivation failure in resource %1 started.	The script before the final action at deactivation failure in resource (%1) has started.	-	o	o
rc	Info	163	Script before final action upon deactivation failure in resource %1 completed.	The script before the final action at deactivation failure in resource (%1) has been completed.	-	o	o
rc	Error	180	Script before final action upon activation failure in resource %1 failed.	The script executed before the final action when an activation failure occurs for resource %1 has failed.	Check the cause of the script failure and take measures.	o	o
rc	Error	181	Script before final action upon deactivation failure in resource %1 failed.	The script executed before the final action when a deactivation failure occurs for resource %1 has failed.	Same as above	o	o
rc	Info	200	Resource(%1) will be reactivated since activating resource(%2) failed.	Resource %2 will now be reactivated because the activation processing of resource %2 failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	201	Group(%1) will be moved to server(%2) since activating resource(%3) failed.	Group %1 will now be moved to server %2 because resource %3 could not be activated.	Troubleshoot according to the group resource message.	o	o
rc	Info	202	Group(%1) will be stopped since activating resource(%2) failed.	Group %1 will now be stopped because resource %2 could not be activated.	Troubleshoot according to the group resource message.	o	o
rc	Info	203	Cluster daemon will be stopped since activating resource(%1) failed.	The EXPRESSCLUSTER server daemon will now be stopped because resource %1 could not be activated.	Troubleshoot according to the group resource message.	o	o
rc	Info	204	System will be halted since activating resource(%1) failed.	The OS will now be shut down because resource %1 could not be activated.	Troubleshoot according to the group resource message.	o	o
rc	Info	205	System will be rebooted since activating resource(%1) failed.	The OS will now be rebooted because resource %1 could not be activated.	Troubleshoot according to the group resource message.	o	o
rc	Info	206	Activating group(%1) will be continued since failover process failed.	The activation processing of group %1 will now be continued because the failover processing failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	220	Resource(%1) will be stopping again since stopping resource(%2) failed.	Resource %1 deactivation will now be retried because the deactivation processing of resource %2 failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	222	Group(%1) will be stopped since stopping resource(%2) failed.	Group %1 will now be stopped because resource %2 could not be deactivated.	Troubleshoot according to the group resource message.	o	o
rc	Info	223	Cluster daemon will be stopped since stopping resource(%1) failed.	The server daemon will now be stopped because resource %1 could not be deactivated.	Troubleshoot according to the group resource message.	o	o
rc	Info	224	System will be halted since stopping resource(%1) failed.	The OS will now be shut down because resource %1 could not be deactivated.	Troubleshoot according to the group resource message.	o	o
rc	Info	225	System will be rebooted since stopping resource(%1) failed.	The OS will now be rebooted because resource %1 could not be deactivated.	Troubleshoot according to the group resource message.	o	o
rc	Info	240	System panic by sysrq is requested since activating resource(%1) failed.	A system panic by sysrq has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	241	System reset by keepalive driver is requested since activating resource(%1) failed.	A system reset by the keepalive driver has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	242	System panic by keepalive driver is requested since activating resource(%1) failed.	A system panic by the keepalive driver has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	243	System reset by BMC is requested since activating resource(%1) failed.	A system reset by BMC has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	244	System power down by BMC is requested since activating resource(%1) failed.	A system power down by BMC has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	245	System power cycle by BMC is requested since activating resource(%1) failed.	A system power cycle by BMC has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	246	NMI send by BMC is requested since activating resource(%1) failed.	NMI transmission by BMC has been requested because resource %1 activation failed.	Troubleshoot according to the group resource message.	o	o
rc	Error	260	An attempt to panic system by sysrq due to failure of resource(%1) activation failed.	An attempt to panic the system was made by sysrq because resource %1 could not be activated, but this attempt failed.	Check whether the system is set up so that it can be used by sysrq.	o	o
rc	Error	261	An attempt to reset system by keepalive driver due to failure of resource(%1) activation failed.	An attempt to reset the system was made by the keepalive driver because resource %1 could not be activated, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rc	Error	262	An attempt to panic system by keepalive driver due to failure of resource(%1) activation failed.	An attempt to panic the system was made by the keepalive driver because resource %1 could not be activated, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rc	Error	263	An attempt to reset system by BMC due to failure of resource(%1) activation failed.	An attempt to reset the system was made by BMC because resource %1 could not be activated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	264	An attempt to power down system by BMC due to failure of resource(%1) activation failed.	An attempt to power down the system was made by BMC because resource %1 could not be activated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	265	An attempt to power cycle system by BMC due to failure of resource(%1) activation failed.	An attempt to power cycle the system was made by BMC because resource %1 could not be activated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	266	An attempt to send NMI by BMC due to failure of resource(%1) activation failed.	An attempt to send NMI was made by BMC because resource %1 could not be activated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Info	280	System panic by sysrq is requested since deactivating resource(%1) failed.	A system panic by sysrq has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	281	System reset by keepalive driver is requested since deactivating resource(%1) failed.	A system reset by the keepalive driver has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	282	System panic by keepalive driver is requested since deactivating resource(%1) failed.	A system panic by the keepalive driver has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	283	System reset by BMC is requested since deactivating resource(%1) failed.	A system reset by BMC has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	284	System power down by BMC is requested since deactivating resource(%1) failed.	A system power down by BMC has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	285	System power cycle by BMC is requested since deactivating resource(%1) failed.	A system power cycle by BMC has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Info	286	Sending NMI by BMC is requested since deactivating resource(%1) failed.	NMI transmission by BMC has been requested because resource %1 deactivation failed.	Troubleshoot according to the group resource message.	o	o
rc	Error	300	An attempt to panic system by sysrq due to failure of resource(%1) deactivation failed.	An attempt to panic the system was made by sysrq because resource %1 could not be deactivated, but this attempt failed.	Check whether the system is set up so that it can be used by sysrq.	o	o
rc	Error	301	An attempt to reset system by keepalive driver due to failure of resource(%1) deactivation failed.	An attempt to reset the system was made by the keepalive driver because resource %1 could not be deactivated, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rc	Error	302	An attempt to panic system by keepalive driver due to failure of resource(%1) deactivation failed.	An attempt to panic the system was made by the keepalive driver because resource %1 could not be deactivated, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rc	Error	303	An attempt to reset system by BMC due to failure of resource(%1) deactivation failed.	An attempt to reset the system was made by BMC because resource %1 could not be deactivated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	304	An attempt to power down system by BMC due to failure of resource(%1) deactivation failed.	An attempt to power down the system was made by BMC because resource %1 could not be deactivated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	305	An attempt to power cycle system by BMC due to failure of resource(%1) deactivation failed.	An attempt to power cycle the system was made by BMC because resource %1 could not be deactivated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	306	An attempt to send NMI by BMC due to failure of resource(%1) deactivation failed.	An attempt to send NMI was made by BMC because resource %1 could not be deactivated, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rc	Error	340	Group start has been canceled because waiting for group %1 to start has failed.	An error has occurred while waiting for the group to start.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rc	Info	400	The status of the regular check for a forced stop returned to normal.	The status of the regular check for a forced stop returned to normal.	-	o	o
rc	Error	401	The regular check for a forced stop detected an abnormality.	The regular check for a forced stop detected an abnormality.	The forced-stop function may not be working normally. Identify the cause.	o	o
rc	Error	402	The request for forcibly stopping the server has been timed out.	The request for forcibly stopping the server has been timed out.	Identify the cause of the timeout and take measures.	o	o
rc	Info	403	The request for forcibly stopping the server will be retried.	The request for forcibly stopping the server will be retried.	-	o	o
rc	Error	404	The check of forcibly stopping the server has been timed out.	The check of forcibly stopping the server has been timed out.	Identify the cause of the timeout and take measures.	o	o
rc	Info	405	The check of forcibly stopping the server will be retried.	The check of forcibly stopping the server will be retried.	-	o	o
rc	Warning	441	Waiting for group %1 to stop has failed. However, group stop continues.	An error has occurred while waiting for the group to stop.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rc	Warning	500	Since there is no other normally running server, the final action for an activation error of group resource %1 was suppressed.	Suppression of final action for activation error.	-	o	o
rc	Warning	501	Since there is no other normally running server, the final action for a deactivation error of group resource %1 was suppressed.	Suppression of final action for deactivation error.	-	o	o
rc	Warning	510	Cluster action is disabled.	The cluster action is disabled.	-	o	o
rc	Warning	511	Ignored the automatic start of groups because automatic group startup is disabled.	Being disabled, automatic group startup is ignored.	-	o	o
rc	Warning	512	Ignored the recovery action in resource activation because recovery action caused by group resource activation error is disabled.	Being disabled, the resource recovery action is ignored when a group resource activation error occurs.	-	o	o
rc	Warning	513	Ignored the recovery action in resource deactivation because recovery action caused by group resource deactivation error is disabled.	Being disabled, the resource recovery action is ignored when a group resource deactivation error occurs.	-	o	o
rc	Warning	514	Cluster action is set disabled.	The cluster action is disabled.	-	o	o
rc	Warning	515	Cluster action is set enabled.	The cluster action is enabled.	-	o	o
rc	Warning	516	Ignored the group failover because failover for a server failure is disabled.	The group failover was ignored because failover for a server failure has been disabled.	-	o	o
rm	Info	1	Monitoring %1 has started.	%1 monitoring has started.	-	o	o
rm	Info	2	Monitoring %1 has stopped.	%1 monitoring has stopped.	-	o	o
rm	Info	3	%1 is not monitored by this server.	%1 is not monitored by this server.	-	o	o
rm	Warning	4	Warn monitoring %1. (%2 : %3)	There is a warning about %1 monitoring.	See "Details about monitor resource errors". If a monitor resource is preparing for monitoring, the following message may be set in (). No action is required for this message. (100 : not ready for monitoring.)	o	o
rm	Warning	5	The maximum number of monitor resources has been exceeded. (registered resource is %1)	The maximum number of monitor resources has been exceeded.	Check the configuration data by using the Cluster WebUI.	o	o
rm	Warning	6	Monitor configuration of %1 is invalid. (%2 : %3)	The monitor configuration of %1 is invalid.	Check the configuration data by using the Cluster WebUI.	o	o
rm	Error	7	Failed to start monitoring %1.	%1 monitoring could not be started.	Memory or OS resources may not be sufficient. Check them.	o	o	o	o	o
rm	Error	8	Failed to stop monitoring %1.	%1 monitoring could not be stopped.	Memory or OS resources may not be sufficient. Check them.	o	o
rm	Error	9	Detected an error in monitoring %1. (%2 : %3)	An error was detected during %1 monitoring.	See "Details about monitor resource errors". If a monitoring timeout is detected, the following message is specified in the parentheses: (99 : Monitor was timeout.) If Dummy Failure is enabled, the following message is set in (). No action is needed in the latter case. (201 : Monitor failed for failure verification.) If no response is returned from a monitor resource for a certain period of time, the following message is set in (). (202: couldn't receive reply from monitor resource in time.)	o	o	o	o	o
rm	Info	10	%1 is not monitored.	%1 is not being monitored.	-	o	o
rm / mm	Info	12	Recovery target %1 has stopped because an error was detected in monitoring %2.	Recovery target %1 has been stopped because an error was detected during %2 monitoring.	-	o	o
rm / mm	Info	13	Recovery target %1 has restarted because an error was detected in monitoring %2.	Recovery target %1 has been restarted because an error was detected during %2 monitoring.	-	o	o
rm / mm	Info	14	Recovery target %1 failed over because an error was detected in monitoring %2.	Recovery target %1 has been failed over because an error was detected during %2 monitoring.	-	o	o
rm / mm	Info	15	Stopping the cluster has been required because an error was detected in monitoring %1.	Stopping the server has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Info	16	Stopping the system has been required because an error was detected in monitoring %1.	Stopping the system has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Info	17	Rebooting the system has been required because an error was detected in monitoring %1.	Rebooting the system has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	18	Attempted to stop the recovery target %1 due to the error detected in monitoring %2, but failed.	An attempt to stop recovery target %1 was made because an error was detected during %2 monitoring, but this attempt failed.	Check the status of resource %1.	o	o
rm / mm	Error	19	Attempted to restart the recovery target %1 due to the error detected in monitoring %2, but failed.	An attempt to restart recovery target %1 was made because an error was detected during %2 monitoring, but this attempt failed.	Check the status of resource %1.	o	o
rm / mm	Error	20	Attempted to fail over %1 due to the error detected in monitoring %2, but failed.	An attempt to fail over recovery target %1 was made because an error was detected during %2 monitoring, but this attempt failed.	Check the status of resource %1.	o	o
rm / mm	Error	21	Attempted to stop the cluster due to the error detected in monitoring %1, but failed.	An attempt to stop the server was made because an error was detected during %1 monitoring, but this attempt failed.	Memory or OS resources may not be sufficient. Check them.	o	o
rm / mm	Error	22	Attempted to stop the system due to the error detected in monitoring %1, but failed.	An attempt to stop the system was made because an error was detected during %1 monitoring, but this attempt failed.	Memory or OS resources may not be sufficient. Check them.	o	o
rm / mm	Error	23	Attempted to reboot the system due to the error detected in monitoring %1, but failed.	An attempt to reboot the system was made because an error was detected during %1 monitoring, but this attempt failed.	Memory or OS resources may not be sufficient. Check them.	o	o
rm	Error	24	The group of %1 resource is unknown.	The group of resource %1 is unknown.	The configuration data may be incorrect. Check them.	o	o
rm / mm	Warning	25	Recovery will not be executed since the recovery target %1 is not active.	Recovery will not be performed because recovery target %1 is inactive.	-	o	o
rm / mm	Info	26	%1 status changed from error to normal.	%1 monitoring has changed from "error" to "normal".	-	o	o
rm / mm	Info	27	%1 status changed from error or normal to unknown.	%1 monitoring has changed from "error" or "normal" to "unknown".	Memory or OS resources may not be sufficient. Check them.	o	o
rm	Error	28	Initialization error of monitor process. (%1 : %2)	A monitor process initialization error occurred.	Memory or OS resources may not be sufficient. Check them.	o	o
rm	Info	29	Monitoring %1 was suspended.	%1 monitoring has been suspended.	-	o	o
rm	Info	30	Monitoring %1 was resumed.	%1 monitoring has been resumed.	-	o	o
rm	Info	31	All monitors were suspended.	All monitors were suspended.	-	o	o
rm	Info	32	All monitors were resumed.	All monitors were resumed.	-	o	o
rm / mm	Info	35	System panic by sysrq has been required because an error was detected in monitoring %1.	A system panic by sysrq has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	36	Attempted to panic system by sysrq due to the error detected in monitoring %1, but failed.	An attempt to panic the system was made by sysrq because an error was detected during %1 monitoring, but this attempt failed.	Check whether the system is set up so that it can be used by sysrq.	o	o
rm / mm	Info	37	System reset by keepalive driver has been required because an error was detected in monitoring %1.	A system reset by the keepalive driver has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	38	Attempted to reset system by keepalive driver due to the error detected in monitoring %1, but failed.	An attempt to reset the system was made by the keepalive driver because an error was detected during %1 monitoring, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rm / mm	Info	39	System panic by keepalive driver has been required because an error was detected in monitoring %1.	A system panic by the keepalive driver has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	40	Attempted to panic system by keepalive driver due to the error detected in monitoring %1, but failed.	An attempt to panic the system was made by the keepalive driver because an error was detected during %1 monitoring, but this attempt failed.	Check whether the keepalive driver can be used in this environment.	o	o
rm / mm	Info	41	System reset by BMC has been required because an error was detected in monitoring %1.	A system reset by BMC has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	42	Attempted to reset system by BMC due to the error detected in monitoring %1, but failed.	An attempt to reset the system was made by BMC because an error was detected during %1 monitoring, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rm / mm	Info	43	System power down by BMC has been required because an error was detected in monitoring %1.	A system power down by BMC has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	44	Attempted to power down system by BMC due to the error detected in monitoring %1, but failed.	An attempt to power down the system was made by BMC because an error was detected during %1 monitoring, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rm / mm	Info	45	System power cycle by BMC has been required because an error was detected in monitoring %1.	A system power cycle by BMC has been requested because an error was detected during %1 monitoring.	-	o	o
rm / mm	Error	46	Attempted to power cycle system by BMC due to the error detected in monitoring %1, but failed.	An attempt to power cycle the system was made by BMC because an error was detected during %1 monitoring, but this attempt failed.	Check whether the ipmitool command can be used.	o	o
rm / mm	Info	47	NMI send by BMC has been required because an error was detected in monitoring %1.	NMI of the system by BMC has been required because an error was detected in monitoring %1.	-	o	o
rm / mm	Error	48	Attempted to send NMI by BMC due to the error detected in monitoring %1, but failed.	Attempted to NMI of the system by BMC due to the error detected in monitoring %1, but failed.	Check if the ipmitool command can be used.	o	o
rm	Info	49	%1 status changed from warning to normal.	%1 monitoring has changed from "warning" to "normal".	-	o	o
rm	Error	57	Stopping the cluster is required since license (%1) is invalid.	Stopping the server has been requested because the license is invalid.	Register a valid license.	o	o	o	o	o
rm	Error	58	Stopping the cluster due to invalid license (%1) failed.	The server could not be stopped because the license is invalid.	Register a valid license.	o	o
rm	Warning	71	Detected a monitor delay in monitoring %1. (timeout=%2 actual-time=%3 delay warning rate=%4)	A monitoring delay was detected during %1 monitoring. The current timeout value is %2 (tick count). The actual measurement value at delay detection has reached %3 (tick count), exceeding the delay warning rate %4 (%).	Check the load on the server where monitoring delay was detected and reduce the load. If monitoring timeouts are detected, the monitoring timeout time must be extended.	o	o
rm	Warning	72	%1 could not Monitoring.	%1 could not perform monitoring.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rm / mm	Info	81	Script before %1 upon failure in monitor resource %2 started.	The script before %1 in monitor resource %2 has been started.	-	o	o
rm / mm	Info	82	Script before %1 upon failure in monitor resource %2 completed.	The script before %1 in monitor resource %2 has been complete.	-	o	o
rm / mm	Error	83	Script before %1 upon failure in monitor resource %2 failed.	The script before %1 in monitor resource %2 has failed.	Check the cause of the script failure and take measures.	o	o
rm	Warning	100	Restart count exceeded the maximum of %1. Final action of monitoring %2 will not be executed.	The final action of %2 has not been executed because restart count exceeded the maximum value %1.	-	o	o
rm	Warning	120	The virtual machine (%1) has been migrated by an external operation.	The virtual machine managed by the resource %1 has been migrated by an external operation.	-	o	o
rm	Warning	121	The virtual machine (%1) has been started by an external operation.	The virtual machine managed by the resource %1 has been started by an external operation.	-	o	o
rm	Info	130	Collecting detailed information was triggered by error detection when monitoring monitor resource $1.	Collecting detailed information was triggered by error detection when monitoring monitor resource $1. The timeout time is %2 seconds.	-	o	o
rm	Info	131	The collection of detailed information triggered by error detection when monitoring monitor resource $1 has completed.	The collection of detailed information triggered by error detection when monitoring monitor resource $1 has completed.	-	o	o
rm	Warning	132	The collection of detailed information triggered by error detection when monitoring monitor resource $1 has failed.	The collection of detailed information triggered by error detection when monitoring monitor resource $1 has failed.	-	o	o
rm	Info	140	Process %1 has started.	Process %1 has started.	-	o	o
rm	Warning	141	Process %1 has restarted.	Process %1 has restarted.	-	o	o
rm	Warning	142	Process %1 does not exist.	Process %1 does not exist.	-	o	o
rm	Error	143	Process %1 was restarted %2 times, but terminated abnormally.	Process %1 was restarted %2 times, but terminated abnormally.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rm	Error	150	The cluster is stopped since process %1 was terminated abnormally.	The cluster is stopped since process %1 was terminated abnormally.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rm	Error	151	The server is shut down since process %1 was terminated abnormally.	The server is shut down since process %1 was terminated abnormally.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rm	Error	152	The server is restarted since process %1 was terminated abnormally.	The server is restarted since process %1 was terminated abnormally.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
rm	Error	160	Monitor resource %1 cannot be controlled since the license is invalid.	Monitor resource %1 cannot be controlled since the license is invalid.	Register a valid license.	o	o
rm	Info	170	Recovery script has been executed since an error was detected in monitoring %1.	Recovery script has been executed since an error was detected in monitoring %1.	-	o	o
rm	Error	171	An attempt was made to execute the recovery script due to a %1 monitoring failure, but failed.	An attempt was made to execute the recovery script due to a %1 monitoring failure, but failed.	Check the cause of the recovery script failure and take appropriate action.	o	o
rm	Info	180	Dummy Failure of monitor resource %1 is enabled.	Dummy Failure of monitor resource %1 is enabled.	-	o	o
rm	Info	181	Dummy Failure of monitor resource %1 is disabled.	Dummy Failure of monitor resource %1 is disabled.	-	o	o
rm	Info	182	Dummy Failure of all monitor will be enabled.	Dummy Failure of all monitor will be enabled.	-	o	o
rm	Info	183	Dummy Failure of all monitor will be disabled.	Dummy Failure of all monitor will be disabled.	-	o	o
rm	Warning	184	An attempt was made to enable Dummy Failure of monitor resource %1, but failed.	An attempt was made to enable Dummy Failure of monitor resource %1, but failed.	Check whether monitor resource %1 corresponds to Dummy Failure.	o	o
rm	Warning	185	An attempt was made to disable Dummy Failure of monitor resource %1, but failed.	An attempt was made to disable Dummy Failure of monitor resource %1, but failed.	Check whether monitor resource %1 corresponds to Dummy Failure.	o	o
rm	Info	190	Recovery action caused by monitor resource error is disabled.	Recovery action caused by monitor resource error is disabled.	-	o	o
rm	Info	191	Recovery action caused by monitor resource error is enabled.	Recovery action caused by monitor resource error is enabled.	-	o	o
rm	Warning	192	Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled.	Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled.	-	o	o
rm	Warning	193		Recovery action at timeout occurrence was disabled, so the recovery action of monitor %1 was not executed.		o	o
rm	Warning	200	Since there is no other normally running server, the final action(%1) for the error detection of monitor resource %2 was suppressed.	Suppression of final action for error detection.	-	o	o
rm	Warning	220	Recovery will not be executed since any recovery target is not active.	Recovery will not be executed since any recovery target is not active.	-	o	o
rm	Warning	221	Recovery will not be executed because the group that is set for the recovery target is not active.	Recovery will not be executed because the group that is set for the recovery target is not active.	-	o	o
mm	Info	901	Message monitor has been started.	Message monitor (external linkage monitor module) has been started.	-	o	o
mm	Error	902	Failed to initialize message monitor. (%1 : %2)	Message monitor (external linkage monitor module) could not be initialized.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
mm	Warning	903	An error of %1 type and %2 device has been detected. (%3)	External error %3 of category %1 and keyword %2 has been received.	-	o	o
mm	Error	905	An error has been detected in monitoring %1. (%2)	An error was detected in monitor resource %1 monitoring.	Take appropriate action according to the %2 message.	o	o	o	o	o
mm	Error	906	Message monitor was terminated abnormally.	Message monitor (external linkage monitor module) has been terminated abnormally.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
mm	Error	907	Failed to execute action. (%1)	Executing recovery action has failed.	Check the following possible causes: memory shortage or OS resource insufficiency.	o	o
mm	Info	908	The system will be stopped.	The OS will be shut down.	-	o	o
mm	Info	909	The cluster daemon will be stopped.	The cluster will be stopped.	-	o	o
mm	Info	910	The system will be rebooted.	The OS will be rebooted.	-	o	o
mm	Info	911	Message monitor will be restarted.	Message monitor (external linkage monitor module) will be restarted.	-	o	o
mm	Info	912	Received a message by SNMP Trap from external. (%1 : %2)	Received a message by SNMP Trap from external.	-	o	o
trnsv	Error	1	There was a notification from external (IP=%1), but it was denied.	The notification from %1 was received, but it was denied.	-	o	o
trnsv	Info	10	There was a notification (%1) from external (IP=%2).	The notification (%1) from %2 was received.	-	o	o
trnsv	Info	20	Recovery action (%1) of monitoring %2 has been executed because a notification arrived from external.	Recovery action when an error is detected (%1) of the monitor resource %2 has been executed due to an notification from external arrived.	-	o	o
trnsv	Info	21	Recovery action (%1) of monitoring %2 has been completed.	Execution of recovery action when an error is detected (%1) of the monitor resource %2 succeeded.	-	o	o
trnsv	Error	22	Attempted to recovery action (%1) of monitoring %2, but it failed.	Executed recovery action when an error is detected (%1) of the monitor resource %2, but it failed.	Check if recovery action when an error is detected is executable.	o	o
trnsv	Info	30	Action (%1) has been completed.	Execution of action (%1) succeeded.	-	o	o
trnsv	Error	31	Attempted to execute action (%1), but it failed.	Executed action (%1), but it failed.	Check if recovery action when an error is detected is executable.	o	o
trnsv	Info	40	Script before action of monitoring %1 has been executed.	Script before action when an error is detected of the monitor resource (%1) has been executed.	-	o
trnsv	Info	41	Script before action of monitoring %1 has been completed.	Execution of script before action when an error is detected of the monitor resource (%1) succeeded.	-	o
trnsv	Error	42	Attempted to execute script before action of monitoring %1, but it failed.	Executed script before action when an error is detected of the monitor resource (%1), but it failed.	Check if script before action when an error is detected is executable.	o
lanhb	Warning	71	Heartbeats sent from HB resource %1 of server %2 are delayed.(timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred in the heartbeat from HB resource %1 of server %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on server %2 and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.	o	o
lanhb	Warning	72	Heartbeats sent from HB resource %1 are delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred during the heartbeat transmission of HB resource %1. The transmission destination server is %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on the server to which the delay warning was issued and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.
lanhb	Warning	73	Heartbeats received by HB resource %1 are delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred during the heartbeat reception of HB resource %1. The transmission source server is %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on the server to which the delay warning was issued and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.
lankhb	Warning	71	Heartbeats sent from HB resource %1 of server %2 are delayed.(timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred in the heartbeat from HB resource %1 of server %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on server %2 and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.	o	o
lankhb	Warning	73	Heartbeats received from HB resource %1 is delayed.(timeout=%2*%3 actual-time=%4 delay warning rate=%5)	A delay occurred during the heartbeat reception of HB resource %1. The transmission source server is %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on the server to which the delay warning was issued and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.
diskhb	Error	10	Device(%1) of resource(%2) does not exist.	The specified device does not exist.	Check the configuration data.	o	o
diskhb	Error	11	Device(%1) of resource(%2) is not a block device.	The specified device does not exist.	Check the configuration data.	o	o
diskhb	Error	12	Raw device(%1) of resource(%2) does not exist.	The specified device does not exist.	Check the configuration data.	o	o
diskhb	Error	13	Binding device(%1) of resource(%2) to raw device(%3) failed.	The specified device does not exist.	Check the configuration data.	o	o
diskhb	Error	14	Raw device(%1) of resource(%2) has already been bound to other device.	Raw device %1 of resource %2 is bound to another device.	Specify an unused raw device.	o	o
diskhb	Error	15	File system exists on device(%1) of resource(%2).	A file system exists in device %1 of resource %2.	To use device %1, delete the file system.	o	o
diskhb	Info	20	Resource %1 recovered from initialization error.	Resource %1 has recovered from the initialization error.	-	o	o
diskhb	Warning	71	Heartbeats sent from HB resource %1 of server %2 are delayed.(timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred in the heartbeat from HB resource %1 of server %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on server %2 and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.	o	o
diskhb	Warning	72	Heartbeat write of HB resource %1 is delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6).	A delay occurred during the heartbeat write of HB resource %1. The write destination server is %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on the server to which the delay warning was issued and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.
diskhb	Warning	73	Heartbeat read of HB resource %1 is delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6)	A delay occurred during the heartbeat read of HB resource %1. The read source server is %2. The current timeout value is "%3 (seconds) x %4 (ticks per second)". The actual measurement value when the delay occurred became %5 (ticks), exceeding the delay warning percentage %6 (%).	Check the load on the server to which the delay warning was issued and reduce the load. If an HB timeout occurs, the HB timeout time must be extended.
monp	Error	1	An error occurred when initializing monitored process %1. (status=%2)	An initialization error occurred in monitored process %1.	Memory or OS resources might not be sufficient, or the configuration data might be inconsistent. Check them. If the configuration data is not registered, the process message below is output. This message output, however, does not indicate a problem. + mdagnt + webmgr + webalert	o	o
monp	Error	2	Monitor target process %1 terminated abnormally. (status=%2)	Monitor target process %1 terminated abnormally.	Memory or OS resources may not be sufficient. Check them.	o	o
monp	Info	3	Monitor target process %1 will be restarted.	Monitor target process %1 will now be restarted.	-	o	o
monp	Info	4	The cluster daemon will be stopped since the monitor target process %1 terminated abnormally.	The server will now be stopped because monitor target process %1 terminated abnormally.	-	o	o
monp	Error	5	Attempted to stop the cluster daemon, but failed.	Stopping the server has failed.	The server might not be running or memory or OS resources might not be sufficient. Check them.	o	o
monp	Info	6	The system will be stopped since the monitor target process %1 terminated abnormally.	The system will now stop because monitor target process %1 terminated abnormally.	-	o	o
monp	Error	7	Attempted to stop the system, but failed. (status=%#x)	Stopping the system has failed.	The server might not be running or memory or OS resources might not be sufficient. Check them.	o	o
monp	Info	8	System will be rebooted since monitor target process %1 terminated abnormally.	The system will now be rebooted because monitor target process %1 terminated abnormally.	-	o	o
monp	Error	9	Attempted to reboot the system, but failed. (status=%#x)	Rebooting the system has failed.	The server might not be running or memory or OS resources might not be sufficient. Check them.	o	o
cl	Info	1	There was a request to start %1 from the %2.	A request to start %1 has been issued from %2.	-	o	o
cl	Info	2	There was a request to stop %1 from the %2.	A request to stop %1 has been issued from %2.	-	o	o
cl	Info	3	There was a request to suspend %1 from the %2.	A request to suspend %1 has been issued from %2.	-	o	o
cl	Info	4	There was a request to resume %s from the %s.	A request to resume %1 has been issued from %2.	-	o	o
cl	Error	11	A request to start %1 failed(%2).	A request to start %1 has failed.	Check the server status.	o	o
cl	Error	12	A request to stop %1 failed(%2).	A request to stop %1 has failed.	Check the server status.	o	o
cl	Error	13	A request to suspend %1 failed(%2).	A request to suspend %1 has failed.	Check the server status.	o	o
cl	Error	14	A request to resume %1 failed(%2).	A request to resume %1 has failed.	Check the server status.	o	o
cl	Error	15	A request to %1 cluster failed on some servers(%2).	Request %1 has failed on some servers.	Check the server statuses.	o	o
cl	Error	16	A request to start %1 failed on some servers(%2).	Starting %1 failed on some servers.	Check the status of %1.	o	o
cl	Error	17	A request to stop %1 failed on some servers(%2).	Stopping %1 failed on some servers.	Check the status of %1.	o	o
cl	Warning	18	Automatic start is suspended because the cluster service was not stopped according to the normal procedure.	Automatic start has been suspended since Automatic startup after the system down was not set.	To start the cluster service, use the Cluster WebUI or clpcl command.	o	o
cl	Warning	20	A request to start %1 failed because cluster is running(%2).	Starting %1 has failed since the cluster is running.	Check the status of the cluster.	o	o
cl	Warning	21	A request to stop %1 failed because cluster is running(%2).	Stopping %1 has failed since the cluster is running.	Check the status of the cluster.	o	o
mail	Error	1	The license is not registered. (%1)	Purchase and register the license.	-	o	o
mail	Error	2	The trial license has expired in %1. (%2)	Register a valid license.	-	o	o
mail	Error	3	The registered license is invalid. (%1)	Register a valid license.	-	o	o
mail	Error	4	The registered license is unknown. (%1)	Register a valid license.	-	o	o
mail	Error	5	mail failed(%s).(SMTP server: %s)	Mail reporting has failed.	Check if an error has occurred on the SMTP server, or a trouble occurred in communicating with the SMTP server.	o	o
mail	Info	6	mail successed.(SMTP server: %s)	mail succeed.	-	o	o
userw	Warning	1	Detected a monitor delay in monitoring %1. (timeout=%2*%3 actual-time=%4 delay warning rate=%5)	A monitoring delay was detected during %1 monitoring. The current timeout value is "%2 (seconds) x %3 (ticks per second)". The actual measurement value when the delay was detected became %4 (ticks), exceeding the delay warning percentage %5 (%).	-	o	o
vipw	Warning	1	Detected a monitor delay in monitoring %1. (timeout=%2*%3 actual-time=%4 delay warning rate=%5)	A monitoring delay was detected during %1 monitoring. The current timeout value is "%2 (seconds) x %3 (ticks per second)". The actual measurement value when the delay was detected became %4 (ticks), exceeding the delay warning percentage %5 (%).	-	o	o
ddnsw	Warning	1	Detected a monitor delay in monitoring %1. (timeout=%2*%3 actual-time=%4 delay warning rate=%5)	A monitoring delay was detected during %1 monitoring. The current timeout value is "%2 (seconds) x %3 (ticks per second)". The actual measurement value when the delay was detected became %4 (ticks), exceeding the delay warning percentage %5 (%).	-	o	o
apisv	Info	1	There was a request to stop cluster from the %1(IP=%2).	A request to stop the server has been issued from %1.	-	o	o
apisv	Info	2	There was a request to shutdown cluster from the %1(IP=%2).	A request to shut down the server has been issued from %1.	-	o	o
apisv	Info	3	There was a request to reboot cluster from the %1(IP=%2).	A request to reboot the server has been issued from %1.	-	o	o
apisv	Info	4	There was a request to suspend cluster from the %1(IP=%2).	A request to suspend the server has been issued from %1.	-	o	o
apisv	Info	10	There was a request to stop server from the %1(IP=%2).	A request to stop the server has been issued from %1.	-	o	o
apisv	Info	11	There was a request to shutdown server from the %1(IP=%2).	A request to shut down the server has been issued from %1.	-	o	o
apisv	Info	12	There was a request to reboot server from the %1(IP=%2).	A request to reboot the server has been issued from %1.	-	o	o
apisv	Info	30	There was a request to start group(%1) from the %2(IP=%3).	A request to start group %1 has been issued from %2.	-	o	o
apisv	Info	31	There was a request to start all groups from the %1(IP=%2).	A request to start all groups has been issued from %1.	-	o	o
apisv	Info	32	There was a request to stop group(%1) from the %2(IP=%3).	A request to stop group %1 has been issued from %2.	-	o	o
apisv	Info	33	There was a request to stop all groups from the %1(IP=%2).	A request to stop all groups has been issued from %1.	-	o	o
apisv	Info	34	There was a request to restart group(%1) from the %2(IP=%3).	A request to restart group %1 has been issued from %2.	-	o	o
apisv	Info	35	There was a request to restart all groups from the %1(IP=%2).	A request to restart all groups has been issued from %1.	-	o	o
apisv	Info	36	There was a request to move group(%1) from the %2(IP=%3).	A request to move group %1 has been issued from %2.	-	o	o
apisv	Info	37	There was a request to move group from the %1(IP=%2).	A request to move a group has been issued from %1.	-	o	o
apisv	Info	38	There was a request to failover group(%1) from the %2(IP=%3).	A request to fail over group %1 has been issued from %2.	-	o	o
apisv	Info	39	There was a request to failover group from the %1(IP=%2).	A request to fail over a group has been issued from %1.	-	o	o
apisv	Info	40	There was a request to migrate group(%1) from the %2(IP=%3).	A request to migrate group %1 has been issued from %2.	-	o	o
apisv	Info	41	There was a request to migrate group from the %1(IP=%2).	A request to migrate a group has been issued from %2.	-	o	o
apisv	Info	42	There was a request to failover all groups from the %1(IP=%2).	A request to provide failover for all groups was issued from %2.	-	o	o
apisv	Info	43	There was a request to cancel waiting for the dependence destination group of group the %1 was issued from %2.	A request to cancel waiting for the dependence destination group of group %1 was issued from %2.	-	o	o
apisv	Info	50	There was a request to start resource(%1) from the %2(IP=%3).	A request to start resource %1 has been issued from %2.	-	o	o
apisv	Info	51	There was a request to start all resources from the %1(IP=%2).	A request to start all resources has been issued from %1.	-	o	o
apisv	Info	52	There was a request to stop resource(%1) from the %2(IP=%3).	A request to stop resource %1 has been issued from %2.	-	o	o
apisv	Info	53	There was a request to stop all resources from the %1(IP=%2).	A request to stop all resources has been issued from %1.	-	o	o
apisv	Info	54	There was a request to restart resource(%1) from the %2(IP=%3).	A request to restart resource %1 has been issued from %2.	-	o	o
apisv	Info	55	There was a request to restart all resources from the %1(IP=%2).	A request to restart all resources has been issued from %1.	-	o	o
apisv	Info	60	There was a request to suspend monitor resources from the %1(IP=%2).	A request to suspend monitor resources has been issued from %1.	-	o	o
apisv	Info	61	There was a request to resume monitor resources from the %1(IP=%2).	A request to resume monitor resources has been issued from %1.	-	o	o
apisv	Info	62	There was a request to enable Dummy Failure of monitor resources from the %1(IP=%2).	A request to enable Dummy Failure of monitor resource was issued from %1.	-	o	o
apisv	Info	63	There was a request to disable Dummy Failure of monitor resources from the %1(IP=%2).	A request to disable Dummy Failure of monitor resource was issued from %1.	-	o	o
apisv	Error	101	A request to stop cluster was failed(0x%08x).	A request to stop the server has failed.	Check the server status.	o	o
apisv	Error	102	A request to shutdown cluster was failed(0x%08x).	A request to shut down the server has failed.	Check the server status.	o	o
apisv	Error	103	A request to reboot cluster was failed(0x%08x).	A request to reboot the server has failed.	Check the server status.	o	o
apisv	Error	104	A request to suspend cluster was failed(0x%08x).	A request to suspend the server has failed.	Check the server status.	o	o
apisv	Error	110	A request to stop server was failed(0x%08x).	A request to stop the server has failed.	Check the status of the server.	o	o
apisv	Error	111	A request to shutdown server was failed(0x%08x).	A request to shut down the server has failed.	Check the status of the server.	o	o
apisv	Error	112	A request to reboot server was failed(0x%08x).	A request to reboot the server has failed.	Check the status of the server.	o	o
apisv	Error	113	A request to server panic was failed(0x%08x).	Server panic has failed.	Check the status of the server.	o	o
apisv	Error	114	A request to server reset was failed(0x%08x).	Server reset has failed.	Check the status of the server.	o	o
apisv	Error	115	A request to server sysrq was failed(0x%08x).	SYSRQ panic has failed.	Check the status of the server.	o	o
apisv	Error	116	A request to KA RESET was failed(0x%08x).	Keepalive reset has failed.	Check the status of the server.	o	o
apisv	Error	117	A request to KA PANIC was failed(0x%08x).	Keepalive panic has failed.	Check the status of the server.	o	o
apisv	Error	118	A request to BMC RESET was failed(0x%08x).	BMC reset has failed.	Check the status of the server.	o	o
apisv	Error	119	A request to BMC PowerOff was failed(0x%08x).	BMC power-off has failed.	Check the status of the server.	o	o
apisv	Error	120	A request to BMC PowerCycle was failed(0x%08x).	BMC power cycle has failed.	Check the status of the server.	o	o
apisv	Error	121	A request to BMC NMI was failed(0x%08x).	BMC NMI has failed.	Check the status of the server.	o	o
apisv	Error	130	A request to start group(%1) was failed(0x%08x).	A request to start group %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful group start.	o	o
apisv	Error	131	A request to start all groups was failed(0x%08x).	A request to start all groups has failed.	Same as above	o	o
apisv	Error	132	A request to stop group(%1) was failed(0x%08x).	A request to stop group %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful group stop.	o	o
apisv	Error	133	A request to stop all groups was failed(0x%08x).	A request to stop all groups has failed.	Same as above	o	o
apisv	Error	134	A request to restart group(%1) was failed(0x%08x).	Restarting group (%1) has failed.	Take appropriate action according to the group stop failure message issued by rc.	o	o
apisv	Error	135	A request to restart all groups was failed(0x%08x).	Restarting all groups has failed.	Same as above.	o	o
apisv	Error	136	A request to move group(%1) was failed(0x%08x).	A request to move group %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful group movement.	o	o
apisv	Error	137	A request to move all groups was failed(0x%08x).	Moving all groups has failed.	Same as above.	o	o
apisv	Error	138	A request to failover group(%1) was failed(0x%08x).	A request to fail over group %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful group failover.	o	o
apisv	Error	139	A request to failover group was failed(0x%08x).	A request to fail over all groups has failed.	Same as above	o	o
apisv	Error	140	A request to migrate group(%1) was failed(0x%08x).	Migration of group (%1) has failed.	Take appropriate action according to the group failover failure message issued by rc.	o	o
apisv	Error	141	A request to migrate all groups was failed(0x%08x).	Migration of all groups has failed.	Same as above.	o	o
apisv	Error	142	A request to failover all groups was failed(0x%08x).	Failover for all groups has failed.	Same as above.	o	o
apisv	Error	143	A request to cancel waiting for the dependency destination group of group %1 has failed(0x%08x).	Canceling waiting for the dependency destination group of group %1 has failed.	Same as above.	o	o
apisv	Error	150	A request to start resource(%1) was failed(0x%08x).	A request to start resource %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful resource start.	o	o
apisv	Error	152	A request to stop resource(%1) was failed(0x%08x).	A request to stop resource %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful resource stop.	o	o
apisv	Error	154	A request to restart resource(%1) was failed(0x%08x).	A request to restart resource %1 has failed.	Take appropriate action according to the message output by rc indicating the unsuccessful resource restart.	o	o
apisv	Error	155	A request to restart all resources was failed(0x%08x).	A request to start all resources has failed.	Same as above	o	o
apisv	Error	160	A request to suspend monitor resource was failed(0x%08x).	A request to suspend the monitor resources has failed.	Check the status of the monitor resources.	o	o
apisv	Error	161	A request to resume monitor resource was failed(0x%08x).	A request to resume the monitor resources has failed.	Same as above	o	o
apisv	Error	162	A request to enable Dummy Failure of monitor resource was failed(0x%08x).	The monitor resource failed to start Dummy Failure.	Check the status of the monitor resource.	o	o
apisv	Error	163	A request to disable Dummy Failure of monitor resource was failed(0x%08x).	The monitor resource failed to stop Dummy Failure.	Same as above.	o	o
cfmgr	Info	1	The cluster configuration data has been uploaded by %1.	The configuration data has been uploaded.	-	o	o
sra	Error	1	system monitor closed because reading the SG file failed.	An error occurred in reading the SG file.	Check the message separately issued.		o
sra	Error	2	Opening an ignore file failed. file name = %1, errno = %2. %1:File name %2:errno	The SG file (%1) failed to be opened.	Restart the cluster, or execute the suspend and resume.		o
sra	Error	3	Reading a configuration file failed.	An error occurred in reading the SG file.	Check the message separately issued.		o
sra	Error	4	Trace log initialization failed.	The internal log file could not be initialized.	Restart the cluster, or execute the suspend and resume.		o
sra	Error	5	Creating a daemon process failed.	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Error	6	Reading a service configuration file failed.	An error occurred in reading the SG file.	Check the message separately issued.		o
sra	Error	7	mlock() failed.	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Error	8	A daemon process could not be created.	SystemResourceAgent has failed to start (turning the process into a daemon).	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Error	9	stdio and stderr could not be closed.	SystemResourceAgent has failed to start (closing the standard I/O).	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Error	10	A signal mask could not be set up.	SystemResourceAgent has failed to start (setting the signal mask).	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Error	11	A configuration file error occurred. (1) [line = %1, %2] %1:Line %2:Setting value	SystemResourceAgent has failed to start (reading the SG file).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	12	A configuration file error occurred. (2) [line=%1, %2] %1:Line %2:Setting value	SystemResourceAgent has failed to start (reading the SG file).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	13	A plugin event configuration file error occurred. The DLL pointer was not found. [line = %1, %2] %1:Line %2:Setting value	SystemResourceAgent has failed to start (registering the plugin event).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	14	malloc failed. [event structure]	SystemResourceAgent has failed to start (registering the plugin event).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	15	A service configuration file error occurred due to an invalid event. [%1] %1:Setting value	SystemResourceAgent has failed to start (reading the service file).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	16	A plugin event configuration file error occurred due to %1. %1:Cause of error	SystemResourceAgent has failed to start (reading the plugin event file).	Restart the cluster, or execute the suspend and resume.		o
sra	Error	17	Internal error occurred.	A shared memory access error has occurred.	-		o
sra	Warning	101	Opening an SG file failed. file name = %1, errno = %2 %1:File name %2:errno	The SG file (%1) failed to be opened.	Recreate the SG file and restart the cluster, or execute the suspend and resume.		o
sra	Warning	102	malloc(3) fail(1) . [%1] %1:Function name	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Warning	103	malloc(3) fail(2). [%1] %1:Function name	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Warning	104	An internal error occurred. rename(2) error (errno = %1) %1:errno	This product has terminated abnormally.	See the most recently issued system log message.		o
sra	Warning	105	realloc(3) fail. [%1]. %1:Function name	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Warning	106	A script timed out. (%1 %2) %1:Script file name %2:Argument	An external error has occurred.	Check the load status of the server and remove the load.		o
sra	Warning	107	[%1] execvp(2) fail (%2). %1:Script file name %2:errno	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Warning	108	[%1] fork fail (%2). Suspended. %1:Script file name %2:errno	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Warning	109	malloc(3) fail. [%1] %1:Function name	An external error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.		o
sra	Info	201	A script was executed. (%1) %1:Script name	Script (%1) has been executed.	-		o
sra	Info	202	Running a script finished. (%1) %1:Script name	Script has ended normally.	-		o
sra	Info	203	An %1 event succeeded. %1:Executed event type	The operation management command has been executed. The executed event type (boot, shutdown, stop, start, or flush) is output.	-		o
sra	Error	301	A process resource error was detected. (%1, type = cpu, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the CPU usage rates of specific processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = memory leak, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the memory usage of specific processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = file leak, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the number (maximum) of open files of specific processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = open file, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the number (upper kernel limit) of open files of specific processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = thread leak, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the number of threads of specific processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = defunct, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the zombie processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	301	A process resource error was detected. (%1, type = same name process, pid = %2, %3) %1:Monitor resource name %2:Process ID %3:Process name	An error was detected in monitoring the same-name processes.	Check the possible causes of the monitoring failure.	o	o
sra	Error	302	A system resource error was detected. (%1, type = cpu) %1:Monitor resource name	An error was detected in monitoring the CPU usage rates of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	302	A system resource error was detected. (%1, type = memory) %1:Monitor resource name	An error was detected in monitoring the total usage of memory of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	302	A system resource error was detected. (%1, type = swap) %1:Monitor resource name	An error was detected in monitoring the total usage of virtual memory of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	302	A system resource error was detected. (%1, type = file) %1:Monitor resource name	An error was detected in monitoring the total number of open files of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	302	A system resource error was detected. (%1, type = thread) %1:Monitor resource name	An error was detected in monitoring the total number of threads of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	303	A system resource error was detected. (%1, type = number of process, user name = %2) %1:Monitor resource name %2:User name	An error was detected in monitoring the number of running processes for each user of the system.	Check the possible causes of the monitoring failure.	o	o
sra	Error	304	A disk resource error was detected. (%1, type = used rate, level = NOTICE, %2) %1:Monitor resource name %2:mount point	A notice level error was detected in monitoring the disk usage rates.	Check the possible causes of the monitoring failure.	o	o
sra	Error	304	A disk resource error was detected. (%1, type = used rate, level = WARNING, %2) %1:Monitor resource name %2:mount point	A warning level error was detected in monitoring the disk usage rates.	Check the possible causes of the monitoring failure.	o	o
sra	Error	304	A disk resource error was detected. (%1, type = free space, level = NOTICE, %2) %1:Monitor resource name %2:mount point	A notice level error was detected in monitoring the free disk space.	Check the possible causes of the monitoring failure.	o	o
sra	Error	304	A disk resource error was detected. (%1, type = free space, level = WARNING, %2) %1:Monitor resource name %2:mount point	A warning level error was detected in monitoring the free disk space.	Check the possible causes of the monitoring failure.	o	o
sra	Warning	401	zip/unzip package is not installed.	The compression of statistical information collected by System Resource Agent failed.	Check if a zip (unzip) package has been installed in the system.	o	o
lcns	Info	1	The number of licenses is %1. (Product name:%2)	The number of cluster licenses is %1. %1: Number of licenses %2: Product name	-	o	o
lcns	Info	2	The trial license is valid until %1. (Product name:%2)	The trial license is effective until %1. %1: Trial end date %2: Product name	-	o	o
lcns	Warning	3	The number of licenses is insufficient. The number of insufficient licenses is %1. (Product name:%2)	The number of licenses is insufficient. The number of insufficient licenses is %1. %1: Required number of licenses %2: Product name	Purchase the required number of licenses and then register them.	o	o
lcns	Error	4	The license is not registered. (Product name:%1)	The license is not registered. %1: Product name	Purchase the license and then register it.	o	o
lcns	Error	5	The trial license has expired in %1. (Product name:%2)	The validity term of the trial license has expired. %1: Trial end date %2: Product name	Register a valid license.	o	o
lcns	Error	6	The registered license is invalid. (Product name:%1, Serial No:%2)	The registered license is invalid. %1: Product name %2: Serial number	Register a valid license.	o	o
lcns	Error	7	The registered license is unknown. (Product name:%1)	The registered license is unknown. %1: Product name	Register a valid license.	o	o
lcns	Error	8	The trial license is valid from %1. (Product name:%2)	The validity term of the trial license is not reached. %1: Trial start date %2: Product name	Register a valid license.	o	o
lcns	Info	9	The fixed term license is valid until %1. (Product name:%2)	The validity term of the fixed-term license is effective until %1. %1:End date of validity term %2: Product name	-	o	o
lcns	Error	10	The fixed term license has expired in %1. (Product name:%2)	The validity term of the fixed-term license has expired. %1: End date of validity term %2: Product name	Register a valid license.	o	o
reg	Info	1	The number of reboots due to group resource errors has been reset.	The number of reboots due to group resource errors has been reset.	-	o	o
reg	Info	2	The number of reboots due to monitor resource errors has been reset.	The number of reboots due to monitor resource errors has been reset.	-	o	o
webmgr	Warning	21	HTTPS configuration isn't correct, HTTPS mode doesn't work. Please access WebManager by HTTP mode.	HTTPS configuration isn't correct, HTTPS mode doesn't work. Please access WebManager by HTTP mode.	-	o	o

4.2. Driver syslog messages

4.2.1. Kernel mode LAN heartbeat driver

Module Type	Event type	Event ID	Message	Description	Solution
clpkhb	Info	101	Kernel Heartbeat was initialized successfully. (major=%1, minor=%2)	The clpkhb driver was successfully loaded.	-
clpkhb	Info	102	Kernel Heartbeat was released successfully.	The clpkhb driver was successfully unloaded.	-
clpkhb	Error	103	Can not register miscdev on minor=%1. (err=%2)	Failed to load the clpkhb driver.	-
clpkhb	Error	104	Can not deregister miscdev on minor=%1. (err=%2)	Failed to unload the clpkhb driver.	-
clpkhb	Info	105	Kernel Heartbeat was initialized by %1.	The clpkhb driver was successfully initialized by [%1] module.	-
clpkhb	Info	106	Kernel Heartbeat was terminated by %1.	The clpkhb driver was successfully terminated by [%1] module.	-
clpkhb	Error	107	Can not register Kernel Heartbeat proc file!	Failed to create proc file for the clpkhb driver.	-
clpkhb	Error	108	Version error.	The inside version information of the clpkhb driver is invalid.	Reinstall EXPRESSCLUSTER.
clpkhb	Info	110	The send thread has been created. (PID=%1)	The send thread of the clpkhb driver was successfully created. The process ID is [%1].	-
clpkhb	Info	110	The recv thread has been created. (PID=%1)	The receive thread of the clpkhb driver was successfully created. The process ID is [%1].	-
clpkhb	Error	111	Failed to create send thread. (err=%1)	Failed to create the send thread of the clpkhb driver due to the error [%1].	-
clpkhb	Error	111	Failed to create recv thread. (err=%1)	Failed to create the receive thread of the clpkhb driver due to the error [%1].	-
clpkhb	Info	112	Killed the send thread successfully.	The send thread of clpkhb driver was successfully stopped.	-
clpkhb	Info	112	Killed the recv thread successfully.	The receive thread of clpkhb driver was successfully stopped.	-
clpkhb	Info	113	Killed the recv thread successfully.	Killing the clpkhb driver.	-
clpkhb	Info	114	Killed the recv thread successfully.	Killing the clpkhb driver.	-
clpkhb	Info	115	Kernel Heartbeat has been stopped	The clpkhb driver successfully stopped.	-
clpkhb	Error	120	Failed to create socket to send %1 packet. (err=%2)	Failed to create the socket for sending the [%1] (HB/DOWN/KA) packet due to the error [%2].	-
clpkhb	Error	120	Failed to create socket to receive packet. (err=%2)	Failed to create the socket for receiving the packet due to the error [%2].	-
clpkhb	Error	121	Failed to create sending %1 socket address. (err=%2)	Failed to set the socket for sending the [%1] (HB/DOWN/KA) packet.	The physical memory may be running out. Add physical memories, or terminate unnecessary applications.
clpkhb	Error	122	Failed to create %1 socket address. (err=%2)	Failed to set the socket for sending the [%1] (HB/DOWN/KA) packet.	The physical memory may be running out. Add physical memories, or terminate unnecessary applications.
clpkhb	Error	123	Failed to bind %1 socket. (err=%2)	Failed to bind the socket for [%1] (HB/DOWN/KA).	Check the status of the operating system. The communication port for clpkhb may be used already by other applications or others. Check the usage status of the communication port. Check the cluster configuration information server property if the IP address set for the interconnect LAN I/F is correct.
clpkhb	Error	125	Failed to send %1 data to %2. (err=%3)	Failed to send [%1] (HB/DOWN/KA) data to [%2].	Check the status of the network for the clpkhb communication. Check the status of the remote server. Check that the setting information is correct.
clpkhb	Error	126	Failed to receive data. (err=%3)	Failed to receive data.	The remote server may be down. Check if the server is active. If the server is not down, check the status of the network for clpkhb.
clpkhb	Info	127	Received an invalid packet. Magic is not correct! Received an invalid packet from %1. Magic(%2) is not correct!	Received an invalid packet. Ignore the packet. An invalid packet [%2] has been received from %1, but will be ignored.	Other applications may be sending the data to the port for clpkhb. Check the usage status of the port.
clpkhb	Error	128	Received an invalid packet. %1 is not correct! Received an invalid packet from %1. %2 is not correct!	Received an invalid packet. The invalid part of the packet is [%1] (Resource priority/Source ip address). An invalid packet has been received from %1. The invalid part of the packet is %2 (Resource priority/Source ip address).	Same as above.
clpkhb	Info	129	Receiving operation was interrupted by ending signal!	The receive thread ends by termination signal.	-
clpkhb	Info	130	clpka: <server priority: %1> <reason: %2> <process name: %3> system reboot. clpka: <server priority: %1> <source: %2> <exit code: %3> system reboot.	A reset message was received from another server. The priority [%1] server was reset because the reason [%2] problem occurred in the process [%3]. A reset message was received from another server. The priority [%1] server was reset because %2 ended with the exit code [%3].	Check the status of the server where the reset occurred.
clpkhb	Info	131	clpka: <server priority: %1> <reason: %2> <process name: %3> system panic. clpka: <server priority: %1> <source: %2> <exit code: %3> system panic.	A panic message was received from another server. The priority [%1] server panicked because the reason [%2] problem occurred in the process [%3]. A panic message was received from another server. The priority [%1] server panicked because %2 ended with the exit code [%3].	Check the status of the server where the panic occurred.
clpkhb	Error	140	Reference an inaccessible memory area!	Failed to pass data to an application by ioctl().	Check the status of the operating system.
clpkhb	Error	141	Failed to allocate memory!	Failed to allocate memory.	The physical memory may be running out. Add physical memories, or terminate unnecessary applications.
clpkhb	Error	142	Invalid argument, %1!	The parameter passed to the clpkhb driver is not correct.	Check if the settings are correct.
clpkhb	Warning	143	Local node has nothing with current resource.	The heartbeat resource information passed to the clpkhb driver is not correct.	Same as above.

4.2.2. Keepalive driver

Module Type	Event type	Event ID	Message	Description	Solution
clpka	Info	101	Kernel Keepalive was initialized successfully. (major=%1, minor=%2)	The clpka driver was successfully loaded.	-
clpka	Info	102	Kernel Keepalive was released successfully.	The clpka driver was successfully unloaded.	-
clpka	Error	103	Can not register miscdev on minor=%1. (err=%2)	Failed to load the clpka driver.	Check the distribution and kernel support the kernel mode LAN heartbeat.
clpka	Info	105	Kernel Keepalive was Initialized by %1.	The clpka driver was successfully initialized.	-
clpka	Error	107	Can not register Kernel Keepalive proc file!	Failed to create proc file for the clpka driver.	The kernel may not be running normally because of lack of memory or other reasons. Add physical memories, or terminate unnecessary applications.
clpka	Error	108	Version error.	The version of the clpka driver is invalid.	Check if the installed clpka driver is legitimate.
clpka	Error	111	Failed to create notify thread. (err=%1)	Failed to create the thread of the clpka driver.	The kernel may not be running normally because of lack of memory or other reasons. Add physical memories, or terminate unnecessary applications.
clpka	Info	130	Reboot tried.	In keeping with the settings, the clpka driver tried to restart the machine.	-
clpka	Info	132	Kernel do nothing.	In keeping with the settings, the clpka driver did nothing.	-
clpka	Error	140	Reference an inaccessible memory area!	Failed to pass the version information of the clpka driver to the cluster main body.	Check if the installed clpka driver is legitimate.
clpka	Error	141	Failed to allocate memory!	The size of physical memory is not sufficient.	The physical memory is running out. Add physical memories, or terminate unnecessary applications.
clpka	Error	142	Invalid argument, %1!	Invalid information was passed from the cluster main body to the clpka driver.	Check if the installed clpka driver is legitimate.
clpka	Error	144	Process (PID=%1) is not set.	A process other than cluster main body tried operation to the clpka driver.	Check if there is any application trying to access to the clpka driver erroneously.

4.3. Detailed information on activating and deactivating group resources

4.3.1. EXEC resources

Module Type	Type	Return Value	Message	Explanation	Solution
exec	Error	1	Termination code %1 was returned.	A termination code other than 0 has been returned as the execution result of a synchronous script or application.	If this message appears for a script, the contents of the script might be incorrect. Check whether the script is correctly specified. If this message appears for an application, the application might have terminated abnormally. Check the application operation.
exec	Error	1	Command was not completed within %1 seconds.	Execution of a synchronous script or application has not terminated within the specified time.	If this message appears for a script, the contents of the script might be incorrect. Check whether the script is correctly described. If this message appears for an application, the application might have stalled. Check the application operation. The cause of this error might be identifiable from the logs. For details about log output settings, refer to "Details of other settings" in the "EXPRESSCLUSTER X SingleServerSafe Configuration Guide".
exec	Error	1	Command was aborted.	A synchronous script or application has been aborted.	If this message appears for an application, the application might have been aborted. Check the application operation. Memory or OS resources may not be sufficient. Check them.
exec	Error	1	Command was not found. (error=%1)	The application was not found.	The application path might be incorrect. Check the path of the application in the configuration data.
exec	Error	1	Command string was invalid.	The application path is invalid.	Check the path of the application in the configuration data.
exec	Error	1	Log string was invalid.	The path of the log output destination is incorrect.	Check the path of the data log output destination in the configuration data.
exec	Error	1	Internal error. (status=%1)	Another internal error occurred.	Memory or OS resources may not be sufficient. Check them.

4.4. Details about monitor resource errors

4.4.1. Software RAID monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
lmdw	Warning	101	Device=(%1): Bad disks(%2) are detected in mirror disk.	Some physical disks under the mirror disk are damaged and now have the [caution] status.	The mirror disk can be used but the damaged physical disks must be replaced.
lmdw	Warning	102 190	Internal error.err=%1	An internal error occurred.	There might not be enough memory space or OS resources. Check them.
lmdw	Warning	102 190	Config file error.(err=%1)	The contents of the configuration data are incorrect.	Check whether the configuration data is correct.
lmdw	Warning	190	Soft RAID module has a problem. (err=%1)	The kernel module related to software RAID is faulty.	-
lmdw	Warning	190	Options or parameters are invalid.	A command parameter error occurred.	Check whether the configuration data is correct.
lmdw	Warning	190	Failed to read config file.(err=%1)	The configuration file could not be read.	Check whether the configuration data is correct.
lmdw	Warning	191	Device=(%1): Mirror disk is in recovery process (%2).	The mirror disk is now in the [recovery] process.	-

4.4.2. IP monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
ipw	Error	5	Ping was failed by timeout. IP=%s...	The ping command has failed due to a timeout.	The system may be under high load, or memory or OS resources may not be sufficient. Check them.
ipw	Error	31	Ping cannot reach. (ret=%1) IP=%2...	The packet transmitted by the ping command has not arrived.	Check whether the ping command to the corresponding IP address succeeds. If the command fails, check the status of the device that has the IP address or status of the network interface.
ipw	Warning	102	Ping was failed. (ret=%1) IP=%2...	The ping command has failed.	Memory or OS resources may not be sufficient. Check them.
ipw	Warning	106 108 to 121	Internal error. (status=%1)	Another internal error occurred.	Memory or OS resources may not be sufficient. Check them.
ipw	Warning	189	Internal error. (status=%1)	Monitoring of the IP monitor resource failed by time out.	Memory or OS resources may not be sufficient. Check them.

4.4.3. Disk monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
diskw	Error	12	Ioctl was failed. (err=%1) Device=%2	Failed to control the device.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk.
diskw	Error	14	Open was failed. (err=%1) File=%2	The file could not be opened.	Check whether a directory that has the same name as the file exists, the monitoring target disk is connected properly, the disk is on, or other errors occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	14	Open was failed. (err=%1) Device=%2	Opening the device failed.	Check whether a directory that has the same name as the file exists, the monitoring target disk is connected properly, the disk is on, or other errors occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	16	Read was failed. (err=%1) Device=%2	Reading from the device has failed.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk. Memory or OS resources may not be sufficient. Check them.
diskw	Error	18	Write was failed. (err=%1) File=%2	Writing to the file has failed.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk.
					Memory or OS resources may not be sufficient. Check them.
diskw	Error	41	SG_IO failed. (sg_io_hdr_t info:%1 SG_INFO_OK_MASK: %2)	SG_IO has failed.	Check if the monitoring target disk is connected properly, the disk is powered on, or no other errors are occurred on the disk.
diskw	Error	49	Already bound for other. Rawdevice=%1 Device=%2	The RAW device has already been bound by another real device.	The set RAW device has already been bound by another real device. Change the RAW device name on the Cluster WebUI.
diskw	Error	55	Bind was failed. Rawdevice=%1 Device=%2	Bind failed.	Bind failed. Check the RAW device name on the Cluster WebUI.
diskw	Error	56	Lseek was failed by timeout. Device=%1	Lseek failed.	The possible cause is the heavily loaded system, insufficient memory, or insufficient OS resources. Check if any of these exists.
diskw	Error	57	Fdatasync was failed by timeout. Device=%1	Fdatasync failed.	Check if the disk as a monitoring target is appropriately connected, is turned on, or has anything abnormal. The possible cause is the heavily loaded system, insufficient memory, or insufficient OS resources. Check if any of these exists.
diskw	Warning	101	Ioctl was failed by timeout. Device=%1	The device control failed due to timeout.	Check the disk to be monitored is properly connected, powered on, or does not have any problem. The system may be heavily loaded, memory or OS resources may not be sufficient. Check them.
diskw	Warning	101	Open was failed by timeout. File=%1	Opening the file failed due to timeout.	Check the disk to be monitored is properly connected, powered on, or does not have any problem.
diskw	Warning	101	Open was failed by timeout. Device=%1	Opening the device failed due to timeout.	The system may be heavily loaded, memory or OS resources may not be sufficient. Check them.
diskw	Warning	101	Read was failed by timeout. Device=%1	Failed to read from the device due to timeout.	Check the disk to be monitored is properly connected, powered on, or does not have any problem.
					The system may be heavily loaded, memory or OS resources may not be sufficient. Check them.
diskw	Warning	101	Write was failed by timeout. File=%1	Writing to the file failed due to timeout.	Check the disk to be monitored is properly connected, powered on, or does not have any problem.
					The system may be heavily loaded, memory or OS resources may not be sufficient. Check them.
diskw	Warning	101	Bind was failed. Rawdevice=%1 Device=%2	Bind failed.	Bind failed. Check the RAW device name on the Cluster WebUI.
diskw	Warning	101	Stat was failed. (err=%1) Device=%2	Stat failed.	Stat failed. Check the device name on the Cluster WebUI.
diskw	Warning	101	Popen was failed. (err=%1)	Popen failed.	Popen failed. Memory or OS resources may not be sufficient. Check them.
diskw	Warning	101 190	Option was invalid.	The option is invalid.	Check the cluster configuration data.
diskw	Warning	101 190	Internal error. (status=%1)	An error other than the errors mentioned above has occurred.	Memory or OS resources may not be sufficient. Check them.
diskw	Warning	190	Parameter was invalid. File=%1	The specified file name is invalid.	Do not specify the file whose name starts with /dev. Specify a normal file.
diskw	Warning	190	Device was invalid. Device=%1	The specified real device is invalid.	Check the device name of the disk monitor resource on the Cluster WebUI.
diskw	Warning	191	Ignored disk full error.	A disk full error has been ignored.	Check the usage of the device.

4.4.4. PID monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
pidw	Error	1	Process does not exist. (pid=%1)	The process does not exist.	Process of the monitoring target was cleared due to some error. Check them.
pidw	Warning	100	Resource %1 was not found.	The resource is not found.	Check the cluster configuration data by using the Cluster WebUI.
pidw	Warning	100	Internal error. (status=%1)	Another internal error occurred.	Memory or OS resources may not be sufficient. Check them.

4.4.5. User space monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
userw	Error	1	Initialize error. (%1)	An error was detected during process initialization.	Check if the driver depended on by the user mode monitor resources exists, or the rpm is installed. The driver or rpm differ depending on the monitor method.

4.4.6. Custom monitor resource

Module Type	Type	Return Value	Message	Explanation	Solution
genw	Error	1	Initialize error. (status=%d)	An error was detected while initialization.	Memory or OS resources may not be sufficient. Check them.
genw	Error	2	Termination code %d was returned.	An unexpected value was returned.	Check if the cluster configuration information is correct.
genw	Error	3	User was not superuser.	User was not root user.	Log in as root user.
genw	Error	4	Getting of config was failed.	Failed to get the cluster configuration information.	Check if the cluster configuration information exists.
genw	Error	5	Parameter was invalid.	The parameter is invalid.	Check if the cluster configuration information is correct.
genw	Error	6	Option was invalid.	The parameter is invalid.	Check if the cluster configuration information is correct.
genw	Error	7	Monitor Resource %s was not found.	The resoruce was not found.	Check if the cluster configuration information is correct.
genw	Error	8	Create process failed.	Create process failed.	Memory or OS resources may not be sufficient. Check them.
genw	Error	9	Process does not exist. (pid=%d)	The process did not exist.	Check if the process exists.
genw	Error	10	Process aborted. (pid=%d)	The process did not exist.	Check if the process exists.
genw	Error	11	Asynchronous process does not exist. (pid=%d)	The process did not exist.	Check if the process exists.
genw	Error	12	Asynchronous process aborted. (pid=%d)	The process did not exist.	Check if the process exists.
genw	Error	13	Monitor path was invalid.	The path is invalid.	Check if the cluster configuration information is correct.
genw	Error	others	Internal error. (status=%d)	Another internal error occurred.	-

4.4.7. Multi target monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
mtw	Error	1	Option was invalid.	The parameter is invalid.	Check if the cluster configuration information is correct.
mtw	Error	2	User was not superuser.	User was not root user.	Log in as root user.
mtw	Error	3	Internal error. (status=%d)	Another internal error occurred.	-

4.4.8. JVM monitor resources

Module Type	Type	Return value	Message	Description	Solution
jraw	Error	11	An error was detected in accessing the monitor target.	Java VM to be monitored cannot be connected.	Check that the Java VM to be monitored is running.
jraw	Error	12	JVM status changed to abnormal. cause = %1.	An error was detected in monitoring Java VM. %1: Error generation cause GarbageCollection JavaMemoryPool Thread WorkManagerQueue WebOTXStall	Based on the message, check the Java application that is running on Java VM to be monitored.
jraw	Warning	189	Internal error occurred.	An internal error has occurred.	Execute cluster suspend and cluster resume.

4.4.9. System monitor resources

Module Type	Type	Return value	Message	Description	Solution
sraw	Error	11	Detected an error in monitoring system resource	An error was detected when monitoring system resources.	There may be an error with the resources. Check them.

4.4.10. Process resource monitor resource

Module Type	Type	Return value	Message	Description	Solution
psrw	Error	11	Detected an error in monitoring process resource	An error was detected when monitoring Process resources.	There may be an error with the resources. Check them.

4.4.11. NIC Link Up/Down monitor resources

Module Type	Type	Return Value	Message	Explanation	Solution
miiw	Error	20	NIC %1 link was down.	The NIC link has gone down.	Check whether the LAN cable is connected properly.
miiw	Warning	110	Get address information was failed. (err=%1)	The socket address of the IPv4 or IPv6 address family could not be obtained.	Check whether the kernel configuration supports TCP/IP networking (IPv4 or IPv6).
miiw	Warning	111	Socket creation was failed. (err=%1)	The socket could not be created.	Memory or OS resources may not be sufficient. Check them.
miiw	Warning	112	ioctl was failed. (err=%1) Device=%2 Request=%3	The control request to the network driver has failed.	Check whether the network driver supports control request %3. For details about the verified NIC and network driver, see "Monitor resource details" in the "EXPRESSCLUSTER X SingleServerSafe Configuration Guide".
miiw	Warning	113	MII was not supported or no such device. Device=%1	MII is not supported by NIC or the monitored object does not exist.	For details about the verified NIC and network driver, see "Monitor resource details" in the "EXPRESSCLUSTER X SingleServerSafe Configuration Guide". If the monitored target does not exist, check the network interface name, such as by using ifconfig.
miiw	Warning	189	Internal error. (status=%d)	Another internal error occurred.	-
miiw	Warning	190	Option was invalid.	The option is invalid.	Check the configuration data by using the Cluster WebUI.
miiw	Warning	190	Config was invalid. (err=%1) %2	The configuration data is invalid.	Check the configuration data by using the Cluster WebUI.

4.4.12. Volume manager monitor resources

Module Type	Type	Return value	Message	Description	Solution
volmgrw	Error	21	Command was failed. (cmd=%1, ret=%2)	%1 command failed. The return value is %2.	The command failed. Check the action status of the volume manager.
volmgrw	Error	22 23	Internal error. (status=%1)	Another internal error occurred.	-
volmgrw	Warning	190	Option was invalid.	The option is invalid.	Check the cluster configuration information on the Cluster WebUI.
volmgrw	Warning	191	%1 %2 is %3 !	The status of the target (%2) of the volume manager (%1) transferred to %3.	Check the status of the volume manager target.
volmgrw	Warning	Others	Internal error. (status=%1)	Another internal error occurred.	-

4.4.13. Process name monitor resources

Module Type	Type	Return value	Message	Description	Solution
psw	Error	11	Process[%1 (pid=%2)] Down	Deletion of a monitored process has been detected.	Check whether the monitored process is running normally.
psw	Error	12	The number of processes is less than the specified minimum process count. %1/%2 (%3)	The number of started processes for the monitor target process is less than the specified minimum count.	Check whether the monitored process is running normally.
psw	Warning	100	Monitoring timeout	Monitoring has timed out.	The OS may be highly loaded. Check that.
psw	Warning	101 190	Internal error	An internal error has occurred.	Check the following possible causes: memory shortage or OS resource insufficiency.
psw	Warning	190	Initialize error	An error has been detected during initialization.	Check the following possible causes: memory shortage or OS resource insufficiency.

4.4.14. Monitoring option monitor resources

The monitoring option monitor resources use common messages. Module types differ per monitoring option monitor resource.

Monitoring Option Monitor Resource	Module Type
DB2 monitor resource	db2w
FTP monitor resource	ftpw
HTTP monitor resource	httpw
IMAP4 monitor resource	imap4w
MySQL monitor resource	mysqlw
NFS monitor resource	nfsw
ODBC monitor resource	odbcw
Oracle monitor resource	oraclew
POP3 monitor resource	pop3w
PostgreSQL monitor resource	psqlw
Samba monitor resource	sambaw
SMTP monitor resource	smtpw
SQL Server monitor resource	sqlserverw
Tuxedo monitor resource	tuxw
WebLogic monitor resource	wlsw
WebSphere monitor resource	wasw
WebOTX monitor resource	otxw

Module Type	Type	Return Value	Message	Explanation	Solution
(see the list above)	Error	5	Failed to connect to %1 server. [ret=%2]	Connecting to the monitoring target has failed. The application name is displayed in place of %1.	Check the status of the monitoring target.
(see the list above)	Error	7	Failed to execute SQL statement (%1). [ret=%2]	The SQL statement could not be executed. The monitoring target is displayed in place of %1.	Check the configuration data by using the Cluster WebUI.
(see the list above)	Error	8	Failed to access with %1.	Data access with the monitoring target has failed. The monitoring target is displayed in place of %1.	Check the status of the monitoring target.
(see the list above)	Error	9	Detected error in %1.	The monitoring target is abnormal. The monitoring target is displayed in place of %1.	Check the status of the monitoring target.
(see the list above)	Warning	104	Detected function exception. [%1, ret=%2]	An error was detected. The monitoring target is displayed in place of %1.	Check the configuration data by using the Cluster WebUI. The OS might be heavily loaded. Check them.
(see the list above)	Warning	106	Detected authority error.	User authentication has failed.	Check the user name, password, and access permissions.
(see the list above)	Warning	111	Detected timeout error.	Communication with the monitoring target timed out.	The OS might be heavily loaded. Check them.
(see the list above)	Warning	112	Can not found install path. (install path=%1)	The install path could not be loaded from the specified location. The install path is displayed in place of %1.	Check the install path location.
(see the list above)	Warning	113	Can not found library. (libpath=%1, errno=%2)	The library could not be loaded from the specified location. The library path is displayed in place of %1.	Check the library location.
(see the list above)	Warning	171	Detected a monitor delay in monitoring %1. (timeout=%2*%3 actual-time=%4 delay warning rate=%5)	A monitoring delay was detected in monitoring %1. The current timeout value is %2 (second) x %3 (tick count per second). The actual measurement value at delay detection is %4 (tick count) and exceeded the delay warning rate %5 (%).	Check the load status of the server on which a monitoring delay was detected and remove the load. If a monitoring timeout is detected, extend it.
(see the list above)	Info	181	The collecting of detailed information triggered by monitor resource %1 error has been started (timeout=%2).	Collecting of detailed information triggered by the detection of a monitor resource $1 monitoring error has started. The timeout is %2 seconds.	-
(see the list above)	Info	182	The collection of detailed information triggered by monitor resource %1 error has been completed.	Collecting of detailed information triggered by the detection of a monitor resource %1 monitoring error has been completed.	-
(see the list above)	Warning	183	The collection of detailed information triggered by monitor resource %1 error has been failed (%2).	Collecting of detailed information triggered by the detection of a monitor resource %1 monitoring error has failed. (%2)	-
(see the list above)	Warning	189	Internal error. (status=%1)	Internal error.	-
(see the list above)	Warning	190	Init error. [%1, ret=%2]	An error was detected during initialization. license, library, XML, share memory, or log is displayed where %1 is represented.	The OS might be heavily loaded. Check them.
(see the list above)	Warning	190	Get config information error. [ret=%1]	Failed to obtain the configuration data.	Check the configuration data by using the Cluster WebUI.
(see the list above)	Warning	190	Invalid parameter.	The configuration data of the Config or Policy file is invalid. The command parameter is invalid.	Check the configuration data by using the Cluster WebUI.
(see the list above)	Warning	190	Init function error. [%1, ret=%2]	Initialize error occurred in the function. The executive function name is displayed in %1.	OS may be heavily loaded. Check the status of OS.
(see the list above)	Warning	190	User was not superuser.	The user does not have root privileges.	The user executing the operation might not have root privileges, or the memory or OS resources might be insufficient. Check them.
(see the list above)	Warning	190	The license is not registered.	The license is not registered.	Check whether the correct license is registered.
(see the list above)	Warning	190	The registration license overlaps.	The license you are attempting to register already exists.	Check whether the correct license is registered.
(see the list above)	Warning	190	The license is invalid.	The license is invalid.	Check whether the correct license is registered.
(see the list above)	Warning	190	The license of trial expired by %1.	The trial license has expired. The expiration date is displayed in place of %1.	-
(see the list above)	Warning	190	The license of trial effective from %1.	The date is not the starting date of the trial license. The starting date of the trial license is displayed in place of %1.	-
(see the list above)	Warning	190	Not supported algorithm(%1).	The algorithm is not supported. %1 represents the algorithm.	-

4.5. JVM monitor resource log output messages

The following messages belong to the JVM operation log files that are specific to the JVM monitor resources.

4.5.1. JVM operation log

Message	Cause of generation	Action
Failed to write the %1$s.stat.	Writing to the JVM statistics log has failed. %1$s.stat: JVM statistics log file name	Check whether there is sufficient free disk space.
%1$s: analyze finish[%4$s]. state = %2$s, cause = %3$s	(When the status of the Java VM to be monitored is abnormal) the resource use amount has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Status of Java VM to be monitored (1=normal, 0=abnormal) %3$s: Error generation location at abnormality occurrence %4$s: Measurement thread name	Review the Java application that runs on the Java VM to be monitored.
thread stopped by UncaughtException.	The thread of the JVM monitor resource has stopped.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
thread wait stopped by Exception.	The thread of the JVM monitor resource has stopped.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
%1$s: monitor thread can't connect to JVM.	The Java VM to be monitored could not be connected. %1$s: Name of the Java VM to be monitored	Check that the Java VM to be monitored is running.
%1$s: monitor thread can't get the JVM state.	The resource use amount could not be acquired from Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check that the Java VM to be monitored is running.
%1$s: JVM state is changed [abnormal -> normal].	The status of the Java VM to be monitored has changed from abnormal to normal. %1$s: Name of the Java VM to be monitored	-
%1$s: JVM state is changed [normal -> abnormal].	The status of the Java VM to be monitored has changed from normal to abnormal. %1$s: Name of the Java VM to be monitored	Review the Java application that runs on the Java VM to be monitored.
%1$s: Failed to connect to JVM.	The Java VM to be monitored could not be connected. %1$s: Name of the Java VM to be monitored	Check that the Java VM to be monitored is running.
Failed to write exit code.	The JVM monitor resource failed to write data to the file for recording the exit code.	Check whether there is sufficient free disk space.
Failed to be started JVM Monitor.	Starting of the JVM monitor resource has failed.	Check the JVM operation log, remove the cause preventing the start, execute cluster suspend/cluster resume, and then restart the JVM monitor resource.
JVM Monitor already started.	The JVM monitor resource has already been started.	Execute cluster suspend/cluster resume and then restart the JVM monitor resource.
%1$s: GARBAGE_COLLECTOR _MXBEAN_DOMAIN_TYPE is invalid.	GC information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: GarbageCollectorMXBean is invalid.	GC information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: Failed to measure the GC stat.	GC information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: GC stat is invalid. last.getCount = %2$s, last.getTime = %3$s, now.getCount = %4$s, now.getTime = %5$s.	The GC generation count and GC execution time could not be measured for the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: GC generation count at last measurement %3$s: Total GC execution time at last measurement %4$s: GC generation count at this measurement %5$s: Total GC execution time at this measurement	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: GC average time is too long. av = %6$s, last.getCount = %2$s, last.getTime = %3$s, now.getCount = %4$s, now.getTime = %5$s.	The average GC execution time has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: GC generation count at last measurement %3$s: Total GC execution time at last measurement %4$s: GC generation count at this measurement %5$s: Total GC execution time at this measurement %6$s: Average of the GC execution time used from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1$s: GC average time is too long compared with the last connection. av = %6$s, last.getCount = %2$s, last.getTime = %3$s, now.getCount = %4$s, now.getTime = %5$s.	After the Java VM to be monitored was reconnected, the average of the GC execution time has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: GC generation count at last measurement %3$s: Total GC execution time at last measurement %4$s: GC generation count at this measurement %5$s: Total GC execution time at this measurement %6$s: Average of the GC execution time used from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1$s: GC count is too frequently. count = %4$s last.getCount = %2$s, now.getCount = %3$s.	The GC generation count has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: GC generation count at last measurement %3$s: GC generation count at this measurement %4$s: GC generation count from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1$s: GC count is too frequently compared with the last connection. count = %4$s last.getCount = %2$s, now.getCount = %3$s.	After the Java VM to be monitored was reconnected, the GC generation count has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: GC generation count at last measurement %3$s: GC generation count at this measurement %4$s: GC generation count from the last measurement to this measurement	Review the Java application that runs on the Java VM to be monitored.
%1$s: RuntimeMXBean is invalid.	Information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: Failed to measure the runtime stat.	Information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct. Check whether the processing load is high in the Java VM to be monitored.
%1$s: MEMORY_MXBEAN_NAME is invalid. %2$s, %3$s.	Memory information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Memory pool name %3$s: Memory name	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: MemoryMXBean is invalid.	Memory information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: Failed to measure the memory stat.	Memory information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct. Check whether the processing load is high in the Java VM to be monitored.
%1$s: MemoryPool name is undefined. memory_name = %2$s.	Memory information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Name of the Java memory pool to be measured	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: MemoryPool capacity is too little. memory_name = %2$s, used = %3$s, max = %4$s, ratio = %5$s%.	The Java memory pool free space has fallen below the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Name of the Java memory pool to be measured %3$s: Use amount of the Java memory pool %4$s: Maximum usable amount of the Java memory pool %5$s: Use rate of the Java memory pool	Review the Java application that runs on the Java VM to be monitored.
%1$s: THREAD_MXBEAN_NAME is invalid.	Thread information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: ThreadMXBean is invalid.	Thread information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: Failed to measure the thread stat.	Thread information could not be acquired from Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: Detect Deadlock. threads = %2$s.	Thread deadlock has occurred in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: ID of the deadlock thread	Review the Java application that runs on the Java VM to be monitored.
%1$s: Thread count is too much(%2$s).	The number of activated threads has exceeded the threshold in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of activated threads at measurement	Review the Java application that runs on the Java VM to be monitored.
%1$s: ThreadInfo is null.Thread count = %2$s.	Thread information could not be acquired in the Java VM to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of activated threads at measurement	Check whether the operating environment of the version of the Java VM to be monitored is correct.
%1$s: Failed to disconnect.	Disconnection from the Java VM to be monitored has failed. %1$s: Name of the Java VM to be monitored	-
%1$s: Failed to connect to WebLogicServer.	WebLogic Server to be monitored could not be connected. %1$s: Name of the Java VM to be monitored	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Failed to connect to Sun JVM.	Java VM and WebOTX to be monitored could not be connected. %1$s: Name of the Java VM to be monitored	Review the Java application that runs on the Java VM and WebOTX to be monitored.
Failed to open the %1$s.	The JVM statistics log could not be output. %1$s: Name of the HA/JVMSaverJVM statistics log file	Check whether the disk has sufficient free space or whether the number of open files has exceeded the upper limit.
%1$s: Can't find monitor file.	No monitoring %1$s: Name of the Java VM to be monitored	-
%1$s: Can't find monitor file, monitor stopped[thread:%2$s].	Monitoring stops. %1$s: Name of the Java VM to be monitored %2$s: Type of the measurement thread	-
%1$s: Failed to create monitor status file.	An internal file could not be created. %1$s: Name of the Java VM to be monitored	Check whether the disk free space and the maximum number of volume files are sufficient.
%1$s: Failed to delete monitor status file.	An internal file could not be deleted. %1$s: Name of the Java VM to be monitored	Check whether there is a problem with the hard disk.
%1$s: com.bea:Type=ServerRuntime is invalid.	Information could not be acquired from the Java VM to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the Java VM to be monitored is correct.
%1$s: WorkManagerRuntimeMBean or ThreadPoolRuntimeMBean is invalid.	Information could not be acquired from the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the WebLogic Server to be monitored is correct.
%1$s: Failed to measure the WorkManager or ThreadPool stat.	Information could not be acquired from the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored	Check whether the operating environment of the WebLogic Server to be monitored is correct.
%1$s: ThreadPool stat is invalid. last.pending = %2$s, now.pending = %3$s.	The number of waiting requests could not be measured in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s:Number of waiting requests at last measurement %3$s:Number of waiting requests at this measurement	Check whether the operating environment of the version of the WebLogic Server to be monitored is correct.
%1$s: WorkManager stat is invalid. last.pending = %2$s, now.pending = %3$s.	The number of waiting requests could not be measured in the work manager of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of waiting requests at last measurement %3$s: Number of waiting requests at this measurement	Check whether the operating environment of the version of the WebLogic Server to be monitored is correct.
%1$s: PendingRequest count is too much. count = %2$s.	The number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: PendingRequest increment is too much. increment = %4$s%%, last.pending = %2$s, now.pending = %3$s.	The increment of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of waiting requests at last measurement %3$s: Number of waiting requests at this measurement %4$s: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: PendingRequest increment is too much compared with the last connection. increment = %4$s, last.pending = %2$s, now.pending = %3$s.	After the WebLogic Server to be monitored was reconnected, the increment of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of waiting requests at last measurement %3$s: Number of waiting requests at this measurement %4$s: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Throughput count is too much. count = %2$s.	The number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of requests executed per unit time at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Throughput increment is too much. increment = %4$s, last.throughput = %2$s, now.throughput = %3$s.	The increment of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of requests executed per unit time at last measurement %3$s: Number of requests executed per unit time at this measurement %4$s: Increment of the number of requests executed per unit time from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Throughput increment is too much compared with the last connection. increment = %4$s, last.throughput = %2$s, now.throughput = %3$s.	After the WebLogic Server to be monitored was reconnected, the increment of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of requests executed per unit time at last measurement %3$s: Number of requests executed per unit time at this measurement %4$s: Increment of the number of requests executed per unit time from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: PendingRequest count is too much. appName = %2$s, name = %3$s, count = %4$s.	The number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Application name %3$s: Work manager name %4$s: Number of waiting requests	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: PendingRequest increment is too much. appName = %2$s, name = %3$s, increment = %6$s%%, last.pending = %4$s, now.pending = %5$s.	The increment of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Application name %3$s: Work manager name %4$s: Number of waiting requests at last measurement %5$s: Number of waiting requests at this measurement %6$s: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: PendingRequest increment is too much compared with the last connection. AppName = %2$s, Name = %3$s, increment = %6$s, last.pending = %4$s, now.pending = %5$s.	After the WebLogic Server to be monitored was reconnected, the increment of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Application name %3$s: Work manager name %4$s: Number of waiting requests at last measurement %5$s: Number of waiting requests at this measurement %6$s: Increment of the number of waiting requests from the last measurement to this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Can't find WorkManager. appName = %2$s, name = %3$s.	The work manager which was set could not be acquired from the WebLogic Server. %1$s: Name of the Java VM to be monitored %2$s: Application name %3$s: Work manager name	Review the setting of Target WebLogic Work Managers.
%1$s: analyze of average start[%2$s].	Analyzing of the average value has started. %1$s: Name of the Java VM to be monitored %2$s: Thread name	-
%1$s: analyze of average finish[%2$s].state = %3$s.	Analyzing of the average value has been completed. %1$s: Name of the Java VM to be monitored %2$s: Thread name %3$s: Status of the target to be monitored	-
%1$s: Average of PendingRequest count is too much. count = %2$s.	The average of the number of waiting requests has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Average of Throughput count is too much. count = %2$s.	The average of the number of requests executed per unit time has exceeded the threshold in the thread pool of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Number of requests executed per unit time at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
%1$s: Average of PendingRequest count is too much. AppName = %2$s, Name = %3$s, count = %4$s.	The average of the number of waiting requests has exceeded the threshold in the work manager of the WebLogic Server to be monitored. %1$s: Name of the Java VM to be monitored %2$s: Application name %3$s: Work manager name %4$s: Number of waiting requests at this measurement	Review the Java application that runs on the WebLogic Server to be monitored.
Error: Failed to operate clpjra_bigip.[%1$s]	%1$s: Error code	Review the setting.
action thread execution did not finish. action is alive = %1$s.	Execution of Command has timed out. %1$s: Executable file name specified by Command	Forcibly terminate Command. Review Command timeout. Remove the cause of the timeout, such as a high load.
%1$s: Failed to connect to Local JVM. cause = %2$s.	Failed to establish connection to JBoss. %1$s: Monitor target name %2$s: Detailed cause of the failure The detailed cause is one of the following. - Failed to find tools.jar, please set JDK's path for the Java installation path. - Load tools.jar exception - Get Local JVM url path exception - Failed to get process name - Failed to connect to JBoss JVM. - Failed to find management-agent.jar, please set JDK's path for the Java installation path	Review Java Installation Path and Process Name. Specify JDK, instead of JRE, as Java Installation Path. Check whether JBoss has started.

4.6. Details on checking cluster configuration data

4.6.1. Cluster Properties

Check item	ID	Message	Action
Number check on Port No. tab	1011	Failed.	Check if the sysctl command is available.
	1012	The port number %1 is within the range of automatically assigned port numbers.	Specify a port number which is not automatically assigned.
Number check on Port No.(Log) tab	1031	Failed.	Check if the sysctl command is available.
	1032	The port number %1 is within the range of automatically assigned port numbers.	Specify a port number which is not automatically assigned.

4.6.2. Heartbeat Resources

Check item	ID	Message	Action
Ping check on hb	4011	Failed.	Check if the ping (ping6) command is available.
	4012	Ping could not reach to %1.	Check if an IP address reachable with a ping is set.

4.6.3. Others

Check item	ID	Message	Action
Checking if SELinux is disabled	5021	Failed.	Check if the getenforce command is available.
	5022	SELinux has not been disabled.	Disable SELinux. For the procedure, see "Installation Guide" - "SELinux settings (Required)". If you have enabled SELinux through the procedure described in the above document, ignore this error message.
Kernel check	5031	Unsupported kernel found. Please check the supported kernel version.	Check the supported kernel version.
Presence check for zip command	5051	Failed.	Check if the which command is available.
	5052	zip command is not found.	Install the zip command.

4.6.4. Unrecommended settings check

Check item	ID	Message	Action
Recovery action check for deactivation failure(%1)	6001	"No operation" is set for Recovery Operation at Deactivation Failure Detection. It is recommended to select any other value.	It is recommended to select a value other than "No operation" for the final action on deactivation failure detection.