11. Error messages¶
This chapter provides information on error messages you might encounter in operating EXPRESSCLUSTER.
This chapter covers:
11.2. Messages reported by syslog, alert, mail, SNMP trap, and Message Topic
11.4. Detailed information in activating and deactivating group resources
11.1. Messages¶
EXPRESSCLUSTER X 5.1 does not support event log (syslog) monitoring of NEC ESMPRO Agent.
EXPRESSCLUSTER X 5.1 does not notify events occurring on EXPRESSCLUSTER to NEC Express Report Service.
11.2. 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 the 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 details of E-mail report and SNMP trap sending, see "Alert Service tab" in "2. Parameter details" and "Alert Service" in "Information on other settings".
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 "2. Parameter details" - "2.2. Cluster properties" - "2.2.19. Cloud tab".
Note
facility = daemon (0x00000018), identity = "expresscls" are displayed on syslogs. The "Event type" on the following list is the log level of the syslog.
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 |
Description |
Solution |
1 |
2 |
3 |
4 |
5 |
---|---|---|---|---|---|---|---|---|---|---|
pm |
Info |
1 |
Starting the cluster daemon... |
The EXPRESSCLUSTER daemon has started normally. |
- |
o |
o |
|||
pm |
Info |
2 |
Shutting down the cluster daemon... |
The EXPRESSCLUSTER daemon is stopping. |
- |
o |
o |
|||
pm |
Info |
3 |
Shutdown monitoring is started... |
Shutdown monitoring has started. |
- |
o |
o |
|||
pm |
Error |
10 |
The cluster daemon has already started. |
The EXPRESSCLUSTER daemon has already started. |
Check the status of the EXPRESSCLUSTER daemon. |
o |
o |
|||
pm |
Error |
11 |
A critical error occurred in the cluster daemon. |
A critical error has occurred in the EXPRESSCLUSTER daemon. |
Check the following possible causes: the execution user has no root permission, there is a memory shortage, or OS resources are insufficient. |
o |
o |
o |
o |
o |
pm |
Error |
12 |
A problem was detected in XML library. |
A problem was detected in the XML library. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
pm |
Error |
13 |
A problem was detected in cluster configuration data. |
A problem was detected in the cluster configuration data. |
Using the Cluster WebUI, check the cluster configuration data. |
o |
o |
o |
o |
o |
pm |
Error |
14 |
No cluster configuration data is found. |
There is no cluster configuration data. |
Create the cluster configuration with the Cluster WebUI and upload it to all servers in the cluster. |
o |
o |
|||
pm |
Error |
15 |
No information about this server is found in the cluster configuration data. |
Information about the local server is not found in the cluster configuration data. |
Using the Cluster WebUI, check the cluster configuration data. |
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 was terminated abnormally. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
o |
o |
o |
pm |
Error |
21 |
The system will be stopped because the cluster daemon process terminated abnormally. |
The system will stop because the EXPRESSCLUSTER daemon process terminated abnormally. |
Deactivation of the group resource may fail. Take appropriate action according to the group resource message. |
o |
o |
|||
pm |
Error |
22 |
An error occurred when initializing process %1.(return code:%2) |
An error occurred in initializing process %1. |
The event process may not yet have been started. See "Troubleshooting". |
o |
o |
o |
o |
o |
pm |
Info |
23 |
The system will be stopped. |
The system will be stopped. |
- |
o |
o |
|||
pm |
Info |
24 |
The cluster daemon will be stopped. |
The EXPRESSCLUSTER daemon will be stopped. |
- |
o |
o |
|||
pm |
Info |
25 |
The system will be rebooted. |
The system will be rebooted. |
- |
o |
o |
|||
pm |
Info |
26 |
Process %1 will be restarted. |
Process %1 will be restarted. |
- |
o |
o |
|||
pm |
Info |
30 |
Received a request to stop the system from %1. |
A system stop request was received from %1. |
- |
o |
o |
|||
pm |
Info |
31 |
Received a request to stop the cluster daemon from %1. |
An EXPRESSCLUSTER daemon stop request was received from %1. |
- |
o |
o |
|||
pm |
Info |
32 |
Received a request to reboot the system from %1. |
A system reboot request was received from %1. |
- |
o |
o |
|||
pm |
Info |
33 |
Received a request to restart the cluster daemon from %1. |
An EXPRESSCLUSTER daemon reboot request was received from %1. |
- |
o |
o |
|||
pm |
Info |
34 |
Received a request to resume the cluster daemon from %1. |
A cluster resume request was received from %1. |
- |
o |
o |
|||
pm |
Info |
35 |
Received a request to suspend the cluster daemon from %1. |
A cluster suspend request was received from %1. |
- |
o |
o |
|||
pm |
Info |
36 |
Received a request to panic by sysrq from %1. |
A panic request by sysrq was received from %1. |
- |
o |
o |
|||
pm |
Info |
37 |
Received a request to reset by keepalive driver from %1. |
A reset request by the keepalive driver was received from %1. |
- |
o |
o |
|||
pm |
Info |
38 |
Received a request to panic by keepalive driver from %1. |
A panic request by the keepalive driver was received from %1. |
- |
o |
o |
|||
pm |
Info |
39 |
Received a request to reset by BMC from %1. |
A reset request by BMC was received from %1. |
- |
o |
o |
|||
pm |
Info |
40 |
Received a request to power down by BMC from %1. |
A power down request by BMC was received from %1. |
- |
o |
o |
|||
pm |
Info |
41 |
Received a request to power cycle by BMC from %1. |
A power cycle request by BMC was received from %1. |
- |
o |
o |
|||
pm |
Info |
42 |
Received a request to send NMI by BMC from %1. |
An NMI send request by BMC was received from %1. |
- |
o |
o |
|||
pm |
Info |
43 |
Waiting for resource %1 to stop has canceled. However, resource stop continues. |
Waiting for resource %1 to stop has canceled. However, resource stop continues. |
- |
o |
||||
pm |
Info |
44 |
Received a request to emergently stop the system from %1. |
An emergent system stop request was received from %1. |
- |
o |
o |
|||
pm |
Info |
45 |
Received a request to emergently reboot the system from %1. |
An emergent system reboot request was received from %1. |
- |
o |
o |
|||
pm |
Error |
66 |
An attempt to panic by sysrq from %1 failed. |
An attempt was made to cause a panic by sysrq from %1, but failed. |
Check whether the system is configured so that it can use sysrq. |
o |
o |
|||
pm |
Error |
67 |
An attempt to reset by keepalive driver from %1 failed. |
An attempt was made to cause a reset by the keepalive driver from %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
pm |
Error |
68 |
An attempt to panic by keepalive driver from %1 failed. |
An attempt was made to cause a panic by the keepalive driver from %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
pm |
Error |
69 |
An attempt to reset by BMC from %1 failed. |
An attempt was made to cause a reset by BMC from %1, but 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 was made to cause power down by BMC from %1, but 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 was made to cause a power cycle by BMC from %1, but 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 was made to perform an NMI transmission by BMC from %1, but failed. |
Check whether the ipmitool command can be used. |
o |
o |
|||
pm |
Info |
100 |
The system will be panic by sysrq. |
The system will be panicked by sysrq. |
- |
o |
o |
|||
pm |
Info |
101 |
The system will be reset by ka. |
The system will be reset by the keep alive driver. |
- |
o |
o |
|||
pm |
Info |
102 |
The system will be panic by ka. |
The system will be panicked by the keep alive driver. |
- |
o |
o |
|||
pm |
Info |
103 |
The system will be reset by bmc. |
The system will be reset by BMC. |
- |
o |
o |
|||
pm |
Info |
104 |
The system will be off by bmc. |
The system will be turned OFF by BMC. |
- |
o |
o |
|||
pm |
Info |
105 |
The system will be cycle by bmc. |
The system will be turned OFF and then back ON by BMC. |
- |
o |
o |
|||
pm |
Info |
106 |
The system will be nmi by bmc. |
The system will be NMI-transmitted by BMC. |
- |
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 all servers to start has started. |
- |
o |
o |
|||
nm |
Info |
6 |
All servers have started. |
All servers have started. |
- |
o |
o |
|||
nm |
Info |
7 |
Timeout occurred during the wait for startup of all servers. |
Waiting for all servers to start has timed out. |
- |
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 has timed out. (Internal communication with some servers is impossible.) |
Check whether there is a network adaptor error and that the network is connected properly. |
o |
o |
|||
nm |
Info |
9 |
Waiting for startup of all servers has been canceled. |
Waiting for servers to start has been canceled. |
- |
o |
o |
|||
nm |
Error |
10 |
Status of resource %1 of server %2 is unknown. |
The status of resource %1 of server %2 is unknown. |
Check that cable for resource %1 and the network are set correctly. |
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 was terminated abnormally. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
o |
o |
o |
nm |
Info |
21 |
The system will be stopped. |
The system will be stopped. |
- |
o |
o |
|||
nm |
Info |
22 |
The cluster daemon will be stopped. |
The EXPRESSCLUSTER daemon will be stopped. |
- |
o |
o |
|||
nm |
Info |
23 |
The system will be rebooted. |
The system will be rebooted. |
- |
o |
o |
|||
nm |
Info |
24 |
Process %1 will be restarted. |
Process %1 will be restarted. |
- |
o |
o |
|||
nm |
Error |
30 |
Network partition was detected. Shut down the server %1 to protect data. |
A network partition was detected. Server %1 is shut down to protect the data. |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
31 |
An error occurred while confirming the network partition. Shut down the server %1. |
A problem occurred while the network partition was being checked. Server %1 is shut down to protect data. |
Check whether there is an error in the network partition resolution resource. |
o |
o |
|||
nm |
Error |
32 |
Shut down the server %1. (reason:%2) |
Server %1 is shut down. (Reason: %2) |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
33 |
Cluster service will be stopped. (reason:%1) |
The cluster service will be stopped. (Reason: %1) |
Remove the factor indicated in "reason". |
o |
o |
|||
nm |
Error |
34 |
The combination of the network partition resources is invalid. (server name:%1) |
The combination of the network partition resolution resources is invalid. (Server name: %1) |
Check the cluster configuration data. |
o |
o |
|||
nm |
Error |
35 |
Failed to start the resource %1. Server name:%2 |
Resource %1 failed to start. (Server name: %2) |
Check whether there is an error 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. |
Network partition %1 of server %2 is abnormal. |
Check whether there is an error in the network partition resolution resource. |
o |
o |
|||
nm |
Error |
38 |
The resource %1 of the server %2 is unknown. |
Resource %1 of server %2 is unknown. |
Check the cluster configuration data. |
o |
o |
|||
nm |
Info |
39 |
The server %1 canceled the pending failover. |
Server %1 canceled the failover. |
- |
o |
o |
|||
nm |
Error |
40 |
Network partition was detected. Stop the cluster service on the server %1 to protect data. |
A network partition was detected. The cluster service of server %1 is stopped to protect the data. |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
41 |
An error occurred while confirming the network partition. Stop the cluster service on the server %1. |
A problem occurred while the network partition was being checked. The cluster service of server %1 is stopped to protect data. |
Check whether there is an error in the network partition resolution resource. |
o |
o |
|||
nm |
Error |
42 |
Network partition was detected. Reboot the cluster service on the server %1 to protect data. |
A network partition was detected. Server %1 is reboot to protect the data. |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
43 |
Network partition was detected. Execute action(%1) on the server %2 to protect data. |
A network partition was detected. Execute action(%1) on the server %2 to protect data. |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
44 |
An error occurred while confirming the network partition. Reboot the server %1. |
A problem occurred while the network partition was being checked. Server %1 is reboot to protect data. |
Check whether there is an error in the network partition resolution resource. |
o |
o |
|||
nm |
Error |
45 |
An error occurred while confirming the network partition. Execute action(%1) on the server %2. |
A problem occurred while the network partition was being checked. Execute action(%1) on the server %2. |
Check whether there is an error in the network partition resolution resource. |
o |
o |
|||
nm |
Error |
46 |
Reboot the server %1. (reason:%2) |
Server %1 is reboot. (Reason: %2) |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
47 |
Execute action(%1) on the server %2. (reason:%3) |
Execute action(%1) on the server %2. (reason:%3) |
All heartbeats cannot be used. Check whether there is a network adaptor error and that the network is connected properly. Check the status of the shared disk if DISKHB is in use. |
o |
o |
|||
nm |
Error |
80 |
Cannot communicate with server %1. |
Internal communication with server %1 is impossible. |
Check whether there is a network adaptor error and that the network is connected properly. |
o |
o |
|||
nm |
Info |
81 |
Recovered from internal communication error with server %1. |
Internal communication with server %1 has been recovered from the abnormal status. |
- |
o |
o |
|||
rc |
Info |
10 |
Activating group %1 has started. |
Activating group %1 has started. |
- |
o |
o |
|||
rc |
Info |
11 |
Activating group %1 has completed. |
Activating group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
12 |
Activating group %1 has failed. |
Activating group %1 has failed. |
Take appropriate action 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 has been canceled because waiting for group %1 to start has 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. |
Stopping group %1 has started. |
- |
o |
o |
|||
rc |
Info |
21 |
Stopping group %1 has completed. |
Stopping group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
22 |
Stopping group %1 has failed. |
Stopping group %1 has failed. |
Take appropriate action 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 start group %2. |
A server on which an absolute exclusion group has already started cannot start another absolute exclusion group. Stop the existing absolute exclusion group and then reexecute. |
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. |
Activating resource %1 has started. |
- |
o |
||||
rc |
Info |
31 |
Activating %1 resource has completed. |
Activating resource %1 has been completed. |
- |
o |
||||
rc |
Error |
32 |
Activating %1 resource has failed.(%2 : %3) |
Activating resource %1 has failed. |
See "Detailed information in activating and deactivating group resources". If a stall occurs during start processing, "Activating %1 resource has failed.(99 : command is timeout)" is output. |
o |
o |
o |
o |
o |
rc |
Info |
33 |
A request to activate %1 resource on server %2 has been started. |
A request to activate resource %1 on server %2 has been started. |
- |
o |
o |
|||
rc |
Info |
34 |
A request to activate %1 resource on server %2 has been completed. |
A request to activate resource %1 on server %2 has been completed. |
- |
o |
o |
|||
rc |
Error |
35 |
A request to activate %1 resource on server %2 has been failed. |
A request to activate resource %1 on server %2 has been failed. |
Check if there is a network error or there is an error with the remote server. |
o |
o |
|||
rc |
Info |
36 |
Since the startup attribute is set to manual, the activation of resource %1 was suppressed. |
Since the startup attribute is set to manual, the activation of resource %1 was suppressed. |
- |
o |
o |
|||
rc |
Info |
40 |
Stopping %1 resource has started. |
Stopping resource %1 has started. |
- |
o |
||||
rc |
Info |
41 |
Stopping %1 resource has completed. |
Stopping resource %1 has been completed. |
- |
o |
||||
rc |
Error |
42 |
Stopping %1 resource has failed.(%2 : %3) |
Stopping resource %1 has failed. |
See "Detailed information in activating and deactivating group resources". If a stall occurs during stop processing, "Stopping %1 resource has failed.(99 : command is timeout)" is output. |
o |
o |
o |
o |
o |
rc |
Info |
44 |
A request to stop %1 resource on server %2 has been started. |
A request to stop resource %1 on server %2 has been started. |
- |
o |
o |
|||
rc |
Info |
45 |
A request to stop %1 resource on server %2 has been completed. |
A request to stop resource %1 on server %2 has been completed. |
- |
o |
o |
|||
rc |
Error |
46 |
A request to stop %1 resource on server %2 has been failed. |
A request to stop resource %1 on server %2 has been failed. |
Check if there is a network error or there is an error with the remote server. |
o |
o |
|||
rc |
Info |
50 |
Moving group %1 has started. |
Moving group %1 has started. |
- |
o |
o |
|||
rc |
Info |
51 |
Moving group %1 has completed. |
Moving group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
52 |
Moving group %1 has failed. |
Moving group %1 has failed. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
55 |
Migrating group %1 has started. |
Migrating group %1 has started. |
- |
o |
o |
|||
rc |
Info |
56 |
Migrating group %1 has completed. |
Migrating group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
57 |
Migrating group %1 has failed. |
Migrating group %1 has failed. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Warning |
58 |
Server %1 is not in a condition to migrate group %2. |
Server %1 cannot make group %2 migrate. |
Check the status of the migration destination server. If no migration destination server exists, the server name is not output to %1. |
o |
o |
|||
rc |
Info |
60 |
Failover group %1 has started. |
Failover of group %1 has started. |
- |
o |
o |
|||
rc |
Info |
61 |
Failover group %1 has completed. |
Failover of group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
62 |
Failover group %1 has failed. |
Failover of group %1 has failed. |
Take appropriate action 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 move group %2. |
Check the status of the movement destination server.
If no movement destination server exists, 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 failover destination of group %2. (Reason: %3) |
- |
o |
o |
|||
rc |
Error |
65 |
There is no appropriate destination for the group %1 (reason: %2). |
There is no appropriate failover destination for group %1. (Reason: %2) |
There is no server that can provide failover. The server is stopping or a monitor resource error disabling failover is occurring. Start the server, remove the cause of the monitor resource error, or stop the monitor resource in which the error is detected. |
o |
o |
|||
rc |
Warning |
66 |
Server %1 is not in a condition to start group %2 (reason: %3). |
Server %1 cannot start group %2. (Reason: %2) |
There is a monitor resource error that is disabling group start. Remove the cause of the monitor resource error, or stop the monitor resource in which the error is detected. |
o |
o |
|||
rc |
Info |
67 |
Server %1 in the same server group (%2) has been set as the destination for the group %3. |
Server %1 in the same server group %2 has been set as the failover destination of group %3. |
- |
o |
o |
|||
rc |
Info |
68 |
Server %1 not in the same server group (%2) has been set as the destination for the group %3. |
Server %1 in a server group other than server group %2 has been set as the failover destination of group %3. |
- |
o |
o |
|||
rc |
Warning |
69 |
Can not failover the group %1 because there is no appropriate destination in the same server group %2. |
Server group %2 does not contain the server that can perform failover for group %1. |
Start the group after starting the server in the server group or start the group with the server in another server group. |
o |
o |
|||
rc |
Info |
70 |
Restarting group %1 has started. |
Reactivating group %1 has started. |
- |
o |
o |
|||
rc |
Info |
71 |
Restarting group %1 has completed. |
Reactivating group %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
72 |
Restarting group %1 has failed. |
Reactivating group %1 has failed. |
Take appropriate action 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 |
Error |
77 |
Failover some groups have failed since the server cannot communicate with some servers. |
Failed to failover some groups because of no internal communication to some servers. |
Check the status of LAN heartbeat and kernel mode LAN heartbeat. After recovering the internal communication, restart the group. |
o |
o |
|||
rc |
Info |
80 |
Restarting resource %1 has started. |
Reactivating resource %1 has started. |
- |
o |
o |
|||
rc |
Info |
81 |
Restarting resource %1 has completed. |
Reactivating resource %1 has been completed. |
- |
o |
o |
|||
rc |
Error |
82 |
Restarting resource %1 has failed. |
Reactivating resource %1 has failed. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
83 |
Starting a single resource %1. |
Single resource %1 is started. |
- |
o |
o |
|||
rc |
Info |
84 |
A single resource %1 has been started. |
Single resource %1 has been started. |
- |
o |
o |
|||
rc |
Error |
85 |
Failed to start a single resource %1. |
Single resource %1 failed to start. |
Take appropriate action 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 start single source %2. |
Check the server and group status. |
o |
o |
|||
rc |
Info |
87 |
Stopping a single resource %1. |
Single resource %1 is stopped. |
- |
o |
o |
|||
rc |
Info |
88 |
A single resource %1 has been stopped. |
Single resource %1 has been stopped. |
- |
o |
o |
|||
rc |
Error |
89 |
Failed to stop a single resource %1. |
Single resource %1 failed to stop. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
90 |
All the servers in the cluster were shut down. |
The cluster has been stopped. |
- |
o |
o |
|||
rc |
Info |
91 |
The server was shut down. |
The server has been stopped. |
- |
o |
o |
|||
rc |
Error |
92 |
Group %1 has started on more than one server. |
Group %1 has started on two or more servers. |
The server is automatically shut down. See "Recovery from network partitioning" in "The system maintenance information" in the "Maintenance Guide". |
o |
o |
o |
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 is not executed. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
160 |
Script before final action upon %1 failure in resource %2 started. |
The script (%1) before the final action at failure in resource (%2) has started. |
- |
o |
o |
|||
rc |
Info |
161 |
Script before final action upon %1 failure in resource %2 completed. |
The script (%1) before the final action at failure in resource (%2) has been completed. |
- |
o |
o |
|||
rc |
Info |
162 |
Script %1 in resource %2 started |
Script (%1) of resource (%2) has started. |
- |
o |
o |
|||
rc |
Info |
163 |
Script %1 in resource %2 completed |
Script (%1) of resource (%2) has been completed. |
- |
o |
o |
|||
rc |
Error |
180 |
Script %1 before final action upon failure in resource %2 failed. |
The script (%1) before the final action at failure in resource (%2) has failed. |
Check the cause of the script failure and take appropriate action. |
o |
o |
|||
rc |
Error |
181 |
Failed to execute script %1 in resource %2.(%3) |
Script (%1) of resource (%2) has failed. |
Same as above. |
o |
o |
|||
rc |
Info |
200 |
Resource(%1) will be reactivated since activating resource(%2) failed. |
Resource %2 is reactivated since resource %1 could not be activated. |
Take appropriate action 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 is moved to server %2 since resource %3 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
202 |
Group(%1) will be stopped since activating resource(%2) failed. |
Group %1 is stopped since resource %2 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
203 |
Cluster daemon will be stopped since activating resource(%1) failed. |
The cluster daemon is stopped since resource %1 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
204 |
System will be halted since activating resource(%1) failed. |
The OS is shut down since resource %1 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
205 |
System will be rebooted since activating resource(%1) failed. |
The OS is rebooted since resource %1 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
206 |
Activating group(%1) will be continued since failover process failed. |
Activating group %1 is continued since the failover failed. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
220 |
Resource(%1) will be stopping again since stopping resource(%2) failed. |
Deactivation of resource %1 is retried since resource %2 could not be deactivated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
222 |
Group(%1) will be stopped since stopping resource(%2) failed. |
Group %1 is stopped since resource %2 could not be deactivated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
223 |
Cluster daemon will be stopped since stopping resource(%1) failed. |
The cluster daemon is stopped since resource %1 could not be deactivated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
224 |
System will be halted since stopping resource(%1) failed. |
The OS is stopped since resource %1 could not be deactivated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
225 |
System will be rebooted since stopping resource(%1) failed. |
The OS is rebooted since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
244 |
System power down by BMC is requested since activating resource(%1) failed. |
System power down by BMC is requested since resource %1 could not be activated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action 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 is requested since resource %1 could not be activated. |
Take appropriate action 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 was made to cause a system panic by sysrq due to an activation failure in resource %1, but failed. |
Check whether the system is configured so that it can use sysrq. |
o |
o |
|||
rc |
Error |
261 |
An attempt to reset system by keepalive driver due to failure of resource(%1) activation failed. |
An attempt was made to cause a system reset by the keepalive driver due to an activation failure in resource %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
rc |
Error |
262 |
An attempt to panic system by keepalive driver due to failure of resource(%1) activation failed. |
An attempt was made to cause a system panic by the keepalive driver due to an activation failure in resource %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
rc |
Error |
263 |
An attempt to reset system by BMC due to failure of resource(%1) activation failed. |
An attempt was made to cause a system reset by BMC due to an activation failure in resource %1, but 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 was made to cause system power down by BMC due to an activation failure in resource %1, but 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 was made to cause system power cycle by BMC due to an activation failure in resource %1, but 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 was made to perform NMI transmission by BMC due to an activation failure in resource %1, but 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 is requested since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be deactivated. |
Take appropriate action according to the group resource message. |
o |
o |
|||
rc |
Info |
284 |
System power down by BMC is requested since deactivating resource(%1) failed. |
System power down by BMC is requested since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be deactivated. |
Take appropriate action 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 is requested since resource %1 could not be deactivated. |
Take appropriate action 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 was made to cause a system panic by sysrq due to a deactivation failure in resource %1, but failed. |
Check whether the system is configured so that it can use sysrq. |
o |
o |
|||
rc |
Error |
301 |
An attempt to reset system by keepalive driver due to failure of resource(%1) deactivation failed. |
An attempt was made to cause a system reset by the keepalive driver due to a deactivation failure in resource %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
rc |
Error |
302 |
An attempt to panic system by keepalive driver due to failure of resource(%1) deactivation failed. |
An attempt was made to cause a system panic by the keepalive driver due to a deactivation failure in resource %1, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
o |
o |
|||
rc |
Error |
303 |
An attempt to reset system by BMC due to failure of resource(%1) deactivation failed. |
An attempt was made to cause a system reset by BMC due to a deactivation failure in resource %1, but 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 was made to cause system power down by BMC due to an deactivation failure in resource %1, but 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 was made to cause system power cycle by BMC due to a deactivation failure in resource %1, but 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 was made to perform NMI transmission by BMC due to a deactivation failure in resource %1, but 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 |
350 |
Group %1 started to check the double activation. |
Checking the double activation started. |
- |
|||||
rc |
Info |
351 |
Group %1 completed to check the double activation. |
Checking the double activation ended. |
- |
|||||
rc |
Error |
352 |
Group %1 failed to check the double activation. |
Checking the double activation failed. |
Check the status of the group. |
o |
o |
|||
rc |
Info |
353 |
Waiting for group %1 to start for check the double activation. |
Group start continues for check the double activation. |
Check the status of the group. |
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 |
433 |
Group failover has been canceled because forced stop of server %1 failed. |
Suppression of failover for forced stop failed |
Check the cause of the forced stop failed and take measures. |
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 |
460 |
The group %1 which were activated on the server %2 will be activated on the same server because its reboot has been completed within the heartbeat timeout. |
The group %1 which were activated on the server %2 will be activated on the same server because its reboot has been completed within the heartbeat timeout. |
Adjust the OS startup time so that the server reboot is not completed before the heartbeat timeout occurs. |
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 |
502 |
Since server %1 is specified as that which suppresses shutdown at both-system activation detection, it ignored the shutdown request. |
Suppression of shutdown caused by both-system activation detection. |
- |
o |
o |
|||
rc |
Warning |
503 |
A mismatch in the group %1 status occurs between the servers. |
Generation of group status mismatch |
Restart the group or reboot the cluster. |
o |
o |
|||
rc |
Info |
504 |
Since server %1 is not specified as that which suppresses shutdown at both-system activation detection, it executed the shutdown request. |
Since server %1 is not specified as that which suppresses shutdown at both-system activation detection, it executed the shutdown request. |
- |
o |
o |
|||
rc |
Warning |
510 |
Cluster operation is disabled. |
Cluster operation is disabled. |
- |
o |
o |
|||
rc |
Warning |
511 |
Ignored the automatic start of groups because automatic group startup is disabled. |
The automatic start of groups was ignored because automatic group start has been disabled. |
- |
o |
o |
|||
rc |
Warning |
512 |
Ignored the recovery action in resource activation because recovery action caused by group resource activation error is disabled. |
The recovery action in resource activation was ignored because recovery action against group resource activation error has been disabled. |
- |
o |
o |
|||
rc |
Warning |
513 |
Ignored the recovery action in resource deactivation because recovery action caused by group resource deactivation error is disabled. |
The recovery action in resource deactivation was ignored because recovery action against group resource deactivation error has been disabled. |
- |
o |
o |
|||
rc |
Info |
514 |
Cluster operation is set disabled. |
Cluster operation is disabled. |
- |
o |
o |
|||
rc |
Info |
515 |
Cluster operation is set enabled. |
Cluster operation 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. |
Monitoring %1 has started. |
- |
o |
o |
|||
rm |
Info |
2 |
Monitoring %1 has stopped. |
Monitoring %1 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) |
Warning of monitoring %1 is issued. |
See "Detailed info of 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. |
Using the Cluster WebUI, check the cluster configuration data. |
o |
o |
|||
rm |
Warning |
6 |
Monitor configuration of %1 is invalid. (%2 : %3) |
The monitor configuration of %1 is invalid. |
Using the Cluster WebUI, check the cluster configuration data. |
o |
o |
|||
rm |
Error |
7 |
Failed to start monitoring %1. |
Starting of monitoring %1 failed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
o |
o |
o |
rm |
Error |
8 |
Failed to stop monitoring %1. |
Stopping of monitoring %1 failed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm |
Error |
9 |
Detected an error in monitoring %1. (%2 : %3) |
An error was detected in monitoring %1. |
o |
o |
o |
o |
o |
|
If a monitoring timeout is detected, the following message is set in (). (99 : Monitor was timeout.) |
o |
o |
o |
o |
o |
|||||
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.) |
o |
o |
o |
o |
o |
|||||
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 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 in monitoring %2. |
- |
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 in monitoring %2. |
- |
o |
o |
|||
rm / mm |
Info |
14 |
Recovery target %1 failed over because an error was detected in monitoring %2. |
Recovery target %1 has failed over because an error was detected in monitoring %2. |
- |
o |
o |
|||
rm / mm |
Info |
15 |
Stopping the cluster has been required because an error was detected in monitoring %1. |
A cluster stop is requested because an error was detected in monitoring %1. |
- |
o |
o |
|||
rm / mm |
Info |
16 |
Stopping the system has been required because an error was detected in monitoring %1. |
A system stop is requested because an error was detected in monitoring %1. |
- |
o |
o |
|||
rm / mm |
Info |
17 |
Rebooting the system has been required because an error was detected in monitoring %1. |
A system restart is requested because an error was detected in monitoring %1. |
- |
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 was made to stop recovery target %1 due to a %2 monitoring failure, but 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 was made to restart recovery target %1 due to a %2 monitoring failure, but 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 was made to provide failover for recovery target %1 due to a %2 monitoring failure, but 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 was made to stop the cluster due to a %1 monitoring failure, but failed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm / mm |
Error |
22 |
Attempted to stop the system due to the error detected in monitoring %1, but failed. |
An attempt was made to stop the system due to a %1 monitoring failure, but failed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm / mm |
Error |
23 |
Attempted to reboot the system due to the error detected in monitoring %1, but failed. |
An attempt was made to restart the system due to a %1 monitoring failure, but failed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm |
Error |
24 |
The group of %1 resource is unknown. |
The group of resource %1 is unknown. |
The cluster configuration information may be mismatched. Check it. |
o |
o |
|||
rm / mm |
Warning |
25 |
Recovery will not be executed since the recovery target %1 is not active. |
Recovery is not performed since recovery target %1 is not active. |
- |
o |
o |
|||
rm / mm |
Info |
26 |
%1 status changed from error to normal. |
Monitoring %1 has changed from error to normal. |
- |
o |
o |
|||
rm / mm |
Info |
27 |
%1 status changed from error or normal to unknown. |
Monitoring %1 has changed from abnormal or normal to unknown. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm |
Error |
28 |
Initialization error of monitor process. (%1 : %2) |
An error occurred while initializing the monitor process. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
rm |
Info |
29 |
Monitoring %1 was suspended. |
Monitoring %1 has temporarily stopped. |
- |
o |
o |
|||
rm |
Info |
30 |
Monitoring %1 was resumed. |
Monitoring %1 has restarted. |
- |
o |
o |
|||
rm |
Info |
31 |
All monitors were suspended. |
All monitoring processes have temporarily stopped. |
- |
o |
o |
|||
rm |
Info |
32 |
All monitors were resumed. |
All monitoring processes have restarted. |
- |
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 is requested because an error was detected in monitoring %1. |
- |
o |
o |
|||
rm / mm |
Error |
36 |
Attempted to panic system by sysrq due to the error detected in monitoring %1, but failed. |
An attempt was made to cause a system panic by sysrq due to a %1 monitoring failure, but failed. |
Check whether the system is configured so that it can use 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 is requested because an error was detected in monitoring %1. |
- |
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 was made to cause a system reset by the keepalive driver due to a %1 monitoring failure, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
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 is requested because an error was detected in monitoring %1. |
- |
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 was made to cause a system panic by the keepalive driver due to a %1 monitoring failure, but failed. |
Check whether the established environment supports the use of the keepalive driver. |
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 is requested because an error was detected in monitoring %1. |
- |
o |
o |
|||
rm / mm |
Error |
42 |
Attempted to reset system by BMC due to the error detected in monitoring %1, but failed. |
An attempt was made to cause a system reset by BMC due to a %1 monitoring failure, but 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. |
System power down by BMC is requested because an error was detected in monitoring %1. |
- |
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 was made to cause a system power down by BMC due to a %1 monitoring failure, but 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. |
System power cycle by BMC is requested because an error was detected in monitoring %1. |
- |
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 was made to cause a system power down by BMC due to a %1 monitoring failure, but 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. |
System NMI transmission by BMC is requested 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. |
An attempt was made to cause a system NMI transmission by BMC due to a %1 monitoring failure, but failed. |
Check whether the ipmitool command can be used. |
o |
o |
|||
rm |
Info |
49 |
%1 status changed from warning to normal. |
%1 status changed from warning to normal. |
- |
o |
o |
|||
rm |
Error |
57 |
Stopping the cluster is required since license (%1) is invalid. |
Stopping the cluster is requested due to an invalid license. |
Register a valid license. |
o |
o |
o |
o |
o |
rm |
Error |
58 |
Stopping the cluster due to invalid license (%1) failed. |
Stopping the cluster due to an invalid license has failed. |
Register a valid license. |
o |
o |
|||
rm |
Warning |
60 |
Cluster operation is forcibly disabled since a valid license has not been registered. |
Cluster operation is forcibly disabled since a valid license has not been registered. |
Register the license. Canceling the forcible disablement of cluster operation requires up to 1 hour after the license is registered. To cancel it immediately, suspend and resume the cluster after the license registration. |
o |
o |
|||
rm |
Info |
61 |
The forcible disablement of cluster operation was canceled since the valid licenses are registered. |
The forcible disablement of cluster operation was canceled since the valid licenses are registered. |
- |
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 in monitoring %1. The current timeout value is %2 (tick count). The actual measurement value at delay detection is %3 (tick count) and exceeded the delay warning rate %4 (%). |
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. |
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 |
|||
Script before %1 upon failure in monitor resource %2 started. |
Script before %1 of monitor resource %2 has started. |
- |
o |
o |
||||||
rm / mm |
Info |
82 |
Script before %1 upon failure in monitor resource %2 completed. |
Script before %1 of monitor resource %2 has been completed. |
- |
o |
o |
|||
rm / mm |
Error |
83 |
Script before %1 upon failure in monitor resource %2 failed. |
Script before %1 of monitor resource %2 has failed. |
Check the cause of the script failure and take appropriate action. |
o |
o |
|||
rm |
Warning |
100 |
Restart count exceeded the maximum of %1. Final action of monitoring %2 will not be executed. |
Because the restart count has exceeded the maximum value %1, the final action of %2 was not executed. |
- |
o |
o |
|||
rm |
Warning |
120 |
The virtual machine (%1) has been migrated to %2 by an external operation. |
The virtual machine managed by resource %1 was made to migrate to server %2 through external operation. |
- |
o |
o |
|||
rm |
Warning |
121 |
The virtual machine (%1) has been started by an external operation. |
The virtual machine managed by resource %1 was started by external operation. |
- |
o |
o |
|||
rm |
Info |
130 |
The collecting of detailed information triggered by monitor resource %1 error has been started (timeout=%2). |
Collecting of detailed information triggered by detection of a monitor resource %1 monitoring error has started. The timeout is %2 seconds. |
- |
o |
o |
|||
rm |
Info |
131 |
The collection of detailed information triggered by monitor resource %1 error has been completed. |
Collecting of detailed information triggered by detection of a monitor resource %1 monitoring error has been completed. |
- |
o |
o |
|||
rm |
Warning |
132 |
The collection of detailed information triggered by monitor resource %1 error has been failed (%2). |
Collecting of detailed information triggered by detection of a monitor resource %1 monitoring error 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. |
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 |
51 |
The trial license is effective until %1. (%2) |
The trial license is effective until %1. |
- |
o |
o |
|||
mm |
Error |
53 |
The license is not registered. (%1) |
The license is not registered. |
Purchase the license and then register it. |
o |
o |
|||
mm |
Error |
54 |
The trial license has expired in %1. (%2) |
The validity term of the trial license has expired. |
Register a valid license. |
o |
o |
|||
mm |
Error |
55 |
The registered license is invalid. (%1) |
The registered license is invalid. |
Register a valid license. |
o |
o |
|||
mm |
Error |
56 |
The registered license is unknown. (%1) |
The registered license is unknown. |
Register a valid license. |
o |
o |
|||
mm |
Error |
59 |
The trial license is valid from %1. (%2) |
The validity term of the trial license is not reached. |
Register a valid license. |
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 |
|||
mm |
Info |
913 |
Received a Fatal Trap from %1. (msg : No data) |
A Fatal Trap was received from the server %1. The message does not contain any information . |
- |
o |
o |
|||
mm |
Info |
914 |
Received a Fatal Trap from %1. (msg : %2) |
A Fatal Trap was received from the server %1. The message contains information (%2). For information about %2 (failure region), see the Device Maintenance Guide 1 . |
- |
o |
o |
|||
mm |
Warning |
915 |
Received a Recoverable Trap.(Performance degradation) (msg : %1) |
A Recoverable Trap was received. (Performance degradation was detected.). The message contains information (%1). For information about %1 (failure region), see the Device Maintenance Guide 1 . |
- |
o |
o |
|||
mm |
Warning |
916 |
Received a Recoverable Trap.(Predict) (msg : %1) |
A Recoverable Trap was received. (A predictive failure was detected.). The message contains information (%1). For information about %1 (failure region), see the Device Maintenance Guide 1 . |
- |
o |
o |
|||
mm |
Warning |
917 |
Received a Recoverable Trap.(Performance degradation & Predict) (msg : %1) |
A Recoverable Trap was received. (A predictive failure was detected.) The message contains information (%1). For information about %1 (failure region), see the Device Maintenance Guide 1 . |
- |
o |
o |
|||
trnsv |
Error |
1 |
There was a notification from external (IP=%1), but it was denied. |
A notification was received from %1, but was not permitted. |
- |
o |
o |
|||
trnsv |
Info |
10 |
There was a notification (%1) from external (IP=%2). |
A notification (%1) from %2 was accepted. |
- |
o |
o |
|||
trnsv |
Info |
20 |
Recovery action (%1) of monitoring %2 has been executed because a notification arrived from external. |
Recovery action (%1) of monitor resource %2 has started through an external notification. |
- |
o |
o |
|||
trnsv |
Info |
21 |
Recovery action (%1) of monitoring %2 has been completed. |
Recovery action (%1) of monitor resource %2 has been successful. |
- |
o |
o |
|||
trnsv |
Error |
22 |
Attempted to recovery action (%1) of monitoring %2, but it failed. |
An attempt was made to perform recovery action (%1) of monitor resource %2, but failed. |
Check whether the environment supports the recovery action. |
o |
o |
|||
trnsv |
Info |
30 |
Action (%1) has been completed. |
Action (%1) has been successful. |
- |
o |
o |
|||
trnsv |
Error |
31 |
Attempted to execute action (%1), but it failed. |
An attempt was made to perform action (%1), but failed. |
Check whether the environment supports the action. |
o |
o |
|||
trnsv |
Info |
40 |
Script before action of monitoring %1 has been executed. |
Script before the recovery action of monitor resource (%1) has been executed. |
- |
o |
||||
trnsv |
Info |
41 |
Script before action of monitoring %1 has been completed. |
Script before the recovery action of monitor resource (%1) has been executed successfully. |
- |
o |
||||
trnsv |
Error |
42 |
Attempted to execute script before action of monitoring %1, but it failed. |
Script before the recovery action of monitor resource (%1) could not be executed. |
Check whether the script before the recovery action is executable. |
o |
||||
trnsv |
Error |
50 |
The system will be shutdown because cluster resume was failed. |
The system will be shutdown because cluster resume was failed. |
- |
o |
||||
trnsv |
Error |
51 |
An attempt to shutdown the system failed. |
An attempt to shutdown the system failed. |
The system may not be able to operate properly. |
o |
||||
trnsv |
Error |
60 |
The log storage destination (%1) is not found. |
The log storage destination (%1) is not found. |
Check if the specified log storage destination exists. |
o |
o |
|||
trnsv |
Error |
61 |
A path under the installation path is specified for the log storage destination. |
A path under the installation path is specified for the log storage destination. |
For the log storage destination, avoid specifying a path under the installation path. |
o |
o |
|||
trnsv |
Info |
83 |
Starting a dynamic adding resource %1. |
Resource %1 has been dynamically added. |
- |
o |
o |
|||
trnsv |
Info |
84 |
A dynamic adding resource %1 has been started. |
Resource %1 succeeded in being dynamically added. |
- |
o |
o |
|||
trnsv |
Error |
85 |
Failed to a dynamic adding resource %1. |
Resource %1 failed to be dynamically added. |
Take appropriate action according to the group resource message. |
o |
o |
|||
trnsv |
Warning |
86 |
Server %1 is not in a condition to start a dynamic adding resource %2. |
Server %1 cannot dynamically add Resource %2. |
Check the server and group status. |
o |
o |
|||
trnsv |
Info |
87 |
Deleting a resource %1. |
Resource %1 has been deleted. |
- |
o |
o |
|||
trnsv |
Info |
88 |
Deleting a resource %1 has been stopped. |
Resource %1 succeeded in being deleted. |
- |
o |
o |
|||
trnsv |
Error |
89 |
Failed to Delete a resource %1. |
Resource %1 failed to be deleted. |
Take appropriate action according to the group resource message. |
o |
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) |
Heartbeats from HB resource %1 of server %2 are delayed. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server %2 and remove the load. If an HB timeout occurs, extend it. |
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) |
Heartbeats sent from HB resource %1 are delayed. The transmission destination server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
lanhb |
Warning |
73 |
Heartbeats received by HB resource %1 are delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats received by HB resource %1 are delayed. The transmission source server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
lankhb |
Warning |
71 |
Heartbeats sent from HB resource %1 of server %2 are delayed. (timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats from HB resource %1 of server %2 are delayed. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server %2 and remove the load. If an HB timeout occurs, extend it. |
o |
o |
|||
lankhb |
Warning |
73 |
Heartbeats received from HB resource %1 is delayed. (timeout=%2*%3 actual-time=%4 delay warning rate=%5) |
Heartbeats received by HB resource %1 are delayed. The transmission source server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
diskhb |
Error |
10 |
Device(%1) of resource(%2) does not exist. |
No device exists. |
Check the cluster configuration data. |
o |
o |
|||
diskhb |
Error |
11 |
Device(%1) of resource(%2) is not a block device. |
No device exists. |
Check the cluster configuration data. |
o |
o |
|||
diskhb |
Error |
15 |
File system exists on device(%1) of resource(%2). |
Device %1 of resource %2 contains the file system. |
To use device %1, delete the file system. |
o |
o |
|||
diskhb |
Info |
20 |
Resource %1 recovered from initialization error. |
Resource %1 was recovered from an 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) |
Heartbeats from HB resource %1 of server %2 are delayed. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server %2 and remove the load. If an HB timeout occurs, extend it. |
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). |
Heartbeats written by HB resource %1 are delayed. The write destination server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
diskhb |
Warning |
73 |
Heartbeat read of HB resource %1 is delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats read by HB resource %1 are delayed. The read source server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
monp |
Error |
1 |
An error occurred when initializing monitored process %1. (status=%2) |
An error occurred in initializing monitored process %1. |
Check the following possible causes: memory shortage, OS resource insufficiency, or cluster configuration data mismatching. If cluster configuration data has not yet been registered, the following process message is output. However, there is no problem.
|
o |
o |
|||
monp |
Error |
2 |
Monitor target process %1 terminated abnormally. (status=%2) |
Monitored process %1 has terminated abnormally. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
monp |
Info |
3 |
Monitor target process %1 will be restarted. |
Monitored process %1 will be restarted. |
- |
o |
o |
|||
monp |
Info |
4 |
The cluster daemon will be stopped since the monitor target process %1 terminated abnormally. |
The cluster will be stopped since monitored process %1 has terminated abnormally. |
- |
o |
o |
|||
monp |
Error |
5 |
Attempted to stop the cluster daemon, but failed. |
An attempt was made to stop the cluster, but failed. |
Check the following possible causes: cluster not yet activated, memory shortage, or OS resource insufficiency. |
o |
o |
|||
monp |
Info |
6 |
The system will be stopped since the monitor target process %1 terminated abnormally. |
The system will be stopped since monitored process %1 has terminated abnormally. |
- |
o |
o |
|||
monp |
Error |
7 |
Attempted to stop the system, but failed. (status=%#x) |
An attempt was made to stop the system, but failed. |
Check the following possible causes: cluster not yet activated, memory shortage, or OS resource insufficiency. |
o |
o |
|||
monp |
Info |
8 |
System will be rebooted since monitor target process %1 terminated abnormally. |
The system will be restarted since monitored process %1 has terminated abnormally. |
- |
o |
o |
|||
monp |
Error |
9 |
Attempted to reboot the system, but failed. (status=%#x) |
An attempt was made to restart the system, but failed. |
Check the following possible causes: cluster not yet activated, memory shortage, or OS resource insufficiency. |
o |
o |
|||
md / hd |
Error |
1 |
Failed to activate mirror disk. %1(Device:%2) |
Activating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Failed to open I/O port. |
The port could not be opened. Check the cluster configuration data. |
o |
o |
|||||||
The local server doesn't have the latest data. |
The local server does not have the latest data. Mirror recovery is needed. |
o |
o |
|||||||
Communication to the remote server failed. |
Communication with a remote server failed. Check the connection status of the mirror disk connection. |
o |
o |
|||||||
The remote server is active. |
The remote server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
The local server is already active. |
The local server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Mount operation failed. |
The mount operation failed. Check whether the mount point exists. Alternatively, check whether the mount option of the cluster configuration data is correct. |
o |
o |
|||||||
NMP size of the local server is greater than that of the remote server. |
The NMP size of the local server is greater than that of the remote server. Execute forced mirror recovery using the remote server as the mirror recovery source server. |
o |
o |
|||||||
Failed to set writable mode for data partition |
Restart the server which tried to activate the resource. Note that failover may occur when the server is restarted. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
md / hd |
Info |
2 |
fsck to %1 has started. |
fsck of %1 has started. |
- |
o |
o |
|||
md / hd |
Info |
3 |
fsck to %1 was successful. |
fsck of %1 has been successful. |
- |
o |
o |
|||
md / hd |
Error |
4 |
Failed to deactivate mirror disk. %1(Device:%2) |
Deactivating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The mirror disk has already been deactivated. |
The mirror disk has already been deactivated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Unmount operation failed. |
The unmount operation failed. Check whether the file system of the mirror disk resource is busy. |
o |
o |
|||||||
md / hd |
Info |
16 |
Initial mirror recovery of %1 has started. |
Preparation for initial mirror construction of %1 has started. |
- |
o |
o |
|||
md / hd |
Info |
18 |
Initial mirror recovery of %1 was successful. |
Preparation for initial mirror construction of %1 has been successful. |
- |
o |
o |
|||
md / hd |
Warning |
24 |
One of the servers is active, but the NMP size of mirror disks are not the same. (Device:%1) |
One of the servers is active. The NMP sizes do not match, however. |
Execute forced mirror recovery using the active server as the mirror recovery source server. |
o |
o |
|||
md / hd |
Error |
37 |
%1 of %2 failed(ret=%3). |
Command %1 of device %2 failed with return value %3. |
See the manual for command %1. |
o |
o |
|||
md / hd |
Warning |
38 |
Executing %1 of %2 with %3 option is necessary. Execute the command manually. |
Executing command %1 of device %2 with option %3 specified is necessary. Execute the command manually. |
Execute command %1 manually with option %3 specified. |
o |
o |
|||
md / hd |
Info |
39 |
%1 of %2 with %3 option has started. |
Command %1 of device %2 with option %3 specified has started. |
- |
o |
o |
|||
md / hd |
Info |
44 |
Mirror recovery of %1 was canceled. |
Mirror recovery of %1 has been canceled. |
- |
o |
o |
|||
md / hd |
Info |
45 |
Failed to cancel mirror recovery of %1. |
Mirror recovery of %1 could not be canceled. |
Stop the mirror recovery again. |
o |
o |
|||
md / hd |
Error |
46 |
umount timeout. Make sure that the length of Unmount Timeout is appropriate. (Device:%1) |
Unmount of mirror %1 has timed out. |
Check whether the unmount timeout setting is sufficiently long. (Refer to "Notes when terminating the Mirror disk resource or the Hybrid disk resource" and "Cache swell by a massive I/O" in "Notes and Restrictions" in the "Getting Started Guide".) |
o |
o |
|||
md / hd |
Error |
47 |
fsck timeout. Make sure that the length of Fsck Timeout is appropriate. (Device:%1) |
fsck that was run prior to mount of mirror %1 has timed out. |
Check whether the fsck timeout setting is sufficiently long. (Refer to "fsck execution" in "Notes and Restrictions" in the "Getting Started Guide".) |
o |
o |
|||
mdadmn |
Error |
2 |
Failed to activate mirror disk. %1(Device:%2) |
Activating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Failed to open I/O port. |
The port could not be opened. Check the cluster configuration data. |
o |
o |
|||||||
The local server doesn't have the latest data. |
The local server does not have the latest data. Mirror recovery is needed. |
o |
o |
|||||||
Communication to the remote server failed. |
Communication with a remote server failed. Check the connection status of the mirror disk connection. |
o |
o |
|||||||
The remote server is active. |
The remote server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
The local server is already active. |
The local server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Mount operation failed. |
The mount operation failed. Check whether the mount point exists. Alternatively, check whether the mount option of the cluster configuration data is correct. |
o |
o |
|||||||
NMP size of the local server is greater than that of the remote server. |
The NMP size of the local server is greater than that of the remote server. Execute forced mirror recovery using the remote server as the mirror recovery source server. |
o |
o |
|||||||
One of other inter-connection works well except mirror disk connections. |
Check that the LAN for mirror connection is normal. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdadmn |
Info |
2 |
fsck to %1 has started. |
fsck of %1 has started. |
- |
o |
o |
|||
mdadmn |
Info |
3 |
fsck to %1 was successful. |
fsck of %1 has been successful. |
- |
o |
o |
|||
mdadmn |
Error |
4 |
Failed to deactivate mirror disk. %1(Device:%2) |
Deactivating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The mirror disk has already been deactivated. |
The mirror disk has already been deactivated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Unmount operation failed. |
The unmount operation failed. Check whether the file system of the mirror disk resource is busy. |
o |
o |
|||||||
mdadmn |
Error |
5 |
Failed to recover the mirror. %1(Device:%2) |
Mirror recovery of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute. |
o |
o |
|||||||
The destination server is active. |
The mirror disk resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Cannot determine the mirror recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
NMP size of recovery destination is smaller. |
Change the mirror recovery direction. If the mirror recovery direction cannot be changed, exchange the mirror recovery destination mirror disk and allocate a data partition of sufficient size. Alternatively, allocate a data partition of sufficient size using the fdisk command or the like. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdadmn |
Info |
6 |
Mirror recovery of %1 was completed successfully. |
Mirror recovery of %1 has been successful. |
- |
o |
o |
|||
mdadmn |
Info |
7 |
Mirror recovery mode is %1.(Device:%2) |
The mirror recovery mode is %1. When %1 is "NORMAL", full-scale mirror recovery (Full Copy) is performed. When %1 is "FAST", difference mirror recovery is performed. |
- |
o |
o |
|||
mdadmn |
Info |
8 |
The number of Replicator Option licenses is %1. (%2) |
The number of Replicator Option licenses is %1. |
- |
o |
o |
|||
mdadmn |
Info |
9 |
The trial license is effective until %1. (%2) |
The trial license is effective until %1. |
- |
o |
o |
|||
mdadmn |
Error |
10 |
The registered license is unknown. (%1) |
The registered license is unknown. |
Register a valid license. |
o |
o |
|||
mdadmn |
Error |
11 |
The registered license is invalid. (%1) |
The registered license is invalid. |
Register a valid license. |
o |
o |
|||
mdadmn |
Error |
12 |
The license is not registered. (%1) |
The license is not registered. |
Purchase the license and then register it. |
o |
o |
|||
mdadmn |
Warning |
13 |
The number of licenses %1 is insufficient. (%2) |
The number of licenses is insufficient. |
Purchase the required number of licenses and then register them. |
o |
o |
|||
mdadmn |
Error |
14 |
The trial license expired in %1. (%2) |
The validity term of the trial license has expired. |
Register a valid license. |
o |
o |
|||
mdadmn |
Error |
15 |
The trial license is effective from %1. (%2) |
The validity term of the trial license is not reached. |
Register a valid license. |
o |
o |
|||
mdadmn |
Info |
16 |
Initial mirror recovery of %1 has started. |
Initial mirror construction of %1 has started. |
- |
o |
o |
|||
mdadmn |
Info |
17 |
Mirror recovery of %s has started.(%d bytes) |
Mirror recovery of %1 has started. |
- |
o |
o |
|||
mdadmn |
Info |
18 |
Initial mirror recovery of %1 was successful. |
Initial mirror construction of %1 has been successful. |
- |
o |
o |
|||
mdadmn |
Error |
19 |
Failed to perform initial mirror recovery. %1(Device:%2) |
Initial mirror construction of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute. |
o |
o |
|||||||
The destination server is active. |
The resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Cannot determine the mirror recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
mdadmn |
Info |
20 |
Initial mirror recovery was not executed following the configuration. (Device:%1) |
Initial mirror construction was not performed according to the setting. |
- |
o |
o |
|||
mdadmn |
Info |
21 |
Mirror partition mkfs was executed. (Device:%1) |
mkfs of the mirror partition has been executed. |
- |
o |
o |
|||
mdadmn |
Info |
22 |
Mirror partition mkfs was not executed following the configuration. (Device:%1) |
mkfs of the mirror partition was not executed according to the setting. |
- |
o |
o |
|||
mdadmn |
Info |
23 |
Forced mirror recovery was canceled. Execute the command "clpmdctrl --force" to resume the mirror recovery. (Device:%1) |
Forced mirror recovery has been canceled. To restart the mirror recovery, execute clpmdctrl --force. |
To restart the mirror recovery, execute clpmdctrl --force. |
o |
o |
|||
mdadmn |
Warning |
24 |
One of the servers is active, but NMP size of mirror disks are not the same. (Device:%1) |
One of the servers is active. The NMP sizes do not match, however. |
Execute forced mirror recovery using the active server as the mirror recovery source server. |
o |
o |
|||
mdadmn |
Info |
25 |
The NMP sizes of both servers' disks has been successfully synchronized. (Device:%1) |
The NMP sizes of both servers have been successfully synchronized. |
- |
o |
o |
|||
mdadmn |
Error |
28 |
Mirror recovery data has been successfully synchronized. NMP size synchronization has failed. (Device:%1) |
Mirror recovery data has been successfully synchronized. However, the NMP sizes could not be synchronized. |
Reexecute the forced mirror recovery. |
o |
o |
|||
mdadmn |
Error |
30 |
The license information was removed after the cluster was started. |
The license was valid when the cluster was started. However, the license was deleted. |
Register a valid license. |
o |
o |
|||
mdadmn |
Error |
31 |
Failed to isolate the mirror. %1(Device:%2) |
%2 could not be isolated. The following message is output to %1: Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||
mdadmn |
Error |
32 |
Forced activation of the mirror failed. %1 (Device:%2) |
Forced activation of %2 failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Failed to open I/O port. |
The port could not be opened. Check the cluster configuration data. |
o |
o |
|||||||
Mount operation failed. |
The mount operation failed. Check whether the mount point exists. Alternatively, check whether the mount option of the cluster configuration data is correct. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdadmn |
Error |
33 |
Forced recovery of the mirror failed. %1(Device:%2) |
Forced recovery of %2 failed. The following message may be output to %1: Register a valid license. |
Register a valid license. |
o |
o |
|||
mdadmn |
Info |
34 |
Isolating the mirror %1 completed successfully. |
Mirror resource %1 has been successfully isolated. |
- |
o |
o |
|||
mdadmn |
Info |
35 |
Mirror force active of %1 was completed successfully. |
Forced activation of %1 has been successful. |
- |
o |
o |
|||
mdadmn |
Info |
36 |
Forced recovery of the mirror %1 completed successfully. |
Forced recovery of %1 has been successful. |
- |
o |
o |
|||
mdadmn |
Error |
37 |
%1 of %2 failed(ret=%3). |
Command %1 of device %2 failed with return value %3. |
See the manual for command %1. |
o |
o |
|||
mdadmn |
Warning |
38 |
Executing %1 of %2 with %3 option is necessary. Execute the command manually. |
Executing command %1 of device %2 with option %3 specified is necessary. Execute the command manually. |
Execute command %1 manually with option %3 specified. |
o |
o |
|||
mdadmn |
Info |
39 |
%1 of %2 with %3 option has started. |
Command %1 of device %2 with option %3 specified has started. |
- |
o |
o |
|||
mdadmn |
Info |
40 |
Failed to write to cluster partition of hybrid disk(%1). |
Writing to cluster partition of %1 has failed. |
Restart the server. |
o |
o |
|||
mdadmn |
Info |
41 |
Timeout in writing to cluster partition of hybrid disk(%1). |
Writing to the cluster partition of %1 has timed out. |
The disk load may be high. Increase the value of Cluster Properties - Mirror Agent tab - Cluster Partition I/O Timeout. Alternatively, increase the timeout value of the monitor resource (hdw, hdnw) along with the increase in the former value. |
o |
o |
|||
mdadmn |
Info |
42 |
Failed to read from cluster partition of hybrid disk(%1). |
Reading of the cluster partition of %1 has failed. |
Restart the server. |
o |
o |
|||
mdadmn |
Info |
43 |
Timeout in reading from cluster partition of hybrid disk(%1). |
Reading of the cluster partition of %1 has timed out. |
The disk load may be high. Increase the value of Cluster Properties - Mirror Agent tab - Cluster Partition I/O Timeout. Alternatively, increase the timeout value of the monitor resource (hdw, hdnw) along with the increase in the former value. |
o |
o |
|||
mdadmn |
Info |
44 |
Mirror recovery of %1 was canceled. |
Mirror recovery of %1 has been canceled. |
- |
o |
o |
|||
mdadmn |
Info |
45 |
Failed to cancel mirror recovery of %1. |
Mirror recovery of %1 could not be canceled. |
Stop the mirror recovery again. |
o |
o |
|||
mdadmn |
Error |
46 |
unmount timeout. Make sure that the length of Unmount Timeout is appropriate. (Device:%1) |
Unmount of mirror %1 has timed out. |
Check whether the unmount timeout setting is sufficiently long. (Refer to "Notes when terminating the Mirror disk resource or the Hybrid disk resource" and "Cache swell by a massive I/O" in "Notes and Restrictions" in the "Getting Started Guide".) |
o |
o |
|||
mdadmn |
Error |
47 |
fsck timeout. Make sure that the length of Fsck Timeout is appropriate. (Device:%1) |
fsck that was run prior to mount of mirror %1 has timed out. |
Check whether the fsck timeout setting is sufficiently long. (Refer to "fsck execution" in "Notes and Restrictions" in the "Getting Started Guide".) |
o |
o |
|||
mdadmn |
Error |
54 |
Update of encryption key of %1 is required. |
The update of encryption key of %1 is required. |
Update the encryption key. |
o |
o |
|||
mdagent |
Info |
1 |
The Mirror Agent has started successfully. |
The mirror agent has been started normally. |
- |
o |
o |
|||
mdagent |
Error |
2 |
Failed to start Mirror Agent. %1 |
The mirror agent could not be started. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Agent is running. |
The agent has already been started. |
o |
o |
|||||||
Command clpmdinit is running. |
The clpmdini command has already been started. Check the end of the command and then restart it. |
o |
o |
|||||||
IP address in the config file is invalid. |
Check the cluster configuration data. |
o |
o |
|||||||
Server name in the config file is invalid. |
Check the cluster configuration data. |
o |
o |
|||||||
There is an error in config file. |
Check the cluster configuration data. |
o |
o |
|||||||
Failed to initialize socket server. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||||||
Disk error had occurred before reboot. Agent will stop starting.. |
Disk error occurred. Check the mirror disk and if necessary, see "How to replace a mirror disk with a new one" in "The system maintenance information" in the "Maintenance Guide", and replace it. |
o |
o |
|||||||
mdagent |
Info |
3 |
The Mirror Agent has stopped successfully. |
The mirror agent has been stopped normally. |
- |
o |
o |
|||
mdagent |
Error |
4 |
Failed to stop the Mirror Agent. |
The mirror agent has failed to stop. |
Check the following possible causes: cluster not yet activated, memory shortage, or OS resource insufficiency. |
o |
o |
|||
It is probable that an attempt to stop the mirror agent or server was made while the mirror disk resource or hybrid disk resource was activated. |
o |
o |
||||||||
Use the Cluster WebUI or an EXPRESSCLUSTER command to stop the mirror agent or server. |
o |
o |
||||||||
It is probable that an attempt to stop the mirror agent or server was made while the mirror disk resource or hybrid disk resource was still mounted. |
o |
o |
||||||||
If an unmount timeout occurred, set a larger value for unmount timeout. |
o |
o |
||||||||
If the user mounted the mirror partition at multiple mount points, unmount the additional mount point before deactivating the mirror. |
o |
o |
||||||||
It is also probable that mirror recovery was in progress. |
o |
o |
||||||||
If mirror recovery is in progress, stop the mirror agent or server after mirror recovery is completed or after stopping mirror recovery. |
o |
o |
||||||||
mdagent |
Warning |
5 |
Failed to load the resource(%1). Check if the Cluster Partition or Data Partition is OK. |
Resource %1 could not be loaded. |
Check whether the paths of the cluster and data partitions of resource %1 are correct or whether those paths may be destroyed. |
o |
o |
|||
mdctrl / hdctrl |
Error |
1 |
Failed to activate mirror disk.%1
(Device:%2)
|
Activating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Failed to open I/O port. |
The port could not be opened. Check the cluster configuration data. |
o |
o |
|||||||
The local server doesn't have the latest data. |
The local server does not have the latest data. Mirror recovery is needed. |
o |
o |
|||||||
Communication to the remote server failed. |
Communication with a remote server failed. Check the connection status of the mirror disk connection. |
o |
o |
|||||||
The remote server is active. |
The remote server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
The local server is already active. |
The local server has already been activated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Mount operation failed. |
The mount operation failed. Check whether the mount point exists. Alternatively, check whether the mount option of the cluster configuration data is correct. |
o |
o |
|||||||
NMP size of the local server is greater than that of the remote server. |
The NMP size of the local server is greater than that of the remote server. Execute forced mirror recovery using the remote server as the mirror recovery source server. |
o |
o |
|||||||
Failed to set writable mode for data partition |
Restart the server which tried to activate the resource. Note that failover may occur when the server is restarted. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdctrl / hdctrl |
Info |
2 |
fsck of %1 has started. |
fsck of %1 has started. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
3 |
fsck of %1 was successful. |
fsck of %1 has been successful. |
- |
o |
o |
|||
mdctrl / hdctrl |
Error |
4 |
Failed to deactivate mirror disk.%1
(Device:%2)
|
Deactivating %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The mirror disk has already been deactivated. |
The mirror disk has already been deactivated. Check the status of the mirror disk resource. |
o |
o |
|||||||
Unmount operation failed. |
The unmount operation failed. Check whether the file system of the mirror disk resource is busy. |
o |
o |
|||||||
mdctrl / hdctrl |
Error |
5 |
Failed to recover mirror.%1
(Device:%2)
|
Mirror recovery of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute. |
o |
o |
|||||||
The destination server is active. |
The mirror disk resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Can not judge the recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
NMP size of recovery destination is smaller. |
Execute the forced mirror recovery using the remote server as the mirror recovery source server. Alternatively, replace the mirror recovery destination disk with a disk of sufficient size or allocate a data partition of sufficient size with the fdisk command. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdctrl / hdctrl |
Info |
7 |
Mirror recovery mode is %1.(Device:%2) |
The mirror recovery mode is %1. When %1 is "NORMAL", full-scale mirror recovery (Full Copy) is performed. When %1 is "FAST", difference mirror recovery is performed. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
16 |
Initial mirror recovery of %1 has started. |
Initial mirror construction of %1 has started. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
17 |
Mirror recovery of %1 has started. |
Mirror recovery of %1 has started. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
18 |
Initial mirror recovery of %1 was successful. |
Initial mirror construction of %1 has been successful. |
- |
o |
o |
|||
mdctrl / hdctrl |
Error |
19 |
Failed to perform initial mirror recovery. %1(Device:%2) |
Initial mirror construction of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute. |
o |
o |
|||||||
The destination server is active. |
The resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Cannot judge the recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
mdctrl / hdctrl |
Info |
20 |
Initial mirror recovery was not executed following the configuration. (Device:%1) |
Initial mirror construction was not performed according to the setting. |
- |
o |
o |
|||
mdctrl / hdctrl |
Error |
31 |
Failed to isolate the mirror. %1(Device:%2) |
%2 failed to be isolated. The following message may be output to %1: Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||
mdctrl / hdctrl |
Error |
32 |
Forced activation of the mirror failed. %1 (Device:%2) |
Forced activation of %2 failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
Failed to open I/O port. |
The port could not be opened. Check the cluster configuration data. |
o |
o |
|||||||
Mount operation failed. |
The mount operation failed. Check whether the mount point exists. Alternatively, check whether the mount option of the cluster configuration data is correct. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdctrl / hdctrl |
Error |
33 |
Forced recovery of the mirror failed. %1(Device:%2) |
Forced recovery of %2 failed. The following messages may be output to %1: |
o |
o |
||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdctrl / hdctrl |
Info |
34 |
Isolating the mirror %1 completed successfully. |
Mirror resource %1 has been successfully isolated. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
35 |
Mirror force active of %1 was completed successfully. |
Forced activation of %1 has been successful. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
36 |
Forced recovery of the mirror %1 completed successfully. |
Forced recovery of %1 has been successful. |
- |
o |
o |
|||
mdctrl / hdctrl |
Error |
37 |
%1 of %2 failed(ret=%3). |
Command %1 of device %2 failed with return value %3. |
See the manual for command %1. |
o |
o |
|||
mdctrl / hdctrl |
Warning |
38 |
Executing %1 of %2 with %3 option is necessary. Execute the command manually. |
Executing command %1 of device %2 with option %3 specified is necessary. Execute the command manually. |
Execute command %1 manually with option %3 specified. |
o |
o |
|||
mdctrl / hdctrl |
Info |
39 |
%1 of %2 with %3 option has started. |
Command %1 of device %2 with option %3 specified has started. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
44 |
Mirror recovery of %1 was canceled. |
Mirror recovery of %1 has been canceled. |
- |
o |
o |
|||
mdctrl / hdctrl |
Info |
45 |
Failed to cancel mirror recovery of %1. |
Mirror recovery of %1 could not be canceled. |
Stop the mirror recovery again. |
o |
o |
|||
mdctrl / hdctrl |
Error |
46 |
umount timeout. Make sure that the length of Unmount Timeout is appropriate. (Device:%1) |
Unmount of mirror %1 has timed out. |
Check whether the unmount timeout setting is sufficiently long. (Refer to "Notes when terminating the Mirror disk resource or the Hybrid disk resource" and "Cache swell by a massive I/O" in "Notes and Restrictions" in the "Getting Started Guide".) |
o |
o |
|||
mdctrl / hdctrl |
Error |
47 |
fsck timeout. Make sure that the length of Fsck Timeout is appropriate. (Device:%1) |
fsck that was run prior to mount of mirror %1 has timed out. |
Check whether the fsck timeout setting is sufficiently long. (Refer to "fsck execution" in "Notes and Restrictions" in the "Getting Started Guide") |
o |
o |
|||
mdctrl / hdctrl |
Info |
50 |
Extension of mirror disk %1 was successful. |
The data partition extension of mirror disk resource %1 succeeded. |
o |
o |
||||
mdctrl / hdctrl |
Error |
51 |
Failed to extend mirror disk %1. |
The data partition extension of mirror disk resource %1 failed. |
Check if the data partition is configured with LVM.
Check if the amount of unused PE of the volume group is sufficient.
|
o |
o |
|||
mdctrl / hdctrl |
Info |
52 |
Update of encryption key of %1 was successful. |
The encryption key of %1 was successfully updated. |
- |
o |
o |
|||
mdctrl / hdctrl |
Error |
53 |
Failed to update encryption key of %1. |
The update of encryption key of %1 failed. |
Check if the key file exists in the configured key file full path on each server. |
o |
o |
|||
mdctrl / hdctrl |
Error |
54 |
Update of encryption key of %1 is required. |
The update of encryption key of %1 is required. |
Update the encryption key. |
o |
o |
|||
mdinit / hdinit |
Info |
21 |
Mirror partition mkfs was executed. (Device:%1) |
mkfs of the mirror partition has been executed. |
- |
o |
o |
|||
mdinit / hdinit |
Info |
22 |
Mirror partition mkfs was not executed following the configuration. (Device:%1) |
mkfs of the mirror partition was not executed according to the setting. |
- |
o |
o |
|||
mdw / hdw |
Error |
5 |
Failed to recover the mirror.%1 (Device:%2) |
Mirror recovery of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
An attempt was made to start auto mirror recovery, but mirror recovery was already started. |
o |
o |
|||||||
The destination server is active. |
The mirror disk resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Cannot determine the mirror recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
NMP size of recovery destination is smaller. |
Execute the forced mirror recovery using the remote server as the mirror recovery source server. Alternatively, replace the mirror recovery destination disk with a disk of sufficient size or allocate a data partition of sufficient size with the fdisk command. |
o |
o |
|||||||
Replicator license is invalid or expired. |
Register a valid license. |
o |
o |
|||||||
mdw / hdw |
Info |
7 |
Mirror recovery mode is %1.(Device:%2) |
The mirror recovery mode is %1. When %1 is "NORMAL", full-scale mirror recovery (Full Copy) is performed. When %1 is "FAST", difference mirror recovery is performed. |
- |
o |
o |
|||
mdw / hdw |
Info |
16 |
Initial mirror recovery of %1 has started. |
Initial mirror construction of %1 has started. |
- |
o |
o |
|||
mdw / hdw |
Info |
17 |
Mirror recovery of %1 has started. |
Mirror recovery of %1 has started. |
- |
o |
o |
|||
mdw / hdw |
Info |
18 |
Initial mirror recovery of %1 was successful. |
Initial mirror construction of %1 has been successful. |
- |
o |
o |
|||
mdw / hdw |
Error |
19 |
Failed to perform initial mirror recovery.%1 (Device:%2) |
Initial mirror construction of %2 has failed. The following messages may be output to %1: |
Take appropriate action according to the message displayed in %1. |
o |
o |
|||
The recovery is in progress. |
Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute. |
o |
o |
|||||||
The destination server is active. |
The resource has already been activated on the copy destination server. Check the status of the mirror disk resource. |
o |
o |
|||||||
Cannot determine the mirror recovery direction. |
The mirror recovery direction cannot be determined. Perform forced mirror recovery. |
o |
o |
|||||||
The source server is abnormal. |
The copy source server is abnormal. Check the status of the mirror agent. |
o |
o |
|||||||
mdw / hdw |
Info |
20 |
Initial mirror recovery was not executed following the configuration. (Device:%1) |
Initial mirror construction was not performed according to the setting. |
- |
o |
o |
|||
mdw / hdw |
Error |
54 |
Update of encryption key of %1 is required. |
The update of encryption key of %1 is required. |
Update the encryption key. |
o |
o |
|||
fip |
Error |
10 |
IP address %1 already exists on the network. |
IP address %1 exists in the network. |
Check whether the IP address is already in use in the network. |
o |
o |
|||
fip |
Info |
11 |
IP address %1 will be forcefully activated. |
IP address %1 is forcibly activated. |
- |
o |
o |
|||
vip |
Error |
10 |
IP address %1 already exists on the network. |
IP address %1 exists in the network. |
Check whether the IP address is already in use in the network. |
o |
o |
|||
vip |
Info |
11 |
IP address %1 will be forcefully activated. |
IP address %1 is forcibly activated. |
- |
o |
o |
|||
disk |
Info |
10 |
%1 of %2 has started. |
Command %1 of device %2 has started. |
- |
o |
o |
|||
disk |
Info |
11 |
%1 of %2 was successful. |
Command %1 of device %2 has been successful. |
- |
o |
o |
|||
disk |
Error |
12 |
%1 of %2 failed (ret=%3). |
Command %1 of device %2 failed with return value %3. |
See the manual for command %1. |
o |
o |
|||
disk |
Warning |
13 |
Executing %1 of %2 with %3 option is necessary. Execute the command manually. |
Executing command %1 of device %2 with option %3 specified is necessary. Execute the command manually. |
Execute command %1 manually with option %3 specified. |
o |
o |
|||
disk |
Info |
14 |
%1 of %2 with %3 option has started. |
Command %1 of device %2 with option %3 specified has started. |
- |
o |
o |
|||
disk |
Error |
15 |
Timeout occurred during %1 of %2. |
Execution of Command %1 of device %2 has timed out. |
Check the cause of the execution timeout of Command %1 and take appropriate action. |
o |
o |
|||
disk |
Warning |
16 |
Executing xfs_repair of %1 is necessary. Execute the command manually. |
Executing the xfs_repair command is necessary. Execute the command manually. |
Execute the xfs_repair command. |
o |
o |
|||
disk |
Warning |
17 |
Setting of Disktype=%1 and Filesystem=%2 can't be combined. |
Disk type %1 and file system %2 cannot be used in combination. |
Review the setting. |
o |
o |
|||
cl |
Info |
1 |
There was a request to start %1 from the %2. |
A request to start %1 was issued from %2. |
- |
o |
o |
|||
cl |
Info |
2 |
There was a request to stop %1 from the %2. |
A request to stop %1 was issued from %2. |
- |
o |
o |
|||
cl |
Info |
3 |
There was a request to suspend %1 from the %2. |
A request to suspend %1 was issued from %2. |
- |
o |
o |
|||
cl |
Info |
4 |
There was a request to resume %s from the %s. |
A request to resume %1 was issued from %2. |
- |
o |
o |
|||
cl |
Error |
11 |
A request to start %1 failed(%2). |
A request to start %1 has failed. |
Check the status of the cluster. |
o |
o |
|||
cl |
Error |
12 |
A request to stop %1 failed(%2). |
A request to stop %1 has failed. |
Check the status of the cluster. |
o |
o |
|||
cl |
Error |
13 |
A request to suspend %1 failed(%2). |
A request to suspend %1 has failed. |
Check the status of the cluster. |
o |
o |
|||
cl |
Error |
14 |
A request to resume %1 failed(%2). |
A request to resume %1 has failed. |
Check the status of the cluster. |
o |
o |
|||
cl |
Error |
15 |
A request to %1 cluster failed on some servers(%2). |
A %1 request of the cluster failed on some servers. |
Check the status of the cluster. |
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 because 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 because 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 because the cluster is running. |
Check the status of the cluster. |
o |
o |
|||
Error |
1 |
The license is not registered. (%1) |
Purchase the license and then register it. |
- |
o |
o |
||||
Error |
2 |
The trial license has expired in %1. (%2) |
Register a valid license. |
- |
o |
o |
||||
Error |
3 |
The registered license is invalid. (%1) |
Register a valid license. |
- |
o |
o |
||||
Error |
4 |
The registered license is unknown. (%1) |
Register a valid license. |
- |
o |
o |
||||
Error |
5 |
mail failed(%s).(SMTP server: %s) |
Mail report failed. |
Check whether there is an error in the SMTP server and that there is no problem with communicating with the SMTP server. |
o |
o |
||||
Info |
6 |
mail successed.(SMTP server: %s) |
Mail report has been successful. |
- |
o |
o |
||||
down |
Info |
1 |
There was a request to shutdown %1 from the %2. |
There was a request to shut down %1 from %2. |
- |
o |
o |
|||
down |
Info |
2 |
There was a request to reboot %1 from the %2. |
There was a request to reboot %1 from %2. |
- |
o |
o |
|||
down |
Error |
11 |
A request to shutdown %1 failed(%2). |
A request to shut down %1 failed. |
Check the status of the server. |
o |
o |
|||
down |
Error |
12 |
A request to reboot %1 failed(%2). |
A request to reboot %1 failed. |
Check the status of the server. |
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 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 condition of the server on which the monitoring delay was detected, and lessen the load appropriately. If a monitoring timeout is likely to be detected, you should increase the monitoring timeout setting. |
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 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 condition of the server on which the monitoring delay was detected, and lessen the load appropriately. If a monitoring timeout is likely to be detected, you should increase the monitoring timeout setting. |
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 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 condition of the server on which the monitoring delay was detected, and lessen the load appropriately. If a monitoring timeout is likely to be detected, you should increase the monitoring timeout setting. |
o |
o |
|||
apisv |
Info |
1 |
There was a request to stop cluster from the %1(IP=%2). |
A request to stop the cluster was 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 cluster was 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 cluster was 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 cluster was 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 was 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 was 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 was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
13 |
There was a request to server panic from the %1(IP=%2). |
A server panic request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
14 |
There was a request to server reset from the %1(IP=%2). |
A server reset request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
15 |
There was a request to server sysrq from the %1(IP=%2). |
An SYSRQ panic request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
16 |
There was a request to KA RESET from the %1(IP=%2). |
A keepalive reset request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
17 |
There was a request to KA PANIC from the %1(IP=%2). |
A keepalive panic request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
18 |
There was a request to BMC reset from the %1(IP=%2). |
A BMC reset request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
19 |
There was a request to BMC PowerOff from the %1(IP=%2). |
A BMC power-off request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
20 |
There was a request to BMC PowerCycle from the %1(IP=%2). |
A BMC power cycle request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
21 |
There was a request to BMC NMI from the %1(IP=%2). |
A BMC NMI request was 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 was 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 was 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 was 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 was 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 was 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 was 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 was issued from %2. |
- |
o |
o |
|||
apisv |
Info |
37 |
There was a request to move all groups from the %1(IP=%2). |
A request to move the group was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
38 |
There was a request to failover group(%1) from the %2(IP=%3). |
A group %1 failover request was issued from %2. |
- |
o |
o |
|||
apisv |
Info |
39 |
There was a request to failover all groups from the %1(IP=%2). |
A group failover request was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
40 |
There was a request to migrate group(%1) from the %2(IP=%3). |
A group %1 migration request was issued from %2. |
- |
o |
o |
|||
apisv |
Info |
41 |
There was a request to migrate all groups from the %1(IP=%2). |
A request to make all groups migrate was 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 was 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 was 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 was 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 was 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 was 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 was 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 the monitor resource was 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 the monitor resource was issued from %1. |
- |
o |
o |
|||
apisv |
Info |
62 |
There was a request to enable Dummy Failure of monitor resource(%1) from the %2(IP=%3). |
A request to enable Dummy Failure of monitor resource %1 was issued from%2. |
- |
o |
o |
|||
apisv |
Info |
63 |
There was a request to disable Dummy Failure of monitor resource(%1) from the %2(IP=%3). |
A request to disable Dummy Failure of monitor resource%1 was issued from%2. |
- |
o |
o |
|||
apisv |
Info |
64 |
There was a request to disable Dummy Failure of all monitor resources from the %1(IP=%2). |
A request to disable Dummy Failure of all the monitor resources was issued from %1. |
- |
o |
o |
|||
apisv |
Error |
101 |
A request to stop cluster was failed(0x%08x). |
The cluster could not be stopped. |
Check the status of the cluster. |
o |
o |
|||
apisv |
Error |
102 |
A request to shutdown cluster was failed(0x%08x). |
The cluster could not be shut down. |
Check the status of the cluster. |
o |
o |
|||
apisv |
Error |
103 |
A request to reboot cluster was failed(0x%08x). |
The cluster could not be rebooted. |
Check the status of the cluster. |
o |
o |
|||
apisv |
Error |
104 |
A request to suspend cluster was failed(0x%08x). |
The cluster could not be suspended. |
Check the status of the cluster. |
o |
o |
|||
apisv |
Error |
110 |
A request to stop server was failed(0x%08x). |
The server could not be stopped. |
Check the status of the server. |
o |
o |
|||
apisv |
Error |
111 |
A request to shutdown server was failed(0x%08x). |
The server could not be shut down. |
Check the status of the server. |
o |
o |
|||
apisv |
Error |
112 |
A request to reboot server was failed(0x%08x). |
The server could not be rebooted. |
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). |
Starting group (%1) has failed. |
Take appropriate action according to the group start failure message issued by rc. |
o |
o |
|||
apisv |
Error |
131 |
A request to start all groups was failed(0x%08x). |
Starting all groups has failed. |
Same as above. |
o |
o |
|||
apisv |
Error |
132 |
A request to stop group(%1) was failed(0x%08x). |
Stopping group (%1) has failed. |
Take appropriate action according to the group stop failure message issued by rc. |
o |
o |
|||
apisv |
Error |
133 |
A request to stop all groups was failed(0x%08x). |
Stopping 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). |
Moving group (%1) has failed. |
Take appropriate action according to the group movement failure message issued by rc. |
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). |
Failover for group (%1) has failed. |
Take appropriate action according to the group failover failure message issued by rc. |
o |
o |
|||
apisv |
Error |
139 |
A request to failover all groups was failed(0x%08x). |
Failover for 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). |
Resource (%1) has failed to start. |
Take appropriate action according to the resource start failure message issued by rc. |
o |
o |
|||
apisv |
Error |
151 |
A request to start all resources was failed(0x%08x). |
Starting all resources has failed. |
Same as above. |
o |
o |
|||
apisv |
Error |
152 |
A request to stop resource(%1) was failed(0x%08x). |
Resource (%1) has failed to stop. |
Take appropriate action according to the resource stop failure message issued by rc. |
o |
o |
|||
apisv |
Error |
153 |
A request to stop all resources was failed(0x%08x). |
Stopping all resources has failed. |
Same as above. |
o |
o |
|||
apisv |
Error |
154 |
A request to restart resource(%1) was failed(0x%08x). |
Resource (%1) has failed to restart. |
Take appropriate action according to the resource restart failure message issued by rc. |
o |
o |
|||
apisv |
Error |
155 |
A request to restart all resources was failed(0x%08x). |
Restarting all resources has failed. |
Same as above. |
o |
o |
|||
apisv |
Error |
160 |
A request to suspend monitor resource was failed(0x%08x). |
The monitor resource could not be suspended. |
Check the status of the monitor resource. |
o |
o |
|||
apisv |
Error |
161 |
A request to resume monitor resource was failed(0x%08x). |
The monitor resource could not be resumed. |
Same as above. |
o |
o |
|||
apisv |
Error |
162 |
A request to enable Dummy Failure of monitor resource(%1) was failed(0x%08x). |
The monitor resource %1 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(%1) was failed(0x%08x). |
The monitor resource %1 failed to stop Dummy Failure. |
Same as above. |
o |
o |
|||
apisv |
Error |
164 |
A request to disable Dummy Failure of all monitor resources was failed(0x%08x). |
All the monitor resources failed to stop Dummy Failure. |
Same as above. |
o |
o |
|||
lamp |
Error |
1 |
The license is not registered. (%1) |
The license is not registered. |
Purchase the license and then register it. |
o |
o |
|||
lamp |
Error |
2 |
The trial license has expired in %1. (%2) |
The validity term of the trial license has expired. |
Register a valid license. |
o |
o |
|||
lamp |
Error |
3 |
The registered license is invalid. (%1) |
The registered license is invalid. |
Register a valid license. |
o |
o |
|||
lamp |
Error |
4 |
The registered license is unknown. (%1) |
The registered license is unknown. |
Register a valid license. |
o |
o |
|||
lamp |
Info |
5 |
Notice by the network warming light succeeded. |
Report by the network warning light has been successful. |
- |
o |
o |
|||
lamp |
Error |
6 |
Error in executing result of warning light command.(%d) |
An error occurred during execution of the network warning light report command. |
Take appropriate action according to the error code. |
o |
o |
|||
lamp |
Error |
7 |
Failed to execute warning light command.(%d) |
The network warning light report command could not be executed. |
Check the following possible causes: memory shortage or OS resource insufficiency. |
o |
o |
|||
cfmgr |
Info |
1 |
The cluster configuration data has been uploaded by %1. |
Cluster 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. |
SystemResource Agent 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. |
SystemResource Agent 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. |
SystemResource Agent 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 |
SystemResource
Agent 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 |
SystemResource Agent 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 |
SystemResource Agent 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] |
SystemResource Agent 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 |
SystemResource Agent 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 |
SystemResource Agent 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 |
Error |
304 |
A disk resource error was detected. (%1, type = inode used rate, level = NOTICE, %2) %1:Monitor resource name %2:mount point |
A notice level error was detected in monitoring the inode usage rates. |
Check the possible causes of the monitoring failure. |
o |
o |
|||
sra |
Error |
304 |
A disk resource error was detected. (%1, type = inode used rate, level = WARNING, %2) %1:Monitor resource name %2:mount point |
A warning level error was detected in monitoring the inode usage rates. |
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. |
Access WebManager by HTTP mode. |
o |
o |
|||
forcestop |
Info |
1 |
Forced stop of server %1 has been requested.(%2, %3) |
forced-stop requested (%1, %2, %3) |
- |
o |
o |
|||
forcestop |
Info |
2 |
Forced stop of server %1 has completed.(%2, %3) |
forced-stop completed (%1, %2, %3) |
- |
o |
o |
|||
forcestop |
Error |
3 |
The previous forced-stop request has not yet been completed on server %1. (%2, %3, pid=%4) |
Uncompleted forced-stop request (%1, %2, %3, pid=%4) |
Check the started processes. |
o |
o |
|||
forcestop |
Error |
4 |
A request to Forced stop of server %1 has been failed.(%2, %3) |
Failure of the forced-stop request (%1, %2, %3) |
Check whether the command can be used. |
o |
o |
|||
forcestop |
Error |
5 |
The previous forced-stop check request has not yet been completed on server %1. |
Uncompleted forced-stop check request (%1, %2, %3, pid=%4) |
Check the started processes. |
o |
o |
|||
forcestop |
Error |
6 |
Forced stop of server %1 failed.(%2, %3) |
forced-stop failed (%1, %2, %3) |
Check whether the command can be used. |
o |
o |
|||
httpnp |
Error |
1 |
In %1, communication with the target failed. |
Communication with the target failed. %1:Resource name |
Check if an error occurred in the network adapter or if the network connection is normal. |
o |
o |
|||
httpnp |
Error |
2 |
In %1, communication with the target timed out. |
Communication with the target timed out. %1:Resource name |
Check if an error occurred in the network adapter or if the network connection is normal. |
o |
o |
|||
httpnp |
Error |
3 |
In %1, the target returned a status code of %2. |
The status code from the target is invalid. %1:Resource name %2:Status code |
Check the target's status. |
o |
o |
|||
httpnp |
Error |
5 |
Initializing the TLS/SSL library failed. |
Initializing the TLS/SSL library failed. |
In [Cluster Properties] (the [Encryption] tab), check the settings of SSL and Crypto libraries. |
o |
o |
|||
witnesshb |
Error |
1 |
In %1, communication with the target failed. |
Communication with the target failed. %1:Resource name |
Check if an error occurred in the network adapter or if the network connection is normal. |
o |
o |
|||
witnesshb |
Error |
2 |
In %1, communication with the target timed out. |
Communication with the target timed out. %1:Resource name |
Check if an error occurred in the network adapter or if the network connection is normal. |
o |
o |
|||
witnesshb |
Error |
3 |
In %1, the target returned a status code of %2. |
The status code from the target is invalid. %1:Resource name %2:Status code |
Check the target's status. |
o |
o |
|||
witnesshb |
Error |
4 |
In %1, an invalid response was received from the target. |
An invalid response was received from the target. %1:Resource name |
Check the status of the target, which may not be a Witness server. |
o |
o |
|||
witnesshb |
Error |
5 |
Initializing the TLS/SSL library failed. |
Initializing the TLS/SSL library failed. |
In [Cluster Properties] (the [Encryption] tab), check the settings of SSL and Crypto libraries. |
o |
o |
|||
witnesshb |
Warning |
71 |
Heartbeats sent from HB resource %1 of server %2 are delayed. (timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats from HB resource %1 of server %2 are delayed. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server %2 and remove the load. If an HB timeout occurs, extend it. |
o |
o |
|||
witnesshb |
Warning |
72 |
Heartbeats sent from HB resource %1 are delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats sent from HB resource %1 are delayed. The transmission destination server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
|||||
witnesshb |
Warning |
73 |
Heartbeats received by HB resource %1 are delayed.(server=%2 timeout=%3*%4 actual-time=%5 delay warning rate=%6) |
Heartbeats received by HB resource %1 are delayed. The transmission source server is %2. The current timeout value is %3 (second) x %4 (tick count per second). The actual measurement value at delay generation is %5 (tick count) and exceeded the delay warning rate %6 (%). |
Check the load status of the server to which a delay warning was issued and remove the load. If an HB timeout occurs, extend it. |
11.3. Driver syslog messages¶
The syslog messages by EXPRESSCLUSTER driver in this version are output as follows:
[Event class] <type: Module type><event: Event ID> Message
Item |
Display content |
Description |
---|---|---|
Event class |
I |
Information/Notification |
W |
Warning/Caution |
|
E |
Error |
|
Module type |
liscal |
Mirror Driver |
clpkhb |
Kernel Mode LAN Heartbeat Driver |
|
clpka |
Keepalive Driver |
|
Event ID |
Digit |
|
Message |
Message |
(Examples of display message)
kernel: [I] <type: liscal><event: 101> Registered blkdev with major=218. |
kernel: [I] <type: liscal><event: 130> NMP1 new thread: liscal_hb_client_thread (PID=30777). |
kernel: [I] <type: liscal><event: 243> NMP1 network is USING 192.168.10.100 - 192.168.10.101 :29031(HB) |
kernel: [W] <type: liscal><event: 220> NMP1 failed to create HB client socket. (err=-111: Connection refused) |
kernel: [I] <type: clpkhb><event: 101> Kernel Heartbeat was initialized successfully. (major=10, minor=253) |
kernel: [E] <type: clpkhb><event: 123> Failed to bind HB socket. (err=-99: Can not assign requested address) |
The messages are displayed under the following log level when outputting syslog.
Module Type |
liscal |
clpkhb |
clpka |
---|---|---|---|
Information/ Notification[I] |
KERN_INFO |
KERN_INFO |
KERN_INFO |
Warning/ Caution[W] |
KERN_INFO |
KERN_INFO |
KERN_INFO |
Error [E] |
KERN_ERR |
KERN_INFO |
KERN_INFO |
See also the followings for the coping process to the messages:
"EXPRESSCLUSTER X 4.1 Getting Started Guide" "Notes and Restrictions"
"EXPRESSCLUSTER X 4.1 Maintenance Guide" "The system maintenance information"
"EXPRESSCLUSTER X 4.1 Reference Guide " "Troubleshooting"
11.3.1. Mirror Driver¶
Module Type |
Event type |
Event ID |
Message |
Description |
Solution |
---|---|---|---|---|---|
liscal |
Info |
100 |
NMP%1 received dataless bio. (%2) |
Internal information of NMP[%1]. Detailed information: [%2] |
- |
%1 |
Other internal information: [%1] |
||||
liscal |
Info |
101 |
Registered blkdev with major=%1. |
Successfully loaded the mirror driver. |
- |
liscal |
Error |
102 |
Failed to register blkdev with major=%1. |
Failed to load the mirror driver. |
- |
liscal |
Info |
103 |
Unregistered blkdev with major=%1. |
Successfully unloaded the mirror driver. |
- |
liscal |
Warning |
104 |
Failed to unregister blkdev with major=%1. |
Unloading the mirror driver failed. |
- |
liscal |
Info |
110 |
Adding disk NMP%1 with major=%2 minor=%3. |
The mirror partition NMP[%1] is going to be added. |
- |
liscal |
Info |
111 |
Deleting disk NMP%1 with major=%2 minor=%3. |
The mirror partition NMP[%1] is going to be deleted. |
- |
liscal |
Info |
112 |
Cleaning up NMP%1 queue. |
The queue of the mirror partition NMP[%1] is going to be Cleaned up. |
- |
liscal |
Error |
113 |
NMP%d failed to add disk. (major=%d, minor=%d, err=%d%s) |
Failed to add mirror partition NMP[%1]. |
Restart the local server. |
liscal |
Error |
120 |
insmod did not pass %1 to liscal with %2. |
Loading the mirror driver failed. Invalid parameter had been specified. |
Restart the local server. |
liscal |
Error |
121 |
Failed to create a proc file %1. |
Creation of proc file [%1] (liscalstat / liscalinner) failed. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Info |
122 |
%1 is busy. (proc->count=%2) |
The proc file [%1] (liscalstat / liscalinner) is being accessed. Waiting for the end of the access. |
Check if there is any process accessing to [%1] (/proc/liscalstat or /proc/liscalinner). The corresponding process is going to be killed. |
liscal |
Info |
123 |
Forced to remove %1 after waiting %2 seconds. |
The proc file[%1] (liscalstat / liscalinner) was deleted forcibly, because killing forcibly all the processes accessing it after waiting for [%2] seconds failed. |
- |
liscal |
Warning |
124 |
NMP%1 waited for all I/O requests to be sent completely, but timeout occurred. Writing differences to bitmap. |
Some asynchronous data could not be sent completely in time at deactivation. Their difference information is going to be written to the Cluster Partition. |
- |
liscal |
Warning |
125 |
NMP%1 %2 I/O requests (%3B) %4 not be sent to remote server %5. |
The number of I/O requests for which the completion of asynchronization data transmission was not checked is [%2] ([%3] bytes). |
- |
liscal |
Info |
130 |
New thread: %2 (PID=%3). NMP%1 new thread: %2 (PID=%3). |
The thread [%2] started. Process id of it is [%3]. |
- |
liscal |
Error |
131 |
Failed to fork thread: %2 (err=%3). |
Starting the thread [%2] failed. (Error code=[%3]) |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
NMP%1 failed to fork thread: %2 (err=%3). |
- |
||||
liscal |
Info |
132 |
killing thread............OK. (%2) NMP%1 killing thread.......OK (%2) |
Thread [%2] ended normally. |
- |
liscal |
Info |
133 |
%1 waiting %2 killed....... |
Thread [%1] is waiting for thread [%2] to end. |
- |
liscal |
Info |
134 |
NMP%1 received signal. (%2) |
Thread / Procedure [%2] received the termination request signal. |
- |
liscal |
Info |
135 |
NMP%1 exit.....OK. (%2) |
Procedure [%2] ended normally. |
- |
liscal |
Error |
136 |
NMP%1 killing thread, but mount port is still opened. |
The mounted mirror disk resource exists at unloading the mirror driver. |
Check the mirror disk resource status. |
liscal |
Error |
137 |
NMP%1 killing thread, but %2 I/O request still exist. |
The mirror partition device is busy. The thread of the mirror driver is going to stop, but the I/O request to the mirror partition has not been still completed. |
Check the mirror disk resources is not accessed. |
liscal |
Info |
140 |
NMP%1 liscal will shutdown, N/W port closed. |
An attempt will be made to perform shutdown with the mirror partition mounted. Mirror data transmission is stopped. Any data that is not transmitted is recorded as the mirror difference to perform mirror break. |
Use clpstdn or clpdown to shut down the server. Check whether shutdown and reboot were used erroneously. |
liscal |
Warning |
141 |
NMP%1 device does not exist. (%2) |
NMP[%1] does not exist. |
Check the cluster configuration information. Check if there is wrong setting with initial construction steps of the mirror disk or the hybrid disk. No problem in case of the following. |
liscal |
Info |
141 |
|
On the environment which udev runs, this message is output when the NMP[%1] is accessed before the mirror driver completes the initialization of NMP[%1]. |
For the workaround, see "Error message in the load of the mirror driver in the udev environment" of "Notes and Restrictions" in "Getting Started Guide". |
liscal |
Info |
141 |
|
In this case, this message and buffer I/O error of NMP[%1] are displayed, but there is no problem. |
Same as above. |
liscal |
Warning |
142 |
NMP%1 N/W is not initialized yet. (%2) |
The initialization of the driver has not completed yet. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Warning |
143 |
NMP%1 cache_table is not initialized. (%2) |
The initialization of the driver has not completed yet. |
Same as above. |
liscal |
Warning |
144 |
NMP%1 I/O port has been closed, mount(%2), io(%3). |
The mirror partition has not been mounted. But it was going to be accessed. |
Check the mirror disk resource status. |
Check if there is any applications trying to access the mirror partition device directly. |
|||||
If output is made at deactivation, it takes time to write memory cache into a disk during unmount processing. This may cause a timeout. While referencing "Cache swell by a massive I/O" below, increase the unmount timeout value sufficiently. |
|||||
If the user specified an additional mount point to be created in a different location for the mirror partition device or mirror mount point, check if that mount point is configured to be unmounted before deactivation. See "When multiple mounts are specified for a resource like a mirror disk resource" below. |
|||||
For others, the following may be applicable. |
|||||
liscal |
Info |
144 |
|
This message can be output in case that the mirror partition is accessed by fsck command before being mounted. |
|
liscal |
Info |
144 |
|
And also, this message can be output when the hotplug service searches devices. |
Same as above. |
liscal |
Info |
144 |
|
This message and buffer I/O error of NMP[%1] are displayed in this case, but there is no problem. |
Same as above. |
liscal |
Error |
145 |
Failed to allocate %2
NMP%1 failed to allocate %2 |
Allocation of memory failed. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Info |
146 |
Failed to allocate %2, retrying.
NMP%1 failed to allocate %2, retrying. |
Allocation of memory failed. Memory allocation is retried. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Warning |
147 |
Failed to allocate %2, other area used instead. |
Allocation of memory failed. The reserved area is used. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Info |
148 |
NMP%1 holder %2. (%3) |
The exclusive access count before or after (timing of [%3]) mount/unmount of NMP[%1] is [%2]. Normally, [%2] is 0before mount or after unmount; [%2] is 1 after mount or before unmount. If the count is other than 0 even after unmount, it is possible that something is holding NMP[%1] or continues to hold it such that unmount cannot be completed. |
If the count does not become 0 even after unmount and a file system error occurs, the unmount timeout setting may be insufficiently long. Refer to "Notes when terminating the Mirror disk resource or the Hybrid disk resource" and "Cache swell by a massive I/O" in "Notes and Restrictions" in the "Getting Started Guide". If the count is other than 0 before mount, the fsck timeout setting may be insufficient. Refer to "fsck execution" in "Notes and Restrictions" in the "Getting Started Guide". |
liscal |
Info |
150 |
NMP%1 mirror break, writing mirror_break_time to Cluster Partition. |
Mirror break occurred. Either there is a problem with mirror disk connection, or I/O to the disk failed in the remote server. |
Check the mirror disk connection status. Check if the mirror disk connection or OS is highly-loaded. |
liscal |
Info |
151 |
NMP%1 ACK1 timeout. |
Timeout occurred while receiving the response to the sent mirror synchronization data (ACK1). |
Same as above. |
liscal |
Info |
152 |
NMP%1 mirror break has occurred during recovery, recovery failed. |
Mirror break occurred while recovering the mirror. Mirror recovery will stop abnormally. |
Same as above. |
liscal |
Info |
154 |
NMP%1 N/W port opened. |
The mirror synchronization data connection port opened because the connection became possible. |
- |
liscal |
Info |
155 |
NMP%1 N/W port closed. |
The connection port closed because the connection became impossible. |
- |
liscal |
Info |
156 |
NMP%1 failed to %2, because N/W port has been closed. |
Sending and receiving of data[%2] failed because the connection port had been closed. |
Check the mirror disk connection status. Check if the mirror disk connection or OS is highly-loaded. |
liscal |
Info |
157 |
NMP%1 failed to recover, because N/W port of remote server has been closed. |
Mirror recovery failed because the connection port of the remote server had been closed. |
Same as above. |
liscal |
Warning |
158 |
NMP%1 received sync data, but mount port has been opened, sync failed. |
The synchronization data from the remote server was received. But the mirror partition has been mounted on the local server. Then the received data was discarded. |
Check if the mirror partition is deactive and is mounted. |
liscal |
Info |
159 |
NMP%1 received request to stop sending data from remote server. |
Synchronization data was sent to the remote server. However, the transmitted synchronization data was discarded because the remote server had mounted the mirror partition or transmission was disabled. |
Same as above. |
liscal |
Error |
160 |
NMP%1 disk I/O error%2 |
The I/O error to the disk occurred now or in the past. The system will reboot. |
The physical defect may have occurred with mirror disk in case of being output while in operation. See "The system maintenance information" in the "Maintenance Guide", exchange the mirror disks and run mirror recovery. Check the cluster partition settings in cluster configuration information in case of being output while constructing the cluster. |
liscal |
Error |
160 |
|
See "The system maintenance information" in the "Maintenance Guide" and clear the cluster partition in case that this message is output at startup even after exchanging the mirror disks. |
|
liscal |
Error |
160 |
|
See "The system maintenance information" in the Maintenance Guide and exchange the mirror disks in case of not having exchanged the mirror disks. |
|
liscal |
Error |
161 |
NMP%1 failed to %2 %3 %4 Cluster Partition. |
The I/O[%2] (read/write / read / write / clear / flush) to the area in the Cluster Partition failed. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource) when the lack of resource is possible. The physical defect may have occurred with mirror disk in case of being output while in operation. See "The system maintenance information" in the "Maintenance Guide", exchange the mirror disks and run mirror recovery. Check the cluster partition settings in cluster configuration information in case of being output while constructing the cluster. |
liscal |
Warning |
162 |
NMP%1 failed to clear the bitmap. (%2) |
In the processing [%4], the difference bitmap processing [%2] (set/clear) for the [%3] area failed. |
Shut down the cluster and restart it. |
liscal |
Info |
163 |
NMP%1 %2 is null. (%3) |
The initialization of the driver has not completed. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Warning |
164 |
NMP%1 sector %2 not found. (%3) |
The processing information to the corresponding sector[%2] was not found in the queue in the driver. |
- |
liscal |
Warning |
165 |
NMP%1 requested sector is out of NMP area. (%2) |
The I/O request to the area exceeding the size of the mirror partition was received at procedure[%2]. This request was discarded. |
- |
liscal |
Info |
166 |
NMP%1 %2 is null. (%3) |
An attempt was made to set a difference bitmap after it had already been set as having a difference. |
- |
liscal |
Info |
167 |
NMP%1 %2 is null. (%3) |
An attempt was made to send ACK2 after it had already been sent. |
- |
liscal |
Error |
168 |
NMP%1 failed to %2 bitmap. Invalid %3 |
Processing [%2] on the differential bitmap for the [%3] area failed. |
A problem may have occurred with the mirror driver. Check if the sizes of the single sectors of the mirror disks on the two servers differ. |
liscal |
Error |
169 |
NMP%1 ioctl code(%2) is not supported. |
Unsupported ioctl code [%2] detected. |
- |
liscal |
Warning |
170 |
ioctl() got %1 inode with NULL, exit. |
Invalid ioctl() call was detected. |
The OS may have become unstable. Restart the system. |
liscal |
Error |
171 |
NMP%1 requested I/O with wrong command(%2) from FS. |
Invalid I/O request was issued to the mirror partition from the file system or others. This request to the NMP device is incorrect. |
Same as above. |
liscal |
Warning |
172 |
request_id(%2) is too big. (%3)
NMP%1 request_id(%2) is too big. (%3) |
Invalid procedure number was detected at procedure[%3]. This request was discarded. |
- |
liscal |
Warning |
173 |
NMP%1 failed to send, but its ID was not found in request_queue. (%2) |
Sending of the mirror synchronization data failed. An attempt to delete the processing information failed, because the corresponding procedure number was not found in the queue in the driver. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Info |
174 |
NMP%1 request_id(%2) deleted. (%3) |
The processing information of procedure number[%2] was deleted normally from the queue in the driver due to the mirror synchronization data send failure. |
- |
liscal |
Error |
175 |
request_id(%2) ACK1 timeout, but its NMP%1 not found. (%3) |
ACK1 (response to the sent mirror data) of procedure number[%2] had not been received in time. But the corresponding procedure number[%2] was not found in the queue in the driver. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Info |
176 |
NMP%1 received ACK1, but its ID was not found in request_queue. |
ACK1 (response to the mirror synchronization data) was received. But the corresponding procedure number[%2] was not found in the queue in the driver. This message is output if ACK1 is received after it has not been received in time. |
When Event ID:151 occurs before this event, this event may mean a server received ACK1 of Event ID:151 by high-load on partner or network. In this case, change Ack timeout too long. (process 4) |
liscal |
Info |
177 |
NMP%1 received ACK2, but its ID was not found in wait_ack2_queue. |
ACK2 (response to mirror synchronization completion notification ACK1) was received. But the corresponding procedure number[%2] was not found in the queue in the driver. This message is output if ACK2 is received after it has not been received in time. |
- |
liscal |
Warning |
178 |
request_id(%2) of ACK is not found in trans_table. (%3)
NMP%1 request_id(%2) of ACK is not found in trans_table. (%3) |
ACK (response to the sent recovery data) of procedure number[%2] was received. But the corresponding procedure number[%2] was not found in the queue in the driver. This message is output if ACK is received after it has not been received in time. |
- |
liscal |
Info |
179 |
NMP%1 received request to stop sending data, but its ID was not found in request_queue. |
The request to close communication of the mirror synchronization data was received, instead of ACK1, from the remote server. But the corresponding procedure number[%2] was not found in the queue in the driver. Waiting for ACK1 reception may have already timed out. |
- |
liscal |
Warning |
180 |
%2 (%3) is invalid. The default setting (%4) will be used instead.
NMP%1 %2 (%3) is invalid. The default setting (%4) will be used instead. |
The parameter[%2] (value:[%3]) is invalid. The default value[%4] is used instead. |
The setting file may have been mistakenly edited directly. Check the setting values by Cluster WebUI. For the details of the parameters, see the after-mentioned coping process 2 2 . |
liscal |
Info |
181 |
NMP%1 %2 (%3) is invalid. The maximum number (%4) will be used instead. |
The parameter[%2] (value:[%3]) is invalid. The maximum value[%4] is used instead. |
In case that the timeout magnification adjustment (clptoratio command) is used, the value may exceed the maximum value. In this case, the maximum value is used. For the details of the parameters, see the after-mentioned coping process 2 2 . |
liscal |
Error |
182 |
%2 (%3) is invalid. (%6)
NMP%1 %2 (%3) is invalid. (%6)
%2 (%3) or %4 (%5) is invalid. (%6)
NMP%1 %2 (%3) or %4 (%5) is invalid. (%6) |
The parameter[%2] (value:[%3]) or the parameter[%4] (value:[%5]) is invalid. |
The setting file may have been mistakenly edited directly. Check the setting values by Cluster WebUI. |
liscal |
Info |
183 |
NMP%1 %2 is %3. Heartbeat of mirror disk connection will be ignored. |
The parameter[%2] (value:[%3]) is specified. The mirror disk connection will not be used. |
- |
liscal |
Info |
184 |
The same %1 Partition is specified. Specify different partitions. (NMP%2, NMP%3) |
The [%1] (Cluster/Data) partition specification is invalid. The same partition is specified for multiple (NMP[%2] and NNP[%3]) resources. |
For the Linux version, separate cluster partitions and data partitions must be assigned to each resource. Correct the partition specification. If the partition configuration presents problems, also review the partition configuration. |
liscal |
Info |
190 |
NMP%1 sync switch flag is set to ON. %2 |
The data synchronization is enabled. |
- |
liscal |
Info |
191 |
NMP%1 sync switch flag is set to OFF. %2 |
The data synchronization is disabled. |
- |
liscal |
Info |
192 |
NMP%1 open I/O port OK. |
The I/O to the Data Partition started. |
- |
liscal |
Info |
193 |
NMP%1 close I/O port OK. |
The I/O to the Data Partition stopped. |
- |
liscal |
Info |
194 |
NMP%1 open mount port OK. |
The access to the mirror partition becomes possible. |
- |
liscal |
Info |
195 |
NMP%1 close mount port OK. |
The access to the mirror partition becomes impossible. |
- |
liscal |
Info |
196 |
NMP%1 open N/W port OK. |
The mirror synchronization data connection port is opened. |
- |
liscal |
Info |
197 |
NMP%1 close N/W port OK. |
The mirror synchronization data connection port is closed. |
- |
liscal |
Warning |
200 |
NMP%1 bmp_size_in_sec (%2) is invalid. |
The size of the area for the difference information is invalid. The Cluster Partition may be set incorrectly. |
Check the settings of the cluster partition in the cluster configuration data. |
liscal |
Warning |
201 |
NMP%1 failed to calculate bitmap offset (%2). |
Calculation of the area of the difference information failed. |
The OS may have become unstable. Restart the system. |
liscal |
Error |
202 |
NMP%1 sector size of Data Partition (%2) is invalid. |
The sector size of the Data Partition (%2) is too big. |
Check if there is any incorrect setting with the mirror disk or the hybrid disk initial construction step. |
liscal |
Warning |
203 |
NMP%1 failed to get total_bitmap_in_bits (%2). (%3) |
Getting the mirror difference information failed at procedure[%3]. |
Same as above. |
liscal |
Warning |
204 |
NMP%1 no trans_table available,recovery failed. |
The mirror recovery failed. The mirror recovery could not utilize the management area of recovery because the number of NMPs recovering mirror has exceeded the upper limit. |
Check the number of NMPs in the cluster configuration data. A problem may have occurred with the mirror driver. Restart the system and execute the mirror recovery again. |
liscal |
Warning |
205 |
NMP%1 failed to lock disk I/O, recovery failed. |
The mirror recovery failed. The mirror recovery could not exclude the other disk I/O. |
A problem may have occurred with the mirror driver. Restart the system and then execute the mirror recovery again. |
liscal |
Warning |
206 |
NMP%1 current NMP has been already locked. |
Excluding the other disk I/O has been already executed. (A number of mirror recovery processes tried to operate the same data block.) |
A problem may have occurred with the mirror driver. Restart the system and execute the mirror recovery again. |
liscal |
Warning |
207 |
NMP%1 current NMP has not been locked. |
The exclusion with the other disk I/O has already been released. |
Same as above. |
liscal |
Warning |
208 |
NMP%1 waited for sync data (sector=%2) written to disk completely, but timeout. |
The disk I/O to sector[%2] did not finish in time before reading the mirror recovery data. The mirror recovery is going to be executed. |
- |
liscal |
Info |
209 |
NMP%1 waiting for recovery data to be %2. (%3/%4) |
A shutdown request arrived while mirror recovery data is [%2] (read or written). [%3] of [%4] was being processed. The system waits for the remaining I/O to be completed. |
- |
liscal |
Warning |
210 |
NMP%1 failed to connect to remote server (err=%2). |
Connecting to the remote server failed because of the reason[%2]. |
|
liscal |
Info |
211 |
NMP%1 failed to send %2, retrying again. |
Sending [%2] failed. It will be sent again. |
|
liscal |
Warning |
212 |
NMP%1 failed to send %2. |
Sending [%2] failed. |
Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. Check if the mirror agent on the remote server is running. |
liscal |
Error |
213 |
NMP%1 failed to read recovery data. |
Reading the mirror recovery data failed. |
|
liscal |
Warning |
214 |
|
|
Same as above. |
liscal |
Info |
215 |
NMP%1 failed to recover because of %2. |
|
Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Info |
216 |
NMP%1 ACK timeout, %2, retrying again. |
The response to the sent data (%2) of the mirror recovery could not be received in time. The data will be sent again. |
(See the after-mentioned coping process 4 4 .) |
liscal |
Warning |
217 |
NMP%1 ACK timeout, %2, recovery failed. |
The response to the sent data (%2) of the mirror recovery could not be received in time again. The mirror recovery failed. |
(See the after-mentioned coping process 4 4 .) |
liscal |
Warning |
218 |
NMP%1 async send queue is full. Mirror break. |
The queue for the data to be sent has become full. The mirror break status is set. |
Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Info |
219 |
NMP%1 can not send async data, because N/W port has been closed. |
Data in the data transmission queue cannot be transmitted because the mirror disk connect is disconnected. |
Check the connection status of the mirror disk connect. Check whether the mirror disk connect, disk I/O, or OS is highly loaded. |
liscal |
Warning |
220 |
NMP%1 failed to create %2 socket (%3).
NMP%1 failed to create %2 socket. |
Creation of the connection for [%2] failed because of the reason[%3]. |
(See the after-mentioned coping process 3 3 ) - In case that the lack of resource is possible, execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Warning |
221 |
NMP%1 failed to bind %2 socket (%3). |
Same as above. |
Same as above. |
liscal |
Warning |
222 |
NMP%1 failed to listen %2 socket (%3). |
Same as above. |
Same as above. |
liscal |
Warning |
223 |
NMP%1 failed to accept %2 socket (%3). |
Same as above. |
Same as above. |
liscal |
Warning |
224 |
NMP%1 failed to receive %2 (err=%3).
NMP%1 failed to receive %2 (err=%3), %4. |
Receiving data[%2] (of the [%4] area) because of the reason[%3]. |
|
liscal |
Warning |
225 |
NMP%1 received wrong head part. (magic=%2 cmd=%3) (%4) |
Invalid data was received. (magic=[%2], cmd=[%3]) |
|
liscal |
Warning |
226 |
NMP%1 received wrong command (cmd=%2).
NMP%1 received wrong command (cmd=%2) instead of %3. |
Invalid mirror data was received. (cmd=[%2]) Invalid data was received at the port for the [%3] (HB / ACK2). (cmd=[%2]) |
Same as above. |
liscal |
Warning |
227 |
NMP%1 failed to uncompress %2. |
Uncompression of the data[%2] failed. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource). |
liscal |
Warning |
228 |
NMP%1 failed to execute received command. (cmd=%2, err=%3) |
The request of [%2] had been received and processed, but [%3] error occurred. |
For the details of the error, see the log output before this log. |
liscal |
Warning |
229 |
NMP%1 failed to receive data, because recv_sock is NULL. |
Receiving the mirror data failed. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Info |
230 |
NMP%1 recv_sock is NULL, can not delete keepalive timer. |
Same as above. |
Same as above. |
liscal |
Warning |
231 |
NMP%1 accepted receive data, but this server is not current server of hybrid disk. |
The local server received the mirror data even though the other server is running as the Current server of hybrid disk configuration. The received data was ignored. The received data will be sent again from the source server to the Current server. |
- |
liscal |
Info |
232 |
NMP%1 disconnected %2 N/W. (%3) |
The connection to receive [%2] (DATA / HB / ACK2) was disconnected at procedure[%3]. |
- |
liscal |
Info |
233 |
NMP%1 failed to receive recovery data at remote server, retrying again. |
The remote server could not receive the recovery data. The local server is going to send it again. |
Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Warning |
234 |
NMP%1 failed to receive recovery data at remote server, recovery failed. |
The remote server could not receive the recovery data again. Recovery was failed. |
Same as above. |
liscal |
Warning |
235 |
NMP%1 gave up ACK before ACK timeout. |
Waiting for the response to the sent mirror recovery data (ACK) was suspended before ACK receive timeout occurs due to the disconnection of mirror disk connection. |
Same as above. |
liscal |
Warning |
236 |
NMP%1 gave up ACK1 before ACK1 timeout. |
Waiting for the response to the sent mirror recovery data (ACK1) was suspended before ACK receive timeout occurs due to the disconnection of mirror disk connection. |
Same as above. |
liscal |
Warning |
240 |
NMP%1 status of current using N/W is ERROR. (%2) |
The mirror disk connection is abnormal. Then the data could not be sent. |
Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Warning |
241 |
NMP%1 can not find a N/W to use. (%2) |
There is no mirror disk connection available for [%2] (DATA / HB / ACK2). |
Check the cluster configuration information. Check the mirror disk connection status. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Warning |
242 |
NMP%1 all of the networks are ERROR. |
All the mirror disk connections became abnormal. |
Same as above. |
liscal |
Info |
243 |
NMP%1 N/W is %2 %3 - %4 :%5(%6)
NMP%1 N/W is %2 %3 - %4 |
The status of the current mirror disk connection for [%6] (DATA / HB / ACK2) was changed to [%2] (ERROR / USING / FREE). IP addresses: [%3] and [%4] Port: [%5] |
Check the mirror disk connection status in case that the status is ERROR. Check that neither mirror disk connection nor the operating system is loaded heavily. |
liscal |
Warning |
250 |
Received ICMP. Length of received ICMP is less than 8. |
ICMP packet was received. But its length was Invalid. It was Ignored. |
- |
liscal |
Info |
251 |
Received ICMP. Type=(%1) Code=(%2) |
ICMP packet of type [%1] and code [%2] was received. ("Destination unreachable" was received.) |
- |
liscal |
Info |
252 |
Received ICMP. Type=(%1) Code=(%2). Ignored.
Received ICMP. Type=(%1) with same ID(%3). Ignored. |
ICMP packet of type [%1] , code [%2] and ID [%3] was received. It was Ignored. |
- |
liscal |
Warning |
260 |
NMP%1 failed to switch N/W to (priority:%2). (%3) |
Switching the mirror disk connection was requested. But it failed because of the reason [%3]. |
|
liscal |
Info |
261 |
NMP%1 already switched N/W to (priority:%2). |
Switching the mirror disk connection was requested. But it has already been switched to [%2]. |
- |
liscal |
Info |
262 |
NMP%1 uses N/W (priority:%2). |
The mirror disk connection of the priority [%2] will be used. |
- |
liscal |
Info |
263 |
NMP%1 switched N/W from (priority:%2) to (priority:%3). |
Switching the mirror disk connection was requested. Then the mirror disk connection of the priority [%2] will be used instead of the priority [%3]. |
- |
liscal |
Info |
270 |
NMP%1 this FS type (%2) is not supported for high speed full copy. |
In the current version this file system cannot be processed with the high speed full-copy. Full-copy will be performed without an analysis of the file system instead. |
- |
liscal |
Info |
271 |
NMP%1 FS type is %2. |
The target file systems for mirror recovery are [%2] (EXT2 / EXT3 / EXT4). |
- |
liscal |
Warning |
272 |
NMP%1 could not read %2 of FS. |
Reading the [%2] area of the file system failed. Full-copy will be performed without an analysis of the file system instead. |
- |
liscal |
Warning |
273 |
NMP%1 failed to set the bitmap dependent on FS. |
Creation of the difference information corresponding to the area used by the file system failed. Full-copy will be performed without an analysis of the file system instead |
- |
liscal |
Info |
280 |
NMP%1 requested to change compress flag. (Sync data : %2) (Recovery data : %3) |
Compression of the mirror transfer data was changed to [%2] (ON / OFF) and [%3] (ON / OFF). |
- |
liscal |
Info |
281 |
The compression function for mirror transfer data is set to [%2](ON/OFF) and [%3](ON/OFF). |
- |
|
liscal |
Error |
282 |
NMP%1 failed to set %2 key. (%3) |
The encryption key failed to be set. |
|
liscal |
Error |
283 |
NMP%1 failed to encrypt magic data. (err=%2%3) |
Mirror data failed to be encrypted. |
|
NMP%1 failed to encrypt data. (err=%2%3) |
The same as above |
The same as above |
|||
NMP%1 failed to encrypt data. (encryption serial no overflow) (%2) |
The encryption serial number overflowed. |
Update the encryption key of NMP%1. |
|||
liscal |
Error |
284 |
NMP%1 failed to decrypt magic data. (err=%2%3) |
Mirror data failed to be decrypted. |
|
NMP%1 failed to decrypt data. (err=%2%3) |
The same as above |
The same as above |
|||
NMP%1 failed to decrypt data. (encryption serial no overflow) (%2) |
The encryption serial number overflowed. |
Update the encryption key of NMP%1. |
|||
liscal |
Info |
285 |
NMP%1 using crypto. |
The mirror communication encryption function for NMP%1 is enabled. |
- |
liscal |
Error |
286 |
NMP%1 received invalid data. (%2) |
The decrypted data is invalid. |
|
liscal |
Error |
287 |
NMP%1 Internal error. receiving size (%2) > buffer size (%3) (%4) |
The size of the received encryption data is invalid. |
|
NMP%1 received invalid length. (len=%2, offset=%3) |
The same as above |
The same as above |
|||
liscal |
Error |
288 |
NMP%1 failed to set auth size. (%2) |
The initialization of the encryption function failed. |
|
liscal |
Info |
290 |
NMP%1 logging statistics information started. (PID=%2) |
Logging of mirror statistic information has started. |
- |
liscal |
Info |
291 |
NMP%1 logging statistics information stopped. (PID=%2) |
Logging of mirror statistic information has stopped. |
- |
liscal |
Info |
292 |
NMP%1 logging statistics information cleared. |
The mirror statistic information counter has been cleared. |
- |
liscal |
Warning |
293 |
NMP%1 statistics information not found. (PID=%2) |
Internal error Processing has not yet been started, or an attempt was made to access a mirror statistic information record that had already ended. |
If mirror statistic information was already acquired by a command, reexecute that command. |
liscal |
Info |
294 |
Perf%1 |
Output result [%1] of mirror statistic information |
- |
liscal |
Info |
300 |
NMP%1 QoS %2 KB/sec. |
The band limitation was set to [%2]. |
- |
liscal |
Error |
310 |
NMP%d failed to delete history information. (%1) |
The history of unsent data was not deleted. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource) when the lack of resource is possible. The physical defect may have occurred with mirror disk in case of being output while in operation. See "The system maintenance information" in the "Maintenance Guide", exchange the mirror disks and run mirror recovery. |
liscal |
Error |
311 |
NMP%d failed to read history information. (%1) |
The history of unsent data was not read. |
The physical defect may have occurred with mirror disk in case of being output while in operation. See "The system maintenance information" in the "Maintenance Guide", exchange the mirror disks and run mirror recovery. |
liscal |
Error |
312 |
NMP%d failed to write history information. (%1) |
The history of unsent data was not written. |
Same as above. |
liscal |
Error |
313 |
NMP%d failed to write history information. (overflow) |
The number of records reached the maximum of the history of unsent data. |
|
liscal |
Error |
321 |
NMP%d failed to read a history file. (%1) |
The history file was not read. |
|
liscal |
Error |
322 |
NMP%d failed to write a history file. (%1) |
The history file was not written. |
Execute the after-mentioned coping process 1 1 (coping process to lack of resource) when the lack of resource is possible. The OS may have become unstable. Restart the system. The partition of the history file directory may not have enough free space. Maintain enough free space. The physical defect may have occurred with the disk of the history file directory in case of being output while in operation. Change the settings of the history file directory or replace the disk. |
liscal |
Error |
323 |
NMP%d failed to write a history file. (overflow) |
The total size reached the maximum of the history file. |
|
liscal |
Error |
324 |
NMP%d failed to delete a history file. (%1) |
The history file was not deleted. |
Check that the history file directory or the file in it has been used by any other application. |
liscal |
Error |
330 |
NMP%d Internal error. (%1) |
Internal error. |
A problem may have occurred with the mirror driver. Restart the system. |
liscal |
Info |
331 |
--- Previous liscal message repeated %1 times --- |
The last message was output consecutively %1 times. |
- |
1 coping process 1 coping process to lack of resource
The physical memory may be running short.
Add more physical memory or stop unnecessary applications.
|
The upper limit of I/O request queue number ensured by the mirror driver may be too big.
In case that a massive amount of I/O over transaction performance are requested to the mirror disk, the kernel memory is used because the I/O requests are queued in the mirror driver.
Decrease the maximum number of the request queue in "Mirror Driver" tab of "Cluster Properties" by seeing " 2. Parameter details" in this guide.
|
The file system may ensure a massive amount of the cache.
In case that a massive amount of I/O over transaction performance are requested, the memory zone for kernel space may be used for the file system cache in addition to the cache and the memory zone for user space.
In that case, as a workaround, keep the memory zone for kernel space used by the driver from being utilized as the cache by setting /proc/sys/vm/lower_zone_protection.
|
2 coping process 2 Parameters
Parameter names output in log |
Setting Item Names in
the Cluster WebUI
|
Positions of Setting Items
in the Cluster WebUI
|
---|---|---|
Bitmap refresh interval |
Bitmap Refresh Interval
(bpchkinterval)
|
Cluster Properties
Mirror Driver tab
|
max_cachenum |
(maxcache) |
(In the configuration file) |
send_queue_size |
The number of queues
(sendqueuesize)
|
Mirror Disk Resource Tuning Properties
Mirror tab
|
band_limit_mode |
Rate limitation of Mirror Connect
(mode)
|
Same as above. |
band_limit |
Rate limitation of Mirror Connect
(bandlimit)
|
Same as above. |
ack_timeout |
Ack Timeout
(acktimeout)
|
Mirror Disk Resource Tuning Properties
Mirror Driver tab
|
connect_timeout |
Connection Timeout
(connecttimeout)
|
Same as above. |
send_timeout |
Send Timeout
(sendtimeout)
|
Same as above. |
receive_normal_timeout |
Receive Timeout
(recvnormaltimeout)
|
Same as above. |
hb_interval |
Heartbeat Interval
(hbinterval)
|
Same as above. |
hb_recv_timeout |
ICMP Receive Timeout
(pingtimeout)
|
Same as above. |
hb_recv_retry |
ICMP Retry Count
(pingretry)
|
Same as above. |
keepalive_time |
(keepalive/timeout) |
(In the configuration file) |
keepalive_probe |
(keepalive/prob) |
Same as above. |
keepalive_interval |
(keepalive/interval) |
Same as above. |
lastupdate_delay |
(lupdatedelay) |
Same as above. |
For the details of each parameter, see the following chapters in this Guide.
"Understanding Mirror disk resources" and "Understanding Hybrid disk resources" in "3. Group resource details"
"Adjusting time-out temporarily (clptoratio command)" in "9. EXPRESSCLUSTER command reference"
3 coping process 3 For the details of the ports used by the mirror driver, see the following.
"Connection port number" in "Notes and Restrictions" in the "Getting Started Guide"
"Changing the range of automatic allocation for the communication port numbers" in "Notes and Restrictions" in the "Getting Started Guide"
"Understanding mirror parameters" of "3. Group resource details" in the "Reference Guide"
"Mirror driver tab" of "3. Group resource details" in the "Reference Guide"
"Communication ports" of "The system maintenance information" in the "Maintenance Guide"
"Settings after configuration hardware" of "Determining a system configuration" in the "Installation and Configuration Guide"
4 coping process 4 Timeout parameters of mirror
Setting Item Names in |
Positions of Setting Items |
---|---|
the Cluster WebUI |
in the Cluster WebUI |
Recovery Data Size |
Cluster Properties
Mirror Agent tab
|
Ack Timeout |
Mirror Disk Resource Tuning Properties |
Connection Timeout
Mirror Driver tab
|
Same as above. |
Send Timeout |
Same as above. |
Receive Timeout |
Same as above. |
For the details of each parameter, see the following chapters in this guide.
11.3.2. 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) |
Loading the clpkhb driver failed. |
- |
clpkhb |
Error |
104 |
Can not deregister miscdev on minor=%1. (err=%2) |
Unloading the clpkhb driver failed. |
- |
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! |
The clpkhb driver failed to create proc file. |
- |
clpkhb |
Error |
108 |
Version error. |
The inside version information of the clpkhb driver is invalid. |
Reinstall EXPRESSCLUSTER. |
clpkhb |
Info |
110 |
|
|
- |
clpkhb |
Error |
111 |
|
|
- |
clpkhb |
Info |
112 |
|
|
- |
clpkhb |
Info |
113 |
Killed the recv thread successfully. |
The clpkhb driver is going to stop. |
- |
clpkhb |
Info |
114 |
Killed the recv thread successfully. |
The clpkhb driver is going to stop. |
- |
clpkhb |
Info |
115 |
Kernel Heartbeat has been stopped |
The clpkhb driver successfully stopped. |
- |
clpkhb |
Error |
120 |
|
|
- |
clpkhb |
Error |
121 |
Failed to create sending %1 socket address. (err=%2) |
Setting the socket for sending the [%1] (HB / DOWN / KA) packet failed. |
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) |
Setting the socket for sending the [%1] (HB / DOWN / KA) packet failed. |
The physical memory may be running out. Add physical memories, or terminate unnecessary applications. |
clpkhb |
Error |
123 |
Failed to bind %1 socket. (err=%2) |
Binding the socket for [%1] (HB / DOWN / KA) failed. |
|
clpkhb |
Error |
125 |
Failed to send %1 data to %2. (err=%3) |
Sending [%1] (HB / DOWN / KA) data to [%2] failed. |
|
clpkhb |
Error |
126 |
Failed to receive data. (err=%3) |
Receiving data failed. |
|
clpkhb |
Info |
127 |
|
|
Other applications may be sending the data to the port for clpkhb. Change the Heartbeat Port Number if other applications use it. |
clpkhb |
Error |
128 |
|
|
Same as above. |
clpkhb |
Info |
129 |
Receiving operation was interrupted by ending signal! |
The receive thread ends by termination signal. |
- |
clpkhb |
Info |
130 |
|
|
Check the status of the server where the reboot occurred. |
clpkhb |
Info |
131 |
|
|
Check the status of the server where the panic occurred. |
clpkhb |
Error |
140 |
Reference an inaccessible memory area! |
ioctl() failed to pass data to an application. |
Check the status of the operating system. |
clpkhb |
Error |
141 |
Failed to allocate memory! |
Memory allocation failed. |
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. |
11.3.3. 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) |
Loading the clpka driver failed. |
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! |
The clpka driver failed to create proc file. |
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) |
The clpka driver failed to create the thread. |
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. |
The clpka driver is going to restart the machine according to the action setting. |
- |
clpka |
Info |
132 |
Kernel do nothing. |
The clpka driver is not going to do anything according to the action setting. |
- |
clpka |
Error |
140 |
Reference an inaccessible memory area! |
Passing the version information of the clpka driver to the cluster main body failed. |
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. |
11.4. Detailed information in activating and deactivating group resources¶
11.4.1. Floating IP resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
fip |
Error |
3 |
Command failed. (%1, ret=%2) |
Failed in executing the command %1. The return value is %2. |
Analyze the failure from the return value of the command. |
fip |
Error |
11 |
Command failed. (%1(%2), errno=%3) |
An error has occurred in executing the command. |
Memory or OS resources may not be sufficient. Check them. |
fip |
Error |
14 |
IP address did not exist. |
Failed to get the IP address list. |
Confirm that the OS can use the TCP/IP protocol. |
fip |
Error |
15 |
IP address was already used. |
The IP address is already used. |
Check the IP address is not already used. |
fip |
Error |
15 |
This ip address was already used. IP=%1 |
The specified IP address exists on the same network. |
Check if the specified IP address is not used on the network. |
fip |
Error |
15 |
The device has another IP address specified as the transmission source. Device=%1 |
The device has another IP address specified as the transmission source. |
Check the resource settings. You can specify only one FIP address as the transmission source for each device. |
fip |
Error |
17 |
Fip interface was not found. |
Floating IP address interface was not found. |
Check if the FIP address network is the same as the server's real IP address. |
fip |
Error |
others |
Internal error. (status=%1) |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.2. Virtual IP resource¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
vip |
Error |
3 |
Command failed. (%1, ret=%2) |
Failed in executing the command %1. The return value is %2. |
Analyze the failure from the return value of the command. |
vip |
Error |
11 |
Command failed. (%1(%2), errno=%3) |
An error has occurred in executing the command. |
Memory or OS resources may not be sufficient. Check them. |
vip |
Error |
14 |
IP address did not exist. |
Failed to acquire the list of IP addresses. |
Check the OS is in the environment that supports the TCP/IP protocol. |
vip |
Error |
15 |
IP address was already used. |
The IP address is already used. |
Check if the IP address is not already used. |
vip |
Error |
15 |
This ip address was already used. IP=%1 |
The specified IP address exists on the same network. |
Check if the specified IP address is not already used on the network. |
vip |
Error |
17 |
Vip interface was not found. |
The specified interface was not found. |
Check if the specified interface exists on the server. |
vip |
Error |
Others |
Internal error. (status=%1) |
Other internal error was occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.3. Disk resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
disk |
Error |
1 |
Resource name was invalid. (%1) |
The resource name is invalid. |
Check the resource name is consistent with the information in the cluster configuration data. |
disk |
Error |
1 |
Group name was invalid. (%1) |
The group resource name is invalid. |
Check the group name is consistent with the information in the cluster configuration data. |
disk |
Error |
1 |
Resource was not in config. (%1) |
The resource name does not exist in the cluster configuration data. |
Check the resource name is consistent with the information in the cluster configuration data. |
disk |
Error |
1 |
Group was not in config. (%1) |
The group resource name does not exist in the cluster configuration data. |
Check the group resource name is consistent with the information in the cluster configuration data. |
disk |
Error |
1 |
Getting of config was failed. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
disk |
Error |
1 |
Mount point was already mounted. (%1) |
The device has already been mounted. |
Check if the specified device is unmounted. |
disk |
Error |
1 |
Mount point was not mounted. (%1) |
The mount point was not mounted. |
An active resource may have been manually unmounted. Check its status. |
disk |
Error |
1 |
Mount point was invalid. (%1) |
The mount point is invalid. |
Check the mount point exists. |
disk |
Error |
1 |
Creating of mount point was failed. (%1) |
Failed to create the mount point. |
Memory or OS resources may not be sufficient. Check them. |
disk |
Error |
1 |
Raw device was already bound. (%1) |
The RAW device has already been bound by another device. |
Check if the unique raw device is set in the cluster. |
disk |
Error |
1 |
Max recover retry over. (%1, retry=%2) |
The number of retires made for activating the device has exceeded the maximum retry count. |
Check the cluster configuration data is correct. |
disk |
Error |
1 |
Command path was invalid. (%1) |
The execution path is invalid. |
Check the command execution path. |
disk |
Error |
1 |
Command timeout. (%1, timeout=%2) |
Detected an internal timeout. |
The OS may be heavily loaded. Check its status. |
disk |
Error |
1 |
Command failed. (%1, ret=%2) |
The command %1 failed. Its return value is %2. |
Troubleshoot the problem by using the return value from the command. |
disk |
Error |
1 |
Command failed. (%1(%2), errno=%3) |
The device operation terminated abnormally. |
Memory or OS resources may not be sufficient. Check them. |
disk |
Error |
1 |
Internal error. (status=%1) |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.4. EXEC resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
exec |
Error |
1 |
Termination code %1 was returned. |
An exit code other than 0 (zero) was returned as the result of a synchronous script or application. |
There may be a problem in the content of the script. Check the script is correct.
The application may have abnormally terminated. Check how the application is working.
|
exec |
Error |
1 |
Command was not completed within %1 seconds. |
A synchronous script or application did not successfully complete within the specified time. |
There may be a problem in the content of the script. Check if the script is correct.
The application may be stalling. Check if the application is working properly.
You may be able to identify the cause from the logs in both cases. For details about logging settings, see "2. Parameter details".
|
exec |
Error |
1 |
Command was aborted. |
A synchronous script or application terminated abnormally. |
The application may have abnormally terminated. Check how the application is working.
Memory or OS resources may not be sufficient. Check them.
|
exec |
Error |
1 |
Command was not found. (error=%1) |
The application does not exist. |
The path to the application may be invalid. Check it in the cluster configuration data |
exec |
Error |
1 |
Command string was invalid. |
The application path is invalid. |
Check the application path in the cluster configuration data. |
exec |
Error |
1 |
Log string was invalid. |
The log output path is invalid. |
Check the log output path in the cluster configuration data. |
exec |
Error |
1 |
Internal error. (status=%1) |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.5. Mirror disk resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
md |
Error |
1 |
Need to start mirror agent at first. |
The Mirror Agent is not active. |
Check if the Mirror Agent is activated. |
md |
Error |
2 |
Options or parameters are invalid. |
Parameters are invalid. |
Check the cluster configuration data is correct. |
md |
Error |
4 |
Getting of config was failed. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
md |
Error |
10 |
NMP size of local server is bigger, can not active |
The server cannot activate the mirror disk resource because the size of NMP of the local server is larger than that of the remote server. |
Execute the forcible mirror recovery using the remote server as the one to be mirrored. |
md |
Error |
30 |
Internal error[status=%1] |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them.
If the status is 2359554, the previous start or execution of a system command such as fsck may have failed. In this case, check the result of the failed command.
|
md |
Error |
77 |
Mirror disk was not in config.(%1) |
Configuration data of the mirror disk resource is invalid. |
Check the cluster configuration data is correct. |
md |
Error |
79 |
Failed to get cluster partition information. |
Failed to obtain the cluster partition data. |
Check the partition is allocated and the operating system can recognize the disk. |
md |
Error |
80 |
Mount point was already mounted.(%1) |
The mount point has already been mounted. |
Check if the mount point of the mirror disk resource has been mounted manually. |
md |
Error |
81 |
The local server has not the latest data.(%1) |
The local server does not have the latest data. |
Perform the mirror recovery. |
md |
Error |
82 |
Failed to set cluster partition information. |
Failed to access the cluster partition. |
Check if the partition is allocated, and the operating system can recognize the disk. |
md |
Error |
83 |
Command timeout(%1, timeout=%2) |
The system command timed out. |
It took longer than expected to run the system command.
Tune the mount time-out, unmount time-out, and fsck time-out values. For details, see "2. Parameter details"
|
md |
Error |
84 |
Mount point was not mounted. (%1) |
The mirror disk resource is not mounted. |
Check if it has manually been unmounted. Check the memory. EXPRESSCLUSTER controls mounting and unmounting. Do not mount or unmount it manually. |
md |
Error |
87 |
Creating of mount point was failed. (%1) |
Failed to create the mount point. |
Check mount point has been specified in the cluster configuration data.
Check if the mount point exists.
|
md |
Error |
89 |
Command failed. (%1) |
Failed to run the system command. |
Check if mount, unmount and fsck commands exist. |
11.4.6. Hybrid disk resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
hd |
Error |
1 |
Need to start mirror agent at first. |
The Mirror Agent is not active. |
Check if the Mirror Agent is activated. |
hd |
Error |
2 |
Options or parameters are invalid. |
Parameters are invalid. |
Check the cluster configuration data is correct. |
hd |
Error |
4 |
Getting of config was failed. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
hd |
Error |
10 |
NMP size of local server is bigger, can not active |
The server cannot activate the mirror disk resource because the size of NMP of the local server is larger than that of the remote server. |
Execute the forcible mirror recovery using the remote server as the one to be mirrored. |
hd |
Error |
12 |
The local server is not current server. |
Resources cannot be operated because the local server is not current server. |
Operate the resources after acquiring the condition where current priority can be acquired in the local server or acquiring the current priority. |
hd |
Error |
30 |
Internal error[status=%1] |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
hd |
Warning |
48 |
The Auto mirror recovery check box is not selected. It is necessary to recover the mirror manually, in order to resume mirroring (%1). |
The resumption of mirroring requires recovering the mirror manually. |
Start the mirror recovery with the command or from the mirror disk list. |
hd |
Error |
77 |
Hybrid disk was not in config.(%1) |
Configuration data of the hybrid disk resource is invalid. |
Check the cluster configuration data is correct. |
hd |
Error |
79 |
Failed to get cluster partition information. |
Failed to obtain the cluster partition data. |
Check the partition is allocated and the operating system can recognize the disk. |
hd |
Error |
80 |
Mount point was already mounted.(%1) |
The mount point has already been mounted. |
Check if the mount point of the mirror disk resource has been mounted manually. |
hd |
Error |
81 |
The local server has not the latest data.(%1) |
The local server does not have the latest data. |
Perform the mirror recovery. |
hd |
Error |
82 |
Failed to set cluster partition information. |
Failed to access the cluster partition. |
Check if the partition is allocated, and the operating system can recognize the disk. |
hd |
Error |
83 |
Command timeout(%1, timeout=%2) |
The system command timed out. |
It took longer than expected to run the system command.
Tune the mount time-out, unmount time-out, and fsck time-out values. For details, see "2. Parameter details"
|
hd |
Error |
84 |
Mount point was not mounted. (%1) |
The mirror disk resource is not mounted. |
Check if it has manually been unmounted. Check the memory. EXPRESSCLUSTER controls mounting and unmounting. Do not mount or unmount it manually. |
hd |
Error |
87 |
Creating of mount point was failed. (%1) |
Failed to create the mount point. |
Check mount point has been specified in the cluster configuration data.
Check if the mount point exists.
|
hd |
Error |
89 |
Command failed. (%1) |
Failed to run the system command. |
Check if mount, unmount and fsck commands exist. |
hd |
Error |
90 |
Failed to be current server. |
Current priority cannot be acquired. |
Check if hybrid disk resource is activated.
If the hybrid disk is being recovered or current priority is being processed in another server, wait for a while.
|
11.4.7. Volume manager resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
volmgr |
Error |
4 |
Invalid Config. |
The cluster configuration information is invalid. |
Check if the cluster configuration information is consistent. |
volmgr |
Error |
10 |
Already Imported. |
The target has already been imported. |
Check the target has been exported before startup of the cluster. |
volmgr |
Error |
11 |
Other Host Imported.(host=%1) |
The target has already been imported by host %1. |
Check whether the target has been exported before startup of the cluster. |
volmgr |
Error |
12
14
|
Command("%1") Error.(cmdret=%2) |
Command %1 failed. The return value of the command is %2. |
Analyze the error by the return value of the command. |
volmgr |
Error |
Other |
Internal Error.(ret=%1) |
Another internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.8. Dynamic DNS resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
ddns |
Error |
1 |
Initialize error. |
An error was detected during initialization. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddns |
Error |
2 |
open() failed.(err=%1) |
Opening the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddns |
Error |
3 |
write() failed.(err=%1) |
Writing to the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddns |
Error |
4 |
closed() failed.(err=%1) |
Closing the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddns |
Error |
5 |
nsupdate command has failed(%1). |
Executing the nsupdate command failed. |
Analyze the error by referring to the command return value. |
ddns |
Error |
90 |
Memory allocation error.(err=%1) |
An internal memory allocation error occurred. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddns |
Error |
92 |
Time out. |
An internal timeout was detected. |
The OS might be heavily loaded. Check whether this is so. |
ddns |
Error |
Other |
Internal error.(status=%d) |
A different internal error occurred. |
There might not be enough memory space or OS resources. Check whether this is so. |
11.4.9. AWS elastic ip resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awseip |
Error |
5 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awseip |
Error |
5 |
The allocation ID '%1' does not exist |
The specified EIP ALLOCATION ID %1 does not exist. |
Check if the value of EIP ALLOCATION ID is correct. |
awseip |
Error |
5 |
The networkInterface ID '%1' does not exist) |
The specified ENI ID %1 does not exist. |
Check if the value of ENI ID is correct. |
awseip |
Error |
6 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awseip |
Error |
7 |
ENI ID is invalid.(ENI ID=%1) |
ENI ID is invalid. |
Check if the ENI ID is correct.
Check if ENI ID of other instance is specified mistakenly
|
awseip |
Error |
99 |
Internal error. (status=%1) |
An internal error occurred. |
Check if Python is installed correctly.
Check if AWS CLI is installed correctly.
Memory or OS resources may not be sufficient. Check them.
|
11.4.10. AWS virtual ip resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awsvip |
Error |
50 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsvip |
Error |
50 |
The vpc ID '%1' does not exist |
The specified VPC ID %1 does not exist. |
Check if the value of VPC ID is correct. |
awsvip |
Error |
50 |
The networkInterface ID '%1' does not exist) |
The specified ENI ID %1 does not exist. |
Check if the value of ENI ID is correct. |
awsvip |
Error |
51 |
The AWS CLI command is not found. |
The AWS CLI command is not found. |
Check if AWS CLI is installed correctly. |
awsvip |
Error |
52 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of AWS virtual ip resource. |
awsvip |
Error |
53 |
The VIP address %1 belongs to a VPC subnet. |
The VIP address %1 belongs to a VPC CIDR. |
For the VIP address, an IP address not belonging to a VPC CIDR must be specified.
Check the VIP address.
|
awsvip |
Error |
54 |
Failed to add the VIP address %1. |
Failed to add the VIP address %1. |
Check the VIP settings.
Memory or OS resources may not be sufficient. Check them.
|
awsvip |
Error |
55 |
Failed to delete the VIP address %1. |
Failed to delete the VIP address %1. |
Memory or OS resources may not be sufficient. Check them. |
awsvip |
Error |
56 |
Failed to obtain a NIC name. |
Failed to obtain a NIC name. |
Check the settings of AWS virtual ip resource.
Memory or OS resources may not be sufficient. Check them.
|
11.4.11. AWS secondary ip resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awssip |
Error |
50 |
The AWS CLI command is not found. |
The AWS CLI command is not found. |
Check if AWS CLI is installed correctly. |
awssip |
Error |
51 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of AWS secondary ip resource. |
awssip |
Error |
52 |
Failed to assign the secondary IP address on the AWS side. |
Failed to assign the secondary IP address on the AWS side. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssip |
Error |
53 |
Failed to release the assigned secondary IP address on the AWS side. |
Failed to release the assigned secondary IP address on the AWS side. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssip |
Error |
54 |
Failed to process checking the secondary IP address on the AWS side. |
Failed to process checking the secondary IP address on the AWS side. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssip |
Error |
55 |
Failed to assign the secondary IP address on the OS side. |
Failed to assign the secondary IP address on the OS side. |
Check the settings of AWS secondary ip resource.
Memory or OS resources may not be sufficient. Check them.
|
awssip |
Error |
56 |
Failed to release the assigned secondary IP address on the OS side. |
Failed to release the assigned secondary IP address on the OS side. |
Check the settings of AWS secondary ip resource.
Memory or OS resources may not be sufficient. Check them.
|
awssip |
Error |
57 |
Failed to process checking the secondary IP address on the OS side. |
Failed to process checking the secondary IP address on the OS side. |
Check the settings of AWS secondary ip resource.
Memory or OS resources may not be sufficient. Check them.
|
awssip |
Error |
58 |
Failed to obtain a MAC address. |
Failed to obtain a MAC address. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssip |
Error |
59 |
Failed to obtain a NIC name. |
Failed to obtain a NIC name. |
Check the settings of AWS secondary ip resource.
Memory or OS resources may not be sufficient. Check them.
|
awssip |
Error |
60 |
Failed to obtain a subnet ID. |
Failed to obtain a subnet ID. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssip |
Error |
61 |
Failed to obtain a CIDR block. |
Failed to obtain a CIDR block. |
Check the settings of AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
11.4.12. AWS DNS resource¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awsdns |
Error |
5 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsdns |
Error |
6 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awsdns |
Error |
99 |
Internal error. (status=%1) |
An internal error occurred. |
Confirm that Python is installed correctly.
Confirm that AWS CLI is installed correctly.
Memory or OS resources may not be sufficient. Check them.
|
11.4.13. Azure probe port resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
azurepp |
Error |
5 |
Probe port %1 is already used. |
Probe port %1 is already used. |
Check if the probe port is already opened on the local server. |
azurepp |
Error |
6 |
Failed to open the probe port %1. |
Releasing probe port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
azurepp |
Error |
7 |
Failed to close the probe port %1. |
Closing probe port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
azurepp |
Error |
8 |
Failed to stop the probe port %1 control process. |
Stopping probe port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them.
Reboot the OS.
|
azurepp |
Error |
9 |
The probe port %1 control process has already started. |
Probe port %1 control process is already started. |
Memory or OS resources may not be sufficient. Check them.
Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the probe port control process (clpazureppp) manually.
|
azurepp |
Error |
10 |
Failed to start the probe port %1 control process. |
Starting probe port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them. |
azurepp |
Error |
99 |
Internal error. (status=%1) |
An internal error has occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.14. Azure DNS resource¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
azuredns |
Error |
41 |
Timeout occurred when Azure CLI command was executed. |
The Azure CLI command was not executed within Azure CLI Timeout. |
Confirm that the Azure CLI command can be executed properly in the EXPRESSCLUSTER server.
Check the load status of the server and remove the load.
Check the value of Azure CLI Timeout.
|
azuredns |
Error |
42 |
Azure CLI command failed. |
The Azure CLI command was executed. However, an error was returned. |
Confirm that the setting of the resource is correct. |
azuredns |
Error |
43 |
Azure CLI command not found. |
The Azure CLI command is missing. |
Confirm that the setting of Azure CLI File Path is correct and that Azure CLI is properly installed. |
azuredns |
Error |
99 |
Internal error. |
An internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.15. Google Cloud virtual IP resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
gcvip |
Error |
5 |
Port %1 is already used. |
Port %1 is already used. |
Check if the port specified for Port Number on the local server has not already been opened. |
gcvip |
Error |
6 |
Failed to open the port %1. |
Opening the port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
gcvip |
Error |
7 |
Failed to close the port %1. |
Closing the port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
gcvip |
Error |
8 |
Failed to stop the port %1 control process. |
Stopping the port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them.
Restart OS.
|
gcvip |
Error |
9 |
The port %1 control process has already started. |
The port %1 control process has already started. |
Memory or OS resources may not be sufficient. Check them.
Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the port control process (clpgcvipp) manually.
|
gcvip |
Error |
10 |
Failed to start the port %1 control process. |
Starting the port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them. |
gcvip |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.4.16. Google Cloud DNS resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
gcdns |
Error |
50 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of Google Cloud DNS resource. |
gcdns |
Error |
51 |
Failed to obtain the record set. |
Failed to obtain the record set of Cloud DNS. |
Check the setting value of Google Cloud DNS resource and the privilege of the account which permitted Cloud SDK. |
gcdns |
Error |
52 |
Failed to start the transaction. |
Failed to start the transaction. |
Check the privilege of the account which permitted Cloud SDK. |
gcdns |
Error |
53 |
Failed to delete the record set. |
Failed to add the record set deletion processing to the transaction. |
Check the privilege of the account which permitted Cloud SDK. |
gcdns |
Error |
54 |
Failed to add the record set. |
Failed to add the record set addition processing to the transaction. |
Check the privilege of the account which permitted Cloud SDK. |
gcdns |
Error |
55 |
Failed to execute the transaction. |
Failed to execute the transaction. |
Check the privilege of the account which permitted Cloud SDK. |
gcdns |
Error |
56 |
Detected an invalid parameter. |
An internal error occurred. |
- |
11.4.17. Oracle Cloud virtual IP resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
ocvip |
Error |
5 |
Port %1 is already used. |
Port %1 is already used. |
Check if the port specified for Port Number on the local server has not already been opened. |
ocvip |
Error |
6 |
Failed to open the port %1. |
Opening the port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
ocvip |
Error |
7 |
Failed to close the port %1. |
Closing the port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
ocvip |
Error |
8 |
Failed to stop the port %1 control process. |
Stopping the port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them.
Restart OS.
|
ocvip |
Error |
9 |
The port %1 control process has already started. |
The port %1 control process has already started. |
Memory or OS resources may not be sufficient. Check them.
Or, the immediately preceding deactivation may have failed. In that case, stop the cluster and forcibly terminate the port control process (clpocvipp) manually.
|
ocvip |
Error |
10 |
Failed to start the port %1 control process. |
Starting the port %1 control process failed. |
Memory or OS resources may not be sufficient. Check them. |
ocvip |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5. Detailed info of monitor resource errors¶
11.5.1. IP monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
ipw |
Error |
5 |
Ping was failed by timeout. IP=%s... |
The ping command failed due to timeout. |
The system may be heavily loaded, memory or OS resources may not be sufficient. Check them. |
ipw |
Error |
31 |
Ping cannot reach. (ret=%1) IP=%2... |
The packet by the ping command did not reach. |
Check if you can ping the IP address. If you fail, check the status of the device that has the IP address or the network interface. |
ipw |
Warning |
102 |
Ping was failed. (ret=%1) IP=%2... |
The ping command failed. |
Memory or OS resources may not be sufficient. Check them. |
ipw |
Warning |
106
108 to 121
|
Internal error. (status=%1) |
An error other than the errors mentioned above has 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. |
11.5.2. Disk monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
diskw |
Error |
12 |
Ioctl was failed. (err=%1) Device=%2 |
Failed to control the device. |
Check the disk to be monitored is properly connected, powered on, or does not have any problem. |
diskw |
Error |
14 |
|
|
Check if there is a directory whose name is similar to the file name, the disk to be monitored is properly connected, powered on, or does not have any problem.
Memory or OS resources may not be sufficient. Check them.
|
diskw |
Error |
16 |
Read was failed. (err=%1) Device=%2 |
Failed to read from the device. |
Check the disk to be monitored is properly connected, powered on, or does not have any problem.
Memory or OS resources may not be sufficient. Check them.
|
diskw |
Error |
18 |
Write was failed. (err=%1) File=%2 |
Writing to the file failed. |
Check the disk to be monitored is properly connected, powered on, or does not have any problem.
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 failed. |
Check the disk to be monitored is properly connected, powered on, or does not have any problem. |
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 system may be heavily loaded, memory or OS resources may not be sufficient. Check them. |
diskw |
Error |
57 |
Fdatasync was failed by timeout. Device=%1 |
fdatasync failed. |
Check if the disk to be monitored is properly connected, powered on, or does not have any other problems.
The system may be heavily loaded, memory or OS resources may not be sufficient. Check them.
|
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 |
|
|
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 |
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 by using the Cluster WebUI. |
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. |
11.5.3. PID monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
pidw |
Error |
1 |
Process does not exist. (pid=%1) |
The process does not exist. |
The process to be monitored disappeared for some reason. |
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) |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.4. User mode monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
userw |
Error |
1 |
Initialize error. (%1) |
An error was detected while initializing the process. |
Check if the driver depended on by the User mode monitor resources exist, or the rpm is installed. The driver or rpm differ depending on the monitor method. |
11.5.5. Custom monitor resource¶
Module Type |
Type |
Return value |
Message |
Description |
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 resource 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 |
Warning |
110 |
Returned warning value (%d). |
The synchronous type script returned a warning value. |
Check the cause of the warning value returned by the script. |
genw |
Error |
others |
Internal error. (status=%d) |
Another internal error occurred. |
- |
11.5.6. Multi target monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
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. |
- |
11.5.7. Mirror disk monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
mdw |
Error |
1 |
The Mirror Agent has not started. |
The Mirror Agent is not activated. |
Check the Mirror Agent is active. |
mdw |
Error |
2 |
Invalid option or parameter. |
The parameter is invalid. |
Check the cluster configuration data is correct. |
mdw |
Error |
4 |
Failed to obtain the cluster configuration information. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
mdw |
Error |
5 |
The configuration information of the mirror disk monitor resource is invalid.(%s) |
The configuration data of the mirror disk monitor resource is incorrect. |
Check if the cluster configuration data is correct. |
mdw |
Error |
30 |
Internal error |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
mdw |
Error |
51 |
Failed to obtain the remote server status. |
Failed to get the other server status. |
Check if the Mirror Agent is activated on the remote server.
Check mirror disk connection status. Check if the IP address in the cluster configuration data is correct.
|
mdw |
Error |
52 |
The mirror driver of the remote server is not working. |
The remote server cannot be connected because it is stopped, or the mirror driver on the remote server has a problem. |
Restart the remote server.
This is not an issue if the remote server is intentionally disconnected like being stopped.
|
mdw |
Error |
53 |
The mirror driver of the local server is not working. |
The mirror driver on the local server has a problem. |
Restart the local server. |
mdw |
Error |
54 |
Both local and remote drivers are not working. |
The mirror drivers on the local and remote servers have a problem. |
After cluster shutdown, restart the both servers. |
mdw |
Error |
58 |
Local mirror disk is unknown or not constructed.(%1) |
The mirror disk status is unknown on the local server, or the initial mirror construction is not performed yet. |
You have to perform the initial mirror construction. |
mdw |
Error |
63 |
Local mirror disk is abnormal. (%1) |
The mirror disk has a problem on the local server. |
The local server does not have the latest data. The mirror recovery needs to be performed. |
mdw |
Error |
64 |
Remote mirror disk is abnormal.(%1) |
Mirror disk is abnormal on the remote server. |
The remote server does not have the latest data. The mirror recovery needs to be performed. |
mdw |
Error |
65 |
Both local and remote mirror disks are abnormal.(%1) |
The mirror drivers on the local and remote servers have a problem. |
The forcible mirror recovery needs to be performed. |
mdw |
Error |
66 |
The mirror disk resource was activated on both servers.(%1) |
Mirror disk resources have been activated on both servers. |
When activation of mirror disk resource is detected on both servers, the servers shut down automatically. Restart the servers.
See the description for the module type rc and event ID 92 in "Messages reported by syslog, alert, mail, SNMP trap, and Message Topic" and "Recovery from network partitioning" in "The system maintenance information" in the "Maintenance Guide" for details.
|
mdw |
Error |
99 |
monitor was timeout |
Response to the mirror disk monitor resource has timed out.
If this error has occurred in the mirror disk monitor resource, there may be a delay in communication between the mirror agents or in the disk I/O with the cluster partition.
|
Increase the transmission timeout setting for communication between mirror agents.
Also, if the timeout setting for the mirror disk monitor resource is smaller than the transmission timeout setting for communication between the mirror agents, adjust the settings so that the former is larger than the latter.
|
mdw |
Warning |
100 |
The mirror recovery is in progress. (%1) |
Mirror recovery is in progress. |
Wait until mirror recovery is successfully completed. |
11.5.8. Mirror disk connect monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
mdnw |
Error |
1 |
The Mirror Agent has not started. |
The Mirror Agent is not activated. |
Check the Mirror Agent is active. |
mdnw |
Error |
2 |
Invalid option or parameter. |
The parameter is invalid |
Check the cluster configuration data is correct. |
mdnw |
Error |
4 |
Failed to obtain the cluster configuration information. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
mdnw |
Error |
5 |
The configuration information of the mirror disk monitor resource is invalid.(%s) |
The configuration data of the mirror disk connect monitor resource is incorrect. |
Check the cluster configuration data is correct. |
mdnw |
Error |
30 |
Internal error[status=%1] |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
mdnw |
Error |
31 |
The network is disconnected. |
The mirror disk connection is not connected. |
Check the mirror disk connection status. |
mdnw |
Warning |
101 |
One of the mirror disk connection is disconnected. |
Among the multiple mirror disk connections that exist, some were disconnected. |
Check the mirror disk connection starts. |
11.5.9. 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. |
11.5.10. 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. |
11.5.11. Process resource monitor resources¶
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. |
11.5.12. Hybrid disk monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
hdw |
Error |
1 |
The Mirror Agent has not started. |
The Mirror Agent is not activated. |
Check the Mirror Agent is active. |
hdw |
Error |
2 |
Invalid option or parameter. |
The parameter is invalid. |
Check the cluster configuration data is correct. |
hdw |
Error |
4 |
Failed to obtain the cluster configuration information. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
hdw |
Error |
5 |
The configuration information of the hybrid disk monitor resource is invalid.(%s) |
The configuration data of the mirror disk monitor resource is incorrect. |
Check if the cluster configuration data is correct. |
hdw |
Error |
13 |
Both hybrid disks are pending. |
Mirror status of both servers is pending. |
Confirm the mirror status. Execute full mirror recovery, forced recovery or resource activation. |
hdw |
Error |
15 |
Local hybrid disk is pending. Remote hybrid disk status is unknown. |
Status of hybrid disk of other server cannot be acquired. Local server is pending. It cannot be specified which server has the latest data. |
Check the inter connect. When it is confirmed that the local server has the latest data, activate the resource in the local server. When it is confirmed that the other server has the latest data, start the other server and activate the resource in the server. |
hdw |
Error |
30 |
Internal error |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
hdw |
Error |
51 |
Failed to obtain the remote server status. |
Failed to get the other server status. |
Check if the Mirror Agent is activated on the remote server.
Check mirror disk connection status. Check if the IP address in the cluster configuration data is correct.
|
hdw |
Error |
52 |
The mirror driver of the remote server is not working. |
The remote server cannot be connected because it is stopped, or the mirror driver on the remote server has a problem. |
Restart the remote server.
This is not an issue if the remote server is intentionally disconnected like being stopped.
|
hdw |
Error |
53 |
The mirror driver of the local server is not working. |
The mirror driver on the local server has a problem. |
Restart the local server. |
hdw |
Error |
54 |
Both local and remote drivers are not working. |
The mirror drivers on the local and remote servers have a problem. |
After cluster shutdown, restart the both servers. |
hdw |
Error |
58 |
Local hybrid disk is unknown or not constructed.(%1) |
The hybrid disk status is unknown on the local server, or the initial mirror construction is not performed yet. |
You have to perform the initial mirror construction. |
hdw |
Error |
63 |
Local hybrid disk is abnormal.(%1) |
The hybrid disk has a problem on the local server. |
The local server does not have the latest data. The mirror recovery needs to be performed. |
hdw |
Error |
64 |
Remote hybrid disk is abnormal.(%1) |
Hybrid disk is abnormal on the remote server. |
The remote server does not have the latest data. The mirror recovery needs to be performed. |
hdw |
Error |
65 |
Both local and remote hybrid disks are abnormal.(%1) |
The hybrid drivers on the local and remote servers have a problem. |
The forcible mirror recovery needs to be performed. |
hdw |
Error |
66 |
The hybrid disk resource was activated on both servers.(%1) |
Hybrid disk resources have been activated on both servers. |
When activation of mirror disk resource is detected on both servers, the servers shut down automatically. Restart the servers.
See the description for the module type rc and event ID 92 in "Messages reported by syslog, alert, mail, SNMP trap, and Message Topic" and "Recovery from network partitioning" in "The system maintenance information"in the "Maintenance Guide" for details.
|
hdw |
Error |
99 |
monitor was timeout |
Response to the hybrid disk monitor resource has timed out.
If this error has occurred in the hybrid disk monitor resource, there may be a delay in communication between the mirror agents or in the disk I/O with the cluster partition.
|
Increase the transmission timeout setting for communication between mirror agents.
Also, if the timeout setting for the hybrid disk monitor resource is smaller than the transmission timeout setting for communication between the mirror agents, adjust the settings so that the former is larger than the latter.
|
hdw |
Warning |
100 |
The mirror recovery is in progress. (%1) |
Mirror recovery is in progress. |
Wait until mirror recovery is successfully completed. |
11.5.13. Hybrid disk connect monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
hdnw |
Error |
1 |
The Mirror Agent has not started. |
The Mirror Agent is not activated. |
Check the Mirror Agent is active. |
hdnw |
Error |
2 |
Invalid option or parameter. |
The parameter is invalid |
Check the cluster configuration data is correct. |
hdnw |
Error |
4 |
Failed to obtain the cluster configuration information. |
Failed to obtain the cluster configuration data. |
Check the cluster configuration data exists. |
hdnw |
Error |
5 |
The configuration information of the hybrid disk monitor resource is invalid.(%s) |
The configuration data of the mirror disk connect monitor resource is incorrect. |
Check the cluster configuration data is correct. |
hdnw |
Error |
30 |
Internal error[status=%1] |
An error other than the errors mentioned above has occurred. |
Memory or OS resources may not be sufficient. Check them. |
hdnw |
Error |
31 |
The network is disconnected. |
The mirror disk connection is not connected. |
Check the mirror disk connection status. |
hdnw |
Warning |
101 |
One of the hybrid disk connection is disconnected. |
The mirror disk connection is not connected. |
Check the mirror disk connection status. |
11.5.14. NIC link up/down monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
miiw |
Error |
20 |
NIC %1 link was down. |
NIC link failed. |
Check that the LAN cable is connected properly |
miiw |
Warning |
110 |
Get IP Address information error. (err=%1) |
Failed to acquire the socket address of IPv4 or IPv6 address family. |
Check that the kernel configuration supports TCP/IP networking (IPv4 or IPv6). |
miiw |
Warning |
111 |
Socket creation was failed. (err=%1) |
Failed to create a socket. |
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 the network driver supports the control request of %3.
See "4. Monitor resource details" of this guide.
|
miiw |
Warning |
113 |
MII was not supported or no such device. Device=%1 |
Either MII is not supported by NIC or the monitoring target does not exist. |
See "4. Monitor resource details" of this guide.
Check the network interface name using a command such as ifconfig if the monitoring target does not exist.
|
miiw |
Warning |
189 |
Internal error. (status=%d) |
Other internal error has occurred. |
- |
miiw |
Warning |
190 |
Option was invalid. |
The option is invalid. |
Check the cluster configuration information on the Cluster WebUI. |
miiw |
Warning |
190 |
Config was invalid. (err=%1) %2 |
The configuration information is invalid |
Check the cluster configuration information on the Cluster WebUI. |
11.5.15. ARP monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
arpw |
Warning |
102 |
Not found IP address. |
Could not find the IP address. |
Check the status of a resource to be monitored. |
arpw |
Warning |
103 |
Socket creation error. |
An error occurred in creating a socket. |
Memory or OS resources may not be sufficient. Check them. |
arpw |
Warning |
104 |
Socket I/O error. |
A failure occurred in control request to the network driver. |
- |
arpw |
Warning |
105 |
Packet send error. |
Failed to send ARP packet. |
Check if packets can be sent from the IP address using such as the ping command. |
arpw |
Warning |
180 |
Memory allocate error. |
Failed to allocate the internal memory. |
Memory or OS resources may not be sufficient. Check them. |
arpw |
Warning |
182 |
Timeout. |
Timeout has occurred in monitoring. |
- |
arpw |
Warning |
190 |
Initialize error. |
A failure was detected during initialization. |
Memory or OS resources may not be sufficient. Check them. |
11.5.16. Virtual IP monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
vipw |
Warning |
102 |
Invalid interface. (err=%1) |
Interface name of NIC is invalid. |
Check the cluster configuration information using the Cluster WebUI. Or check the interface name of NIC exists. |
vipw |
Warning |
103 |
Get IP Address information error. (err=%1) |
Failed to acquire the socket address of IPv4 or IPv6 address family. |
Check that the kernel configuration supports TCP/IP networking (IPv4 or IPv6). |
vipw |
Warning |
104 |
Socket creation error. (err=%1) |
Failed to create a socket. |
Memory or OS resources may not be sufficient. Check them. |
vipw |
Warning |
105 |
Socket option error. (err=%1) |
Failed to set the socket option. |
Memory or OS resources may not be sufficient. Check them. |
vipw |
Warning |
106 |
Socket bind error. (err=%1) |
Failed to bind a socket with the IP address from which a socket is sent. |
Check the cluster configuration information using the Cluster WebUI. Or check the interface name of NIC exists. |
vipw |
Warning |
107 |
Socket I/O error. (err=%1) |
Failed in control request to network driver. |
Memory or OS resources may not be sufficient. Check them. |
vipw |
Warning |
108 |
Packet send error. (err=%1) |
Failed to send RIP packet. |
Check if packet can be sent from the IP address using such as the ping command. |
vipw |
Warning |
180 |
Memory allocation error. (err=%1) |
Failed to allocate internal memory. |
Memory or OS resources may not be sufficient. Check them. |
vipw |
Warning |
182 |
Timeout. |
Timeout occurred in monitoring. |
- |
vipw |
Warning |
189 |
Internal error. (status=%1) |
Other internal error occurred. |
- |
vipw |
Warning |
190 |
Initialize error. |
A failure was detected during initialization. |
Memory or OS resources may not be sufficient. Check them. |
11.5.17. 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. |
- |
11.5.18. Dynamic DNS monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
ddnsw |
Error |
8 |
Ping can not reach virtual host(%1). |
There was no ping response from the virtual host (%1). |
Check the DNS server status. |
ddnsw |
Warning |
102 |
open() failed.(err = %1) |
Opening the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddnsw |
Warning |
103 |
write() failed.(err = %1) |
Writing to the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddnsw |
Warning |
104 |
close() failed.(err = %1) |
Closing the internally used file failed. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddnsw |
Warning |
105 |
nsupdate command has failed. |
Executing the nsupdate command failed. |
Analyze the error by referring to the command return value. |
ddnsw |
Warning |
106 |
Ping can not reach the DNS server(%1). |
There was no ping response from the DNS server (%1). |
Check the DNS server status. |
ddnsw |
Warning |
107 |
nslookup command has failed. |
Executing the nslookup command failed. |
Check the DNS server status. |
ddnsw |
Warning |
180 |
Memory allocation error.(err=%1) |
An internal memory allocation error occurred. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddnsw |
Warning |
182 |
Time out. |
Monitoring timed out. |
The OS might be heavily loaded. Check whether this is so. |
ddnsw |
Warning |
190 |
Initialize error. |
An error was detected during initialization. |
There might not be enough memory space or OS resources. Check whether this is so. |
ddnsw |
Warning |
Other |
Internal error.(status=%d) |
A different internal error occurred. |
There might not be enough memory space or OS resources. Check whether this is so. |
11.5.19. 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. |
11.5.20. Floating IP monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
fipw |
Error |
4 |
IP address does not exist. |
The IP address does not exist. |
NIC may have been disabled.
Check if the FIP address exists with the ifconfig command or the ip command.
|
fipw |
Error |
5 |
Adapter Index is different. |
The adapter index is different. |
NIC may have been disabled.
Check if the FIP address exists with the ifconfig command or the ip command.
|
fipw |
Error |
9 |
Detected NIC Link Down. |
Link Down of NIC was detected. |
Check if the LAN cable is connected properly. |
fipw |
Warning |
106 |
Failed to get IP address table. |
Failed to get the IP address list. |
Memory or OS resources may not be sufficient. Check them. |
fipw |
Warning |
107 |
Failed to get NIC interface name. |
Failed to get the NIC interface name. |
Memory or OS resources may not be sufficient. Check them. |
fipw |
Warning |
108 |
Failed to get NIC status. |
Failed to get the NIC status. |
Check if the NIC device is supported by the device I/O controller. |
fipw |
Warning |
110 |
Timeout occurred. |
A timeout occurred. |
Check the load status of the server and remove the load. |
fipw |
Warning |
189 |
Internal error occurred. (status=%d) |
An internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
fipw |
Warning |
190 |
User is not superuser. |
The user does not have the root user right. |
The user who executed the operation may not have the root user right. Or, memory or OS resources may not be sufficient. Check them. |
fipw |
Warning |
190 |
Parameter is invalid. |
The parameter is invalid. |
Check if the cluster configuration data is correct. |
fipw |
Warning |
190 |
Failed to get the value from cluster configuration date. |
Failed to get the value from cluster configuration data. |
Check if the cluster configuration data is correct. |
11.5.21. AWS elastic ip monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awseipw |
Error |
5 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awseipw |
Error |
6 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awseipw |
Error |
7 |
The EIP address does not exist. (EIP ALLOCATION ID=%1) |
The EIP address %1 does not exist. |
The EIP may have been detached. Check it. |
awseipw |
Warning |
105 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awseipw |
Warning |
106 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awseipw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Check if Python is installed correctly.
Check if AWS CLI is installed correctly.
Memory or OS resources may not be sufficient. Check them.
|
11.5.22. AWS virtual ip monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awsvipw |
Error |
50 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsvipw |
Error |
51 |
The AWS CLI command is not found. |
The AWS CLI command is not found. |
Check if AWS CLI is installed correctly. |
awsvipw |
Error |
52 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of AWS virtual ip monitor resources. |
awsvipw |
Error |
53 |
Failed to obtain the virtual IP address. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of AWS virtual ip monitor resources and AWS virtual ip resource. |
awsvipw |
Error |
54 |
Failed to obtain the VPC ID. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of AWS virtual ip monitor resources and AWS virtual ip resource. |
awsvipw |
Error |
55 |
Failed to obtain the ENI ID. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of AWS virtual ip monitor resources and AWS virtual ip resource. |
awsvipw |
Error |
56 |
The routing for VIP %1 was changed. |
The routing for VIP %1 was changed. |
The VIP routing may have been changed.
Check the Route Tables of the VPC.
|
awsvipw |
Error |
57 |
The VIP address %1 does not exist. |
The VIP address %1 does not exist. |
NIC may have been disabled.
Check if the VIP address exists with the ip command.
|
awsvipw |
Warning |
150 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
11.5.23. AWS secondary ip monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awssipw |
Error |
50 |
The AWS CLI command is not found. |
The AWS CLI command is not found. |
Check if AWS CLI is installed correctly. |
awssipw |
Error |
51 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of AWS secondary ip monitor resources. |
awssipw |
Error |
52 |
Failed to obtain the secondary IP address. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of AWS secondary ip monitor resources and AWS secondary ip resource. |
awssipw |
Error |
53 |
Failed to obtain the ENI ID. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of AWS secondary ip monitor resources and AWS secondary ip resource. |
awssipw |
Error |
54 |
Failed to process checking the secondary IP address on the AWS side. |
Failed to process checking the secondary IP address on the AWS side. |
Check the settings of AWS secondary ip monitor resources and AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
awssipw |
Error |
55 |
Failed to process checking the secondary IP address on the OS side. |
Failed to process checking the secondary IP address on the OS side. |
Check the settings of AWS secondary ip monitor resources and AWS secondary ip resource.
Memory or OS resources may not be sufficient. Check them.
|
awssipw |
Warning |
150 |
Failed to process checking the secondary IP address on the AWS side. |
Failed to process checking the secondary IP address on the AWS side. |
Check the settings of AWS secondary ip monitor resources and AWS secondary ip resource.
Check if the settings in the AWS CLI file are correct.
|
11.5.24. AWS AZ monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awsazw |
Error |
4 |
Failed to monitor the availability zone %1 |
Failed to monitor the availability zone %1. |
The availability zone to which the server belongs may have a problem. Check it. |
awsazw |
Error |
5 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsazw |
Error |
5 |
Invalid availability zone: [%1] |
The specified availability zone %1 does not exist. |
Check if the settings of the availability zone are correct. |
awsazw |
Error |
6 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awsazw |
Warning |
105 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsazw |
Warning |
105 |
Invalid availability zone: [%1] |
The specified availability zone %1 does not exist. |
Check if the settings of the availability zone are correct. |
awsazw |
Warning |
106 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awsazw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Check if Python is installed correctly.
Check if AWS CLI is installed correctly.
Memory or OS resources may not be sufficient. Check them.
|
11.5.25. AWS DNS monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
awsdnsw |
Error |
5 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsdnsw |
Error |
6 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awsdnsw |
Error |
7 |
The resource record set in Amazon Route 53 does not exist. |
Resource record set does not exist in Amazon Route 53. |
The record set to be monitored might be deleted. Check the registration status of the resource record set of Amazon Route 53. |
awsdnsw |
Error |
8 |
IP address different from the setting is registered in the resource record set of Amazon Route 53. |
A different IP address from the setting value is registered in the resource record set of Amazon Route 53 |
Confirm that the IP address registered in the resource record set to be monitored is correct. |
awsdnsw |
Error |
9 |
Failed to resolve domain name. |
Failed to check the name resolution of resource record set. |
The name resolution failed. Check whether or not an error occurs in the setting of the resolver or the network
If the resource record set name uses the escape, the name resolution will fail. Therefore, set Check Name Resolution of the monitor resource to off.
|
awsdnsw |
Error |
10 |
IP address which is resolved domain name from the DNS resolver is different from the setting. |
The IP address of name resolution result is different from the setting value. |
Confirm that the setting of DNS resolver is correct and that an unintended entry does not exist in the hosts file. |
awsdnsw |
Warning |
105 |
Failed in the AWS CLI command. |
Failed in the AWS CLI command. |
Check if the settings in the AWS CLI file are correct. |
awsdnsw |
Warning |
106 |
Timeout occurred. |
Timeout occurred. |
Check the load status of the server and remove the load. |
awsdnsw |
Warning |
189 |
Internal error. (status=%1) |
An internal error occurred. |
Confirm that Python is installed properly.
Confirm that AWS CLI is installed properly.
Memory or OS resources may not be sufficient. Check them.
|
11.5.26. Azure probe port monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
azureppw |
Error |
4 |
Probe port %1 is closed. |
Probe port is closed. |
Probe port is closed.
Please confirm the setting of a network of a server.
|
azureppw |
Error |
5 |
Timeout of waiting probe port %1 occurred. |
Timeout of waiting probe port occurred. |
A probe from a load balancer of Azure couldn't be received in the timeout of waiting probe port.
Please confirm or whether a network is connected with whether an error doesn't occur by a network adapter right.
|
azureppw |
Warning |
105 |
Timeout of waiting probe port %1 occurred. |
Timeout of waiting probe port occurred. |
A probe from a load balancer of Azure couldn't be received in the timeout of waiting probe port.
Please confirm or whether a network is connected with whether an error doesn't occur by a network adapter right.
|
azureppw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.27. Azure load balance monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
azurelbw |
Error |
4 |
On server %1, probe port %2 is opened. |
On server, probe port is opened. |
A probe port is opening by a standby server.
Please make sure that the probe port won't be opened by a standby server.
|
azurelbw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.28. Azure DNS monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
azurednsw |
Error |
11 |
Query to the DNS server failed. |
For DNS server of Microsoft Azure, a query for the name resolution failed. |
Confirm that EXPRESSCLUSTER server can communicate with the DNS server of Microsoft Azure.
From the DNS zone of Microsoft Azure portal, confirm that DNS record set and record set are registered correctly.
|
azurednsw |
Error |
12 |
IP address different from the setting is registered in the record set of the Azure DNS zone. |
The record set of DNS server might be deleted or rewritten from outside. |
For DNS zone of Microsoft Azure portal, check the record set. |
azurednsw |
Warning |
189 |
Internal error. |
An internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.29. Google Cloud virtual IP monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
gcvipw |
Error |
4 |
Port %1 is closed. |
Port %1 is closed. |
The port specified for Port Number is closed.
Check the network settings of the server.
|
gcvipw |
Error |
5 |
Timeout of waiting port %1 occurred. |
Health check timeout occurred. |
The health check could not be received from the load balancer within Health check timeout.
Check if there is an error with the network adopter or the network is properly connected.
Or, extend Health check timeout.
|
gcvipw |
Error |
6 |
Monitoring port %1 failed. |
Monitoring port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
gcvipw |
Error |
7 |
Monitoring port %1 is frozen. |
Monitoring port %1 is frozen. |
Memory or OS resources may not be sufficient. Check them. |
gcvipw |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
gcvipw |
Warning |
105 |
Timeout of waiting port %1 occurred. |
Health check timeout occurred. |
The health check could not be received from the load balancer within Health check timeout.
Check if there is an error with the network adopter or the network is properly connected.
Or, extend Health check timeout.
|
gcvipw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. Check them. |
11.5.30. Google Cloud load balance monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
gclbw |
Error |
4 |
On server %1, port %2 is opened. |
On server %1, port %2 is opened. |
The port specified for Port Number on the standby server is opened.
Make sure that the port will not be opened on the standby server.
|
gclbw |
Error |
5 |
Monitoring port %1 failed. |
Monitoring port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
gclbw |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
gclbw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.31. Google Cloud DNS monitor resources¶
Module Type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
gcdnsw |
Error |
50 |
Failed to obtain the setting value. |
Failed to obtain the setting value. |
Check the settings of Google Cloud DNS monitor resource. |
gcdnsw |
Error |
51 |
Failed to obtain the zone name. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource. |
gcdnsw |
Error |
52 |
Failed to obtain the DNS name. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource. |
gcdnsw |
Error |
53 |
Failed to obtain the record type. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource. |
gcdnsw |
Error |
54 |
Failed to obtain the TTL. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource. |
gcdnsw |
Error |
55 |
Failed to obtain the IP address. |
Failed to obtain the setting value of the resource to be monitored at activation. |
Check the settings of Google Cloud DNS monitor resource and Google Cloud DNS resource. |
gcdnsw |
Error |
56 |
Failed to obtain the record set. |
Failed to obtain the record set of Cloud DNS. |
Check the setting value of Google Cloud DNS monitor resource and the privilege of the account which permitted Cloud SDK. |
gcdnsw |
Error |
57 |
No record set to be monitored. (%1) |
A monitoring failure was detected. %1:Cause of error |
- |
11.5.32. Oracle Cloud virtual IP monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
ocvipw |
Error |
4 |
Port %1 is closed. |
Port %1 is closed. |
The port specified for Port Number is closed.
Check the network settings of the server.
|
ocvipw |
Error |
5 |
Timeout of waiting port %1 occurred. |
Health check timeout occurred. |
The health check could not be received from the load balancer within Health check timeout.
Check if there is an error with the network adopter or the network is properly connected.
Or, extend Health check timeout.
|
ocvipw |
Error |
6 |
Monitoring port %1 failed. |
Monitoring port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
ocvipw |
Error |
7 |
Monitoring port %1 is frozen. |
Monitoring port %1 is frozen. |
Memory or OS resources may not be sufficient. Check them. |
ocvipw |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
ocvipw |
Warning |
105 |
Timeout of waiting port %1 occurred. |
Health check timeout occurred. |
The health check could not be received from the load balancer within Health check timeout.
Check if there is an error with the network adopter or the network is properly connected.
Or, extend Health check timeout.
|
ocvipw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.33. Oracle Cloud load balance monitor resources¶
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
oclbw |
Error |
4 |
On server %1, port %2 is opened. |
On server %1, port %2 is opened. |
The port specified for Port Number on the standby server is opened.
Make sure that the port will not be opened on the standby server.
|
oclbw |
Error |
5 |
Monitoring port %1 failed. |
Monitoring port %1 failed. |
Memory or OS resources may not be sufficient. Check them. |
oclbw |
Error |
99 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
oclbw |
Warning |
189 |
Internal error. (status=%1) |
Internal error occurred. |
Memory or OS resources may not be sufficient. Check them. |
11.5.34. Monitoring option monitor resource¶
Monitor resources of monitoring options use common messages. Module types are different for each 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 |
oracle |
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 |
WebSphere monitor resource |
wasw |
WebLogic monitor resource |
wlsw |
WebOTX monitor resource |
otxw |
Module type |
Type |
Return value |
Message |
Description |
Solution |
---|---|---|---|---|---|
(see the list above) |
Error |
5 |
Failed to connect to %1 server. [ret=%2] %3: |
Failed to connect to the monitor target. |
Check the status of the monitor target.
The actual module type is displayed in %1.
|
(see the list above) |
Error |
7 |
Failed to execute SQL statement (%1). [ret=%2] %3: |
Failed to execute SQL statement (%1).
The actual module type is displayed in %1.
|
Check the cluster configuration information using the Cluster WebUI. |
(see the list above) |
Error |
8 |
Failed to access with %1. %2: |
Failed in data access with monitor target.
The actual module type is displayed in %1.
|
Check the status of monitor target. |
(see the list above) |
Error |
9 |
Detected error in %1. %2: |
A failure occurred on monitor target.
The actual module type is displayed in %1.
|
Check the status of monitor target. |
(see the list above) |
Warning |
104 |
Detected function exception. [%1, ret=%2] %3: function name |
A failure was detected. |
Check the cluster configuration information using the Cluster WebUI.
The OS may be heavily loaded. Check it.
|
(see the list above) |
Warning |
106 |
Detected authority error. |
Failed in the user authentication. |
Check the user name, password, and access right. |
(see the list above) |
Warning |
106 |
Client authentication error. |
Client authentication error. |
Check if the private key and the client certificate are correctly set. |
(see the list above) |
Warning |
111 |
Detected timeout error. |
Communication timeout has occurred. |
OS may be heavily loaded. Check it. |
(see the list above) |
Warning |
112 |
Can not found install path. (install path=%1) |
Can not found install path. |
Check the install path. |
(see the list above) |
Warning |
113 |
Can not found library. (libpath=%1, errno=%2) |
Failed to load the library from the specified location. |
Check where the library is located. |
(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) |
An internal error was detected. |
- |
(see the list above) |
Warning |
190 |
Init error. [%1, ret=%2] |
license/XML/log/share memory module initialization error Failed in Dynamic Library Load. |
OS may be heavily loaded. Check the status of OS. |
(see the list above) |
Warning |
190 |
Get config information error. [ret=%1] |
Failed to acquire the setting information. |
Check the cluster configuration information using the Cluster WebUI. |
(see the list above) |
Warning |
190 |
Invalid parameter. |
The setting information of Config file/Policy file is invalid.
Command parameter is invalid.
|
Check the cluster configuration information using the Cluster WebUI. |
(see the list above) |
Warning |
190 |
Init function error. [%1, ret=%2] |
An error was detected while initialization. |
OS may be heavily loaded. Check the status of OS. |
(see the list above) |
Warning |
190 |
User was not superuser. |
A user does not have the right as root user. |
The user who executed the operation may not have a root user right. Or, memory or OS resources may not be sufficient. Check them. |
(see the list above) |
Warning |
190 |
The license is not registered. |
The license is not registered. |
Check if the valid license is registered. |
(see the list above) |
Warning |
190 |
The registration license overlaps. |
The registered license already exists. |
Check if the valid license is registered. |
(see the list above) |
Warning |
190 |
The license is invalid. |
The license is invalid. |
Check if the valid license is registered. |
(see the list above) |
Warning |
190 |
The license of trial expired by %1. %2: Validity_date |
The license of trial is expired.
The actual validity date is displayed in Validity_date.
|
- |
(see the list above) |
Warning |
190 |
The license of trial effective from %1. %2:
Validity_date
|
The trial license has not become effective yet.
The actual validity date is displayed in Validity_date.
|
- |
(see the list above) |
Warning |
190 |
Not supported algorithm(%1). |
The algorithm is not supported.
%1 represents the algorithm.
|
- |
11.6. JVM monitor resource log output messages¶
The following messages belong to the JVM operation log files that are specific to the JVM monitor resources.
The file is created in the following location:
JVM operation log: <EXPRESSCLUSTER_install_path>/log/ha/jra/jragent*.log (* indicates a number starting at 0.)
11.6.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. retry = %2$s / %3$s. |
The Java VM to be monitored could not be connected.
%1$s: Name of the Java VM to be monitored
%2$s: Number of times the connection consecutively failed
%3$s: Retry Count
* retry = %2$s / %3$s is not shown after the former value exceeds the latter.
|
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, error_count = %7$s / %8$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
%7$s: Number of times the threshold was consecutively exceeded
%8$s: Error Threshold
* error_count = %7$s / %8$s is not shown after the former value exceeds the latter.
|
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, error_count = %7$s / %8$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
%7$s: Number of times the threshold was consecutively exceeded
%8$s: Error Threshold
* error_count = %7$s / %8$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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%, error_count = %6$s / %7$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
%6$s: Number of times the threshold was consecutively exceeded
%7$s: Error Threshold
* error_count = %6$s / %7$s is not shown after the former value exceeds the latter.
|
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). error_count = %3$s / %4$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
%3$s: Number of times the threshold was consecutively exceeded
%4$s: Error Threshold
* error_count = %3$s / %4$s is not shown after the former value exceeds the latter.
|
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, error_count = %3$s / %4$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
%3$s: Number of times the threshold was consecutively exceeded
%4$s: Error Threshold
* error_count = %3$s / %4$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
Review the Java application that runs on the WebLogic Server to be monitored. |
%1$s: Throughput count is too much. count = %2$s, error_count = %3$s / %4$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
%3$s: Number of times the threshold was consecutively exceeded
%4$s: Error Threshold
* error_count = %3$s / %4$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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, error_count = %5$s / %6$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
%5$s: Number of times the threshold was consecutively exceeded
%6$s: Error Threshold
* error_count = %5$s / %6$s is not shown after the former value exceeds the latter.
|
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, error_count = %7$s / %8$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
%7$s: Number of times the threshold was consecutively exceeded
%8$s: Error Threshold
* error_count = %7$s / %8$s is not shown after the former value exceeds the latter.
|
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, error_count = %7$s / %8$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
%7$s: Number of times the threshold was consecutively exceeded
%8$s: Error Threshold
* error_count = %7$s / %8$s is not shown after the former value exceeds the latter.
|
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.
|
11.7. Details on checking cluster configuration data¶
11.7.1. Cluster Properties¶
Check item |
ID |
Message |
Action |
---|---|---|---|
Ping check on the NP resolution resource |
1001 |
Failed. |
Check if the ping (ping6) command is available. |
1002 |
Ping could not reach to %1. |
Check if an IP address reachable with a ping is set. |
|
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.(Mirror) tab |
1021 |
Failed. |
Check if the sysctl command is available. |
1022 |
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. |
11.7.2. Group Resources¶
Check item |
ID |
Message |
Action |
---|---|---|---|
Ping check on fip |
2001 |
Failed. |
Check if the ping (ping6) command is available. |
2002 |
%1 is used already. |
Specify an unused IP address in the LAN to which the cluster servers belong. |
|
Ping check on vip |
2011 |
Failed. |
Check if the ping (ping6) command is available. |
2012 |
%1 is used already. |
Specify an unused IP address in the LAN to which the cluster servers belong. |
|
Partition presence check for disk |
2021 |
%1 does not exist. |
Specify an existing device name. |
Partition presence check for md |
2031 |
%1 does not exist. |
Specify an existing device name. |
Partition presence check for hd |
2041 |
%1 does not exist. |
Specify an existing device name. |
Cluster partition size check for md |
2111 |
In %1, the size is less than 1 GB. |
Set the disk size to 1 GB or more. |
Cluster partition size check for hd |
2121 |
In %1, the size is less than 1 GB. |
Set the disk size to 1 GB or more. |
/etc/fstab entry check for disk |
2051 |
%1 is entered into /etc/fstab. |
Do not enter the target device name into /etc/fstab. |
/etc/fstab entry check for md |
2061 |
%1 is entered into /etc/fstab. |
Do not enter the target device name into /etc/fstab. |
/etc/fstab entry check for hd |
2071 |
%1 is entered into /etc/fstab. |
Do not enter the target device name into /etc/fstab. |
Port number check for md |
2131 |
Failed. |
Check if the sysctl command is available. |
2132 |
The port number %1 is within the range of automatically assigned port numbers. |
Specify a port number which is not automatically assigned. |
|
Port number check for hd |
2141 |
Failed. |
Check if the sysctl command is available. |
2142 |
The port number %1 is within the range of automatically assigned port numbers. |
Specify a port number which is not automatically assigned. |
|
Port number check for azurepp |
2081 |
Failed. |
Check if the sysctl command is available. |
2082 |
The port number %1 is within the range of automatically assigned port numbers. |
Specify a port number which is not automatically assigned. |
|
File system check for disk |
2091 |
Failed. |
Check if the parted or lsblk command is available. |
2092 |
File system is in invalid status. |
Check if an appropriate file system is configured. |
|
File system check for md |
2151 |
Failed. |
Check if the parted or lsblk command is available. |
2152 |
File system is in invalid status. |
Check if an appropriate file system is configured. |
|
File system check for hd |
2161 |
Failed. |
Check if the parted or lsblk command is available. |
2162 |
File system is in invalid status. |
Check if an appropriate file system is configured. |
|
Mount option check for md |
2171 |
The mount option is specified as "data=writeback". |
You cannot specify "data=writeback" for the mount option. |
Mount option check for hd |
2181 |
The mount option is specified as "data=writeback". |
You cannot specify "data=writeback" for the mount option. |
VG presence check for volmgr |
2101 |
Failed. |
Check if the vgs command is available. |
2102 |
%1 does not exist. |
Specify an existing volume group name. |
11.7.3. Heartbeat Resources¶
Check item |
ID |
Message |
Action |
---|---|---|---|
Ping check on khb |
4001 |
Failed. |
Check if the ping (ping6) command is available. |
4002 |
Ping could not reach to %1. |
Check if an IP address reachable with a ping is set. |
|
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. |
|
Device presence check for diskhb |
4021 |
%1 does not exist. |
Specify an existing device name. |
/etc/fstab entry check for diskhb |
4031 |
%1 is entered into /etc/fstab. |
Do not enter the target device name into /etc/fstab. |
11.7.4. Others¶
Check item |
ID |
Message |
Action |
---|---|---|---|
AWSCLI command execution check |
5001 |
AWSCLI command execution failed. |
Check if the AWSCLI execution environment is correctly configured. |
OS start time check |
5011 |
OS start time has not been adjusted.
Please adjust the OS start time.
|
Adjust the OS start time. For the procedure, see "Installation and Configuration Guide" - "Adjustment of time for EXPRESSCLUSTER services to start up (Required)". |
Checking if SELinux is disabled |
5021 |
Failed. |
Check if the getenforce command is available. |
5022 |
SELinux has not been disabled. |
For the procedure, see "Installation and Configuration Guide" - "SELinux settings (Required)".
If you have enabled SELinux through the procedure described in the above document, ignore this error message.
|
|
Checking if Secure Boot is disabled |
5061 |
Failed. |
Check if the mokutil or bootctl command is available. |
5062 |
Secure Boot is not disabled. |
Disable Secure Boot. |
|
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. |
11.7.5. 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.
|