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

Module type

Event type

Event ID

Message

Description

Solution

pm

Info

1

Starting the cluster daemon...

The EXPRESSCLUSTER daemon has started normally.

-

pm

Info

2

Shutting down the cluster daemon...

The EXPRESSCLUSTER daemon is stopping.

-

pm

Info

3

Shutdown monitoring is started...

Shutdown monitoring has started.

-

pm

Error

10

The cluster daemon has already started.

The EXPRESSCLUSTER daemon has already started.

Check the status of the EXPRESSCLUSTER daemon.

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.

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.

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.

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.

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.

pm

Warn

16

The recovery action is configured to change from an OS stop to an OS restart.

Checking the configuration of cluster properties.

-

pm

Error

20

Process %1 was terminated abnormally.

Process %1 was terminated abnormally.

Check the following possible causes: memory shortage or OS resource insufficiency.

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.

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.

pm

Info

23

The system will be stopped.

The system will be stopped.

-

pm

Info

24

The cluster daemon will be stopped.

The EXPRESSCLUSTER daemon will be stopped.

-

pm

Info

25

The system will be rebooted.

The system will be rebooted.

-

pm

Info

26

Process %1 will be restarted.

Process %1 will be restarted.

-

pm

Info

30

Received a request to stop the system from %1.

A system stop request was received from %1.

-

pm

Info

31

Received a request to stop the cluster daemon from %1.

An EXPRESSCLUSTER daemon stop request was received from %1.

-

pm

Info

32

Received a request to reboot the system from %1.

A system reboot request was received from %1.

-

pm

Info

33

Received a request to restart the cluster daemon from %1.

An EXPRESSCLUSTER daemon reboot request was received from %1.

-

pm

Info

34

Received a request to resume the cluster daemon from %1.

A cluster resume request was received from %1.

-

pm

Info

35

Received a request to suspend the cluster daemon from %1.

A cluster suspend request was received from %1.

-

pm

Info

36

Received a request to panic by sysrq from %1.

A panic request by sysrq was received from %1.

-

pm

Info

37

Received a request to reset by keepalive driver from %1.

A reset request by the keepalive driver was received from %1.

-

pm

Info

38

Received a request to panic by keepalive driver from %1.

A panic request by the keepalive driver was received from %1.

-

pm

Info

39

Received a request to reset by BMC from %1.

A reset request by BMC was received from %1.

-

pm

Info

40

Received a request to power down by BMC from %1.

A power down request by BMC was received from %1.

-

pm

Info

41

Received a request to power cycle by BMC from %1.

A power cycle request by BMC was received from %1.

-

pm

Info

42

Received a request to send NMI by BMC from %1.

An NMI send request by BMC was received from %1.

-

pm

Info

43

Received a request to send IO Fencing by ACPI driver from %1.

An IO Fencing send request by ACPI driver was received from %1.

-

pm

Info

44

Received a request to emergently stop the system from %1.

An emergent system stop request was received from %1.

-

pm

Info

45

Received a request to emergently reboot the system from %1.

An emergent system reboot request was received from %1.

-

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.

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.

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.

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.

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.

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.

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.

pm

Error

73

An attempt to send IO Fencing by ACPI driver from %1 failed.

An attempt was made to perform I/O fencing with the ACPI driver from %1, but failed.

Confirm whether the ACPI driver for EXPRESSCLUSTER linkage is available.

pm

Info

100

The system will be panic by sysrq.

The system will be panicked by sysrq.

-

pm

Info

101

The system will be reset by ka.

The system will be reset by the keep alive driver.

-

pm

Info

102

The system will be panic by ka.

The system will be panicked by the keep alive driver.

-

pm

Info

103

The system will be reset by bmc.

The system will be reset by BMC.

-

pm

Info

104

The system will be off by bmc.

The system will be turned OFF by BMC.

-

pm

Info

105

The system will be cycle by bmc.

The system will be turned OFF and then back ON by BMC.

-

pm

Info

106

The system will be nmi by bmc.

The system will be NMI-transmitted by BMC.

-

pm

Info

107

The system will be iofencing.

The system will be subject to I/O fencing.

-

nm

Info

1

Server %1 has started.

Server %1 has started.

-

nm

Info

2

Server %1 has been stopped.

Server %1 has stopped.

-

nm

Info

3

Resource %1 of server %2 has started.

Resource %1 of server %2 has started.

-

nm

Info

4

Resource %1 of server %2 has stopped.

Resource %1 of server %2 has stopped.

-

nm

Info

5

Waiting for all servers to start.

Waiting for all servers to start has started.

-

nm

Info

6

All servers have started.

All servers have started.

-

nm

Info

7

Timeout occurred during the wait for startup of all servers.

Waiting for all servers to start has timed out.

-

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.

nm

Info

9

Waiting for startup of all servers has been canceled.

Waiting for servers to start has been canceled.

-

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.

nm

Warn

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.

nm

Error

20

Process %1 was terminated abnormally.

Process %1 was terminated abnormally.

Check the following possible causes: memory shortage or OS resource insufficiency.

nm

Info

21

The system will be stopped.

The system will be stopped.

-

nm

Info

22

The cluster daemon will be stopped.

The EXPRESSCLUSTER daemon will be stopped.

-

nm

Info

23

The system will be rebooted.

The system will be rebooted.

-

nm

Info

24

Process %1 will be restarted.

Process %1 will be restarted.

-

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.

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.

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.

nm

Error

33

Cluster service will be stopped. (reason:%1)

The cluster service will be stopped. (Reason: %1)

Remove the factor indicated in "reason".

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.

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.

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.

-

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.

nm

Error

38

The resource %1 of the server %2 is unknown.

Resource %1 of server %2 is unknown.

Check the cluster configuration data.

nm

Info

39

The server %1 canceled the pending failover.

Server %1 canceled the failover.

-

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.

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.

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.

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.

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.

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.

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.

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.

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.

nm

Info

81

Recovered from internal communication error with server %1.

Internal communication with server %1 has been recovered from the abnormal status.

-

rc

Info

10

Activating group %1 has started.

Activating group %1 has started.

-

rc

Info

11

Activating group %1 has completed.

Activating group %1 has been completed.

-

rc

Error

12

Activating group %1 has failed.

Activating group %1 has failed.

Take appropriate action according to the group resource message.

rc

Info

15

Waiting for group %1 to start has started.

Waiting for the group to start has started.

-

rc

Info

16

Waiting for group %1 to start has been completed.

Waiting for the group to start has been normally completed.

-

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.

rc

Warn

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.

-

rc

Info

20

Stopping group %1 has started.

Stopping group %1 has started.

-

rc

Info

21

Stopping group %1 has completed.

Stopping group %1 has been completed.

-

rc

Error

22

Stopping group %1 has failed.

Stopping group %1 has failed.

Take appropriate action according to the group resource message.

rc

Warn

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.

rc

Info

25

Waiting for group %1 to stop has started.

Waiting for the group to stop has started.

-

rc

Info

26

Waiting for group %1 to stop has been completed.

Waiting for the dependent group to stop has been normally completed.

-

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.

rc

Warn

28

Waiting for group %1 to stop has timed out. However, group stop continues.

Stop waiting has timed out. However, group stop continues.

-

rc

Info

30

Activating %1 resource has started.

Activating resource %1 has started.

-

rc

Info

31

Activating %1 resource has completed.

Activating resource %1 has been completed.

-

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.

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.

-

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.

-

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.

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.

-

rc

Info

40

Stopping %1 resource has started.

Stopping resource %1 has started.

-

rc

Info

41

Stopping %1 resource has completed.

Stopping resource %1 has been completed.

-

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.

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.

-

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.

-

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.

rc

Info

50

Moving group %1 has started.

Moving group %1 has started.

-

rc

Info

51

Moving group %1 has completed.

Moving group %1 has been completed.

-

rc

Error

52

Moving group %1 has failed.

Moving group %1 has failed.

Take appropriate action according to the group resource message.

rc

Info

55

Migrating group %1 has started.

Migrating group %1 has started.

-

rc

Info

56

Migrating group %1 has completed.

Migrating group %1 has been completed.

-

rc

Error

57

Migrating group %1 has failed.

Migrating group %1 has failed.

Take appropriate action according to the group resource message.

rc

Warn

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.

rc

Info

60

Failover group %1 has started.

Failover of group %1 has started.

-

rc

Info

61

Failover group %1 has completed.

Failover of group %1 has been completed.

-

rc

Error

62

Failover group %1 has failed.

Failover of group %1 has failed.

Take appropriate action according to the group resource message.

rc

Warn

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.

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)

-

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.

rc

Warn

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.

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.

-

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.

-

rc

Warn

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.

rc

Info

70

Restarting group %1 has started.

Reactivating group %1 has started.

-

rc

Info

71

Restarting group %1 has completed.

Reactivating group %1 has been completed.

-

rc

Error

72

Restarting group %1 has failed.

Reactivating group %1 has failed.

Take appropriate action according to the group resource message.

rc

Info

74

Failback group %1 has started.

Failback group %1 has started.

-

rc

Info

75

Failback group %1 has completed.

Failback group %1 has been completed.

-

rc

Error

76

Failback group %1 has failed.

Failback group %1 has failed.

Take appropriate action according to the group resource message.

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.

rc

Info

80

Restarting resource %1 has started.

Reactivating resource %1 has started.

-

rc

Info

81

Restarting resource %1 has completed.

Reactivating resource %1 has been completed.

-

rc

Error

82

Restarting resource %1 has failed.

Reactivating resource %1 has failed.

Take appropriate action according to the group resource message.

rc

Info

83

Starting a single resource %1.

Single resource %1 is started.

-

rc

Info

84

A single resource %1 has been started.

Single resource %1 has been started.

-

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.

rc

Warn

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.

rc

Info

87

Stopping a single resource %1.

Single resource %1 is stopped.

-

rc

Info

88

A single resource %1 has been stopped.

Single resource %1 has been stopped.

-

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.

rc

Info

90

All the servers in the cluster were shut down.

The cluster has been stopped.

-

rc

Info

91

The server was shut down.

The server has been stopped.

-

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".

rc

Warn

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.

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.

-

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.

-

rc

Info

162

Script %1 in resource %2 started

Script (%1) of resource (%2) has started.

-

rc

Info

163

Script %1 in resource %2 completed

Script (%1) of resource (%2) has been completed.

-

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.

rc

Error

181

Failed to execute script %1 in resource %2.(%3)

Script (%1) of resource (%2) has failed.

Same as above.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

rc

Info

247

IO Fencing by ACPI driver is requested since activating resource(%1) failed.

I/O fencing with the ACPI driver was requested due to an activation failure in resource %1.

Take appropriate action according to the group resource message.

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.

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.

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.

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 ipmitoo command can be used.

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.

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.

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.

rc

Error

267

An attempt to IO Fencing by ACPI driver due to failure of resource(%1) activation failed.

An attempt was made to perform I/O fencing by the ACPI driver due to an activation failure in resource %1, but failed.

Confirm whether the ACPI driver for EXPRESSCLUSTER linkage is available.

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.

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.

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.

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.

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.

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.

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.

rc

Info

287

IO Fencing by ACPI driver is requested since deactivating resource(%1) failed.

I/O fencing is executed by using the ACPI driver due to an activation failure in resource %1.

-

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.

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.

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.

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.

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.

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.

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 ipmitoo command can be used.

rc

Error

307

An attempt to IO Fencing by ACPI driver due to failure of resource(%1) deactivation failed.

An attempt was made to perform I/O fencing by the ACPI driver due to an activation error in resource %1, but failed.

Confirm whether the ACPI driver for EXPRESSCLUSTER linkage is available.

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.

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.

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.

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.

-

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.

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.

rc

Info

403

The request for forcibly stopping the server will be retried.

The request for forcibly stopping the server will be retried.

-

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.

rc

Info

405

The check of forcibly stopping the server will be retried.

The check of forcibly stopping the server will be retried.

-

rc

Warn

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.

rc

Warn

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.

rc

Warn

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.

rc

Warn

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.

-

rc

Warn

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.

-

rc

Warn

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.

-

rc

Warn

503

A mismatch in the group %1 status occurs between the servers.

Generation of group status mismatch

Restart the group or reboot the cluster.

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.

-

rc

Warn

510

Cluster operation is disabled.

Cluster operation is disabled.

-

rc

Warn

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.

-

rc

Warn

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.

-

rc

Warn

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.

-

rc

Info

514

Cluster operation is set disabled.

Cluster operation is disabled.

-

rc

Info

515

Cluster operation is set enabled.

Cluster operation is enabled.

-

rc

Warn

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.

-

rm

Info

1

Monitoring %1 has started.

Monitoring %1 has started.

-

rm

Info

2

Monitoring %1 has stopped.

Monitoring %1 has stopped.

-

rm

Info

3

%1 is not monitored by this server.

%1 is not monitored by this server.

-

rm

Warn

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.)

rm

Warn

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.

rm

Warn

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.

rm

Error

7

Failed to start monitoring %1.

Starting of monitoring %1 failed.

Check the following possible causes: memory shortage or OS resource insufficiency.

rm

Error

8

Failed to stop monitoring %1.

Stopping of monitoring %1 failed.

Check the following possible causes: memory shortage or OS resource insufficiency.

rm

Error

9

Detected an error in monitoring %1. (%2 : %3)

An error was detected in monitoring %1.

See "Detailed info of monitor resource errors".

If a monitoring timeout is detected, the following message is set in ().

(99 : Monitor was timeout.)

If Dummy Failure is enabled, the following message is set in (). No action is needed in the latter case.

(201 : Monitor failed for failure verification.)

If no response is returned from a monitor resource for a certain period of time, the following message is set in ().

(202: couldn't receive reply from monitor resource in time.)

rm

Info

10

%1 is not monitored.

%1 is not monitored.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

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.

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.

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.

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.

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.

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.

rm / mm

Warn

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.

-

rm / mm

Info

26

%1 status changed from error to normal.

Monitoring %1 has changed from error to normal.

-

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.

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.

rm

Info

29

Monitoring %1 was suspended.

Monitoring %1 has temporarily stopped.

-

rm

Info

30

Monitoring %1 was resumed.

Monitoring %1 has restarted.

-

rm

Info

31

All monitors were suspended.

All monitoring processes have temporarily stopped.

-

rm

Info

32

All monitors were resumed.

All monitoring processes have restarted.

-

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.

-

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.

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.

-

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.

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.

-

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.

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.

-

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.

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.

-

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.

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.

-

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.

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.

-

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.

rm

Info

49

%1 status changed from warning to normal.

%1 status changed from warning to normal.

-

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.

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.

rm

Warn

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.

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.

-

rm

Warn

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.

rm

Warn

72

%1 could not Monitoring.

%1 could not perform monitoring.

Check the following possible causes: memory shortage or OS resource insufficiency.

Script before %1 upon failure in monitor resource %2 started.

Script before %1 of monitor resource %2 has started.

-

rm / mm

Info

82

Script before %1 upon failure in monitor resource %2 completed.

Script before %1 of monitor resource %2 has been completed.

-

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.

rm

Warn

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.

-

rm

Warn

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.

-

rm

Warn

121

The virtual machine (%1) has been started by an external operation.

The virtual machine managed by resource %1 was started by external operation.

-

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.

-

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.

-

rm

Warn

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.

-

rm

Info

140

Process %1 has started.

Process %1 has started.

-

rm

Warn

141

Process %1 has restarted.

Process %1 has restarted.

-

rm

Warn

142

Process %1 does not exist.

Process %1 does not exist.

-

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.

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.

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.

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.

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.

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.

-

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.

rm

Info

180

Dummy Failure of monitor resource %1 is enabled.

Dummy Failure of monitor resource %1 is enabled.

-

rm

Info

181

Dummy Failure of monitor resource %1 is disabled.

Dummy Failure of monitor resource %1 is disabled.

-

rm

Info

182

Dummy Failure of all monitor will be enabled.

Dummy Failure of all monitor will be enabled.

-

rm

Info

183

Dummy Failure of all monitor will be disabled.

Dummy Failure of all monitor will be disabled.

-

rm

Warn

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.

rm

Warn

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.

rm

Info

190

Recovery action caused by monitor resource error is disabled.

Recovery action caused by monitor resource error is disabled.

-

rm

Info

191

Recovery action caused by monitor resource error is enabled.

Recovery action caused by monitor resource error is enabled.

-

rm

Warn

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.

-

rm

Warn

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.

-

rm

Warn

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.

-

rm / mm

Info

210

IO Fencing by ACPI driver has been required because an error was detected in monitoring %1.

I/O fencing by the ACPI driver is necessary because an error was detected in monitoring %1.

-

rm / mm

Error

211

Attempted to IO Fencing by ACPI driver due to the error detected in monitoring %1, but failed.

An attempt was made to perform I/O fencing by the ACPI driver in response to the error detected in monitoring %1, but failed.

Confirm whether the ACPI driver for EXPRESSCLUSTER linkage can be used in the environment.

rm

Warn

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.

-

rm

Warn

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.

-

mm

Info

51

The trial license is effective until %1. (%2)

The trial license is effective until %1.

-

mm

Error

53

The license is not registered. (%1)

The license is not registered.

Purchase the license and then register it.

mm

Error

54

The trial license has expired in %1. (%2)

The validity term of the trial license has expired.

Register a valid license.

mm

Error

55

The registered license is invalid. (%1)

The registered license is invalid.

Register a valid license.

mm

Error

56

The registered license is unknown. (%1)

The registered license is unknown.

Register a valid license.

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.

mm

Info

901

Message monitor has been started.

Message monitor (external linkage monitor module) has been started.

-

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.

mm

Warn

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.

-

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.

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.

mm

Error

907

Failed to execute action. (%1)

Executing recovery action has failed.

Check the following possible causes: memory shortage or OS resource insufficiency.

mm

Info

908

The system will be stopped.

The OS will be shut down.

-

mm

Info

909

The cluster daemon will be stopped.

The cluster will be stopped.

-

mm

Info

910

The system will be rebooted.

The OS will be rebooted.

-

mm

Info

911

Message monitor will be restarted.

Message monitor (external linkage monitor module) will be restarted.

-

mm

Info

912

Received a message by SNMP Trap from external. (%1 : %2)

Received a message by SNMP Trap from external.

-

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 .

-

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]..

-

mm

Warn

915

Received a Recoverble 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 Guide1.

-

mm

Warn

916

Received a Recoverble 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 Guide1.

-

mm

Warn

917

Received a Recoverble Trap.(Performance degradation & Predict) (msg : %1)

A Recoverble Trap was received. (A predictive failure was detected.) The message contains information (%1). For information about %1 (failure region), see the Device Maintenance Guide1.

-

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.

-

trnsv

Info

10

There was a notification (%1) from external (IP=%2).

A notification (%1) from %2 was accepted.

-

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.

-

trnsv

Info

21

Recovery action (%1) of monitoring %2 has been completed.

Recovery action (%1) of monitor resource %2 has been successful.

-

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.

trnsv

Info

30

Action (%1) has been completed.

Action (%1) has been successful.

-

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.

trnsv

Info

40

Script before action of monitoring %1 has been executed.

Script before the recovery action of monitor resource (%1) has been executed.

-

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.

-

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.

trnsv

Error

50

The system will be shutdown because cluster resume was failed.

The system will be shutdown because cluster resume was failed.

-

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.

trnsv

Info

83

Starting a dynamic adding resource %1.

Resource %1 has been dynamically added.

-

trnsv

Info

84

A dynamic adding resource %1 has been started.

Resource %1 succeeded in being dynamically added.

-

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.

trnsv

Warn

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.

trnsv

Info

87

Deleting a resource %1.

Resource %1 has been deleted.

-

trnsv

Info

88

Deleting a resource %1 has been stopped.

Resource %1 succeeded in being deleted.

-

trnsv

Error

89

Failed to Delete a resource %1.

Resource %1 failed to be deleted.

Take appropriate action according to the group resource message.

lanhb

Warn

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.

lanhb

Warn

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

Warn

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

Warn

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.

lankhb

Warn

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.

diskhb

Error

11

Device(%1) of resource(%2) is not a block device.

No device exists.

Check the cluster configuration data.

diskhb

Error

12

Raw device(%1) of resource(%2) does not exist.

No device exists.

Check the cluster configuration data.

diskhb

Error

13

Binding device(%1) of resource(%2) to raw device(%3) failed.

No device exists.

Check the cluster configuration data.

diskhb

Error

14

Raw device(%1) of resource(%2) has already been bound to other device.

Raw device %1 of resource %2 has already been bound to another device.

Set the raw device that is not in use.

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.

diskhb

Info

20

Resource %1 recovered from initialization error.

Resource %1 was recovered from an initialization error.

-

diskhb

Warn

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.

diskhb

Warn

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

Warn

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.

bmchb

Error

10

Failed to initialize to BMC.

BMC initialization failed.

Check whether the hardware can use the BMC linkage function.

bmchb

Warn

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.

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.

  • mdagnt

  • webmgr

  • webalert

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.

monp

Info

3

Monitor target process %1 will be restarted.

Monitored process %1 will be restarted.

-

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.

-

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.

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.

-

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.

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.

-

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.

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.

Failed to open I/O port.

The port could not be opened. Check the cluster configuration data.

The local server doesn't have the latest data.

The local server does not have the latest data. Mirror recovery is needed.

Communication to the remote server failed.

Communication with a remote server failed. Check the connection status of the mirror disk connection.

The remote server is active.

The remote server has already been activated. Check the status of the mirror disk resource.

The local server is already active.

The local server has already been activated. Check the status of the mirror disk resource.

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.

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.

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.

Replicator license is invalid or expired.

Register a valid license.

md / hd

Info

2

fsck to %1 has started.

fsck of %1 has started.

-

md / hd

Info

3

fsck to %1 was successful.

fsck of %1 has been successful.

-

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.

The mirror disk has already been deactivated.

The mirror disk has already been deactivated. Check the status of the mirror disk resource.

Unmount operation failed.

The unmount operation failed. Check whether the file system of the mirror disk resource is busy.

md / hd

Info

16

Initial mirror recovery of %1 has started.

Preparation for initial mirror construction of %1 has started.

-

md / hd

Info

18

Initial mirror recovery of %1 was successful.

Preparation for initial mirror construction of %1 has been successful.

-

md / hd

Warn

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.

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.

md / hd

Warn

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.

md / hd

Info

39

%1 of %2 with %3 option has started.

Command %1 of device %2 with option %3 specified has started.

-

md / hd

Info

44

Mirror recovery of %1 was canceled.

Mirror recovery of %1 has been canceled.

-

md / hd

Info

45

Failed to cancel mirror recovery of %1.

Mirror recovery of %1 could not be canceled.

Stop the mirror recovery again.

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".)

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".)

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.

Failed to open I/O port.

The port could not be opened. Check the cluster configuration data.

The local server doesn't have the latest data.

The local server does not have the latest data. Mirror recovery is needed.

Communication to the remote server failed.

Communication with a remote server failed. Check the connection status of the mirror disk connection.

The remote server is active.

The remote server has already been activated. Check the status of the mirror disk resource.

The local server is already active.

The local server has already been activated. Check the status of the mirror disk resource.

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.

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.

One of other inter-connection works well except mirror disk connections.

Check that the LAN for mirror connection is normal.

Replicator license is invalid or expired.

Register a valid license.

mdadmn

Info

2

fsck to %1 has started.

fsck of %1 has started.

-

mdadmn

Info

3

fsck to %1 was successful.

fsck of %1 has been successful.

-

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.

The mirror disk has already been deactivated.

The mirror disk has already been deactivated. Check the status of the mirror disk resource.

Unmount operation failed.

The unmount operation failed. Check whether the file system of the mirror disk resource is busy.

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.

The recovery is in progress.

Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute.

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.

Cannot determine the mirror recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

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.

Replicator license is invalid or expired.

Register a valid license.

mdadmn

Info

6

Mirror recovery of %1 was completed successfully.

Mirror recovery of %1 has been successful.

-

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.

-

mdadmn

Info

8

The number of Replicator Option licenses is %1. (%2)

The number of Replicator Option licenses is %1.

-

mdadmn

Info

9

The trial license is effective until %1. (%2)

The trial license is effective until %1.

-

mdadmn

Error

10

The registered license is unknown. (%1)

The registered license is unknown.

Register a valid license.

mdadmn

Error

11

The registered license is invalid. (%1)

The registered license is invalid.

Register a valid license.

mdadmn

Error

12

The license is not registered. (%1)

The license is not registered.

Purchase the license and then register it.

mdadmn

Warn

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.

mdadmn

Error

14

The trial license expired in %1. (%2)

The validity term of the trial license has expired.

Register a valid license.

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.

mdadmn

Info

16

Initial mirror recovery of %1 has started.

Initial mirror construction of %1 has started.

-

mdadmn

Info

17

Mirror recovery of %s has started.(%d bytes)

Mirror recovery of %1 has started.

-

mdadmn

Info

18

Initial mirror recovery of %1 was successful.

Initial mirror construction of %1 has been successful.

-

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.

The recovery is in progress.

Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute.

The destination server is active.

The resource has already been activated on the copy destination server. Check the status of the mirror disk resource.

Cannot determine the mirror recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

mdadmn

Info

20

Initial mirror recovery was not executed following the configuration. (Device:%1)

Initial mirror construction was not performed according to the setting.

-

mdadmn

Info

21

Mirror partition mkfs was executed. (Device:%1)

mkfs of the mirror partition has been executed.

-

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.

-

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.

mdadmn

Warn

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.

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.

-

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.

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.

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.

mdadmn

Error

32

Forced activation of the mirror failed. %1 (Device:%2)

Forced activation of %2 failed. The following messages may be output output to %1:

Take appropriate action according to the message displayed in %1.

Failed to open I/O port.

The port could not be opened. Check the cluster configuration data.

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.

Replicator license is invalid or expired.

Register a valid license.

mdadmn

Error

33

Forced recovery of the mirror failed. %1(Device:%2)

Forced recovery of %2 failed. The following message may be output output to %1:

Register a valid license.

Register a valid license.

mdadmn

Info

34

Isolating the mirror %1 completed successfully.

Mirror resource %1 has been successfully isolated.

-

mdadmn

Info

35

Mirror force active of %1 was completed successfully.

Forced activation of %1 has been successful.

-

mdadmn

Info

36

Forced recovery of the mirror %1 completed successfully.

Forced recovery of %1 has been successful.

-

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.

mdadmn

Warn

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.

mdadmn

Info

39

%1 of %2 with %3 option has started.

Command %1 of device %2 with option %3 specified has started.

-

mdadmn

Info

40

Failed to write to cluster partition of hybrid disk(%1).

Writing to cluster partition of %1 has failed.

Restart the server.

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.

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.

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.

mdadmn

Info

44

Mirror recovery of %1 was canceled.

Mirror recovery of %1 has been canceled.

-

mdadmn

Info

45

Failed to cancel mirror recovery of %1.

Mirror recovery of %1 could not be canceled.

Stop the mirror recovery again.

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".)

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".)

mdadmn

Error

54

Update of encryption key of %1 is required.

The update of encryption key of %1 is required.

Update the encryption key.

mdagent

Info

1

The Mirror Agent has started successfully.

The mirror agent has been started normally.

-

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.

Agent is running.

The agent has already been started.

Command clpmdinit is running.

The clpmdini command has already been started. Check the end of the command and then restart it.

IP address in the config file is invalid.

Check the cluster configuration data.

Server name in the config file is invalid.

Check the cluster configuration data.

There is an error in config file.

Check the cluster configuration data.

Failed to initialize socket server.

Check the following possible causes: memory shortage or OS resource insufficiency.

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.

mdagent

Info

3

The Mirror Agent has stopped successfully.

The mirror agent has been stopped normally.

-

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.

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.

Use the Cluster WebUI or an EXPRESSCLUSTER command to stop the mirror agent or server.

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.

If an unmount timeout occurred, set a larger value for unmount timeout.

If the user mounted the mirror partition at multiple mount points, unmount the additional mount point before deactivating the mirror.

It is also probable that mirror recovery was in progress.

If mirror recovery is in progress, stop the mirror agent or server after mirror recovery is completed or after stopping mirror recovery.

mdagent

Warn

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.

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.

Failed to open I/O port.

The port could not be opened. Check the cluster configuration data.

The local server doesn't have the latest data.

The local server does not have the latest data. Mirror recovery is needed.

Communication to the remote server failed.

Communication with a remote server failed. Check the connection status of the mirror disk connection.

The remote server is active.

The remote server has already been activated. Check the status of the mirror disk resource.

The local server is already active.

The local server has already been activated. Check the status of the mirror disk resource.

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.

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.

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.

Replicator license is invalid or expired.

Register a valid license.

mdctrl / hdctrl

Info

2

fsck of %1 has started.

fsck of %1 has started.

-

mdctrl / hdctrl

Info

3

fsck of %1 was successful.

fsck of %1 has been successful.

-

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.

The mirror disk has already been deactivated.

The mirror disk has already been deactivated. Check the status of the mirror disk resource.

Unmount operation failed.

The unmount operation failed. Check whether the file system of the mirror disk resource is busy.

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.

The recovery is in progress.

Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute.

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.

Can not judge the recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

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.

Replicator license is invalid or expired.

Register a valid license.

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.

-

mdctrl / hdctrl

Info

16

Initial mirror recovery of %1 has started.

Initial mirror construction of %1 has started.

-

mdctrl / hdctrl

Info

17

Mirror recovery of %1 has started.

Mirror recovery of %1 has started.

-

mdctrl / hdctrl

Info

18

Initial mirror recovery of %1 was successful.

Initial mirror construction of %1 has been successful.

-

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.

The recovery is in progress.

Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute.

The destination server is active.

The resource has already been activated on the copy destination server. Check the status of the mirror disk resource.

Cannot judge the recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

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.

-

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.

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.

Failed to open I/O port.

The port could not be opened. Check the cluster configuration data.

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.

Replicator license is invalid or expired.

Register a valid license.

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:

Replicator license is invalid or expired.

Register a valid license.

mdctrl / hdctrl

Info

34

Isolating the mirror %1 completed successfully.

Mirror resource %1 has been successfully isolated.

-

mdctrl / hdctrl

Info

35

Mirror force active of %1 was completed successfully.

Forced activation of %1 has been successful.

-

mdctrl / hdctrl

Info

36

Forced recovery of the mirror %1 completed successfully.

Forced recovery of %1 has been successful.

-

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.

mdctrl / hdctrl

Warn

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.

mdctrl / hdctrl

Info

39

%1 of %2 with %3 option has started.

Command %1 of device %2 with option %3 specified has started.

-

mdctrl / hdctrl

Info

44

Mirror recovery of %1 was canceled.

Mirror recovery of %1 has been canceled.

-

mdctrl / hdctrl

Info

45

Failed to cancel mirror recovery of %1.

Mirror recovery of %1 could not be canceled.

Stop the mirror recovery again.

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".)

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")

mdctrl / hdctrl

Info

50

Extension of mirror disk %1 was successful.

The data partition extension of mirror disk resource %1 succeeded.

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.

mdctrl / hdctrl

Info

52

Update of encryption key of %1 was successful.

The encryption key of %1 was successfully updated.

-

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.

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.

mdinit / hdinit

Info

21

Mirror partition mkfs was executed. (Device:%1)

mkfs of the mirror partition has been executed.

-

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.

-

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.

The recovery is in progress.

An attempt was made to start auto mirror recovery, but mirror recovery was already started.

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.

Cannot determine the mirror recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

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.

Replicator license is invalid or expired.

Register a valid license.

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.

-

mdw / hdw

Info

16

Initial mirror recovery of %1 has started.

Initial mirror construction of %1 has started.

-

mdw / hdw

Info

17

Mirror recovery of %1 has started.

Mirror recovery of %1 has started.

-

mdw / hdw

Info

18

Initial mirror recovery of %1 was successful.

Initial mirror construction of %1 has been successful.

-

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.

The recovery is in progress.

Mirror recovery is in progress. Wait for the completion of the mirror recovery and then reexecute.

The destination server is active.

The resource has already been activated on the copy destination server. Check the status of the mirror disk resource.

Cannot determine the mirror recovery direction.

The mirror recovery direction cannot be determined. Perform forced mirror recovery.

The source server is abnormal.

The copy source server is abnormal. Check the status of the mirror agent.

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.

-

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.

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.

fip

Info

11

IP address %1 will be forcefully activated.

IP address %1 is forcibly activated.

-

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.

vip

Info

11

IP address %1 will be forcefully activated.

IP address %1 is forcibly activated.

-

disk

Info

10

%1 of %2 has started.

Command %1 of device %2 has started.

-

disk

Info

11

%1 of %2 was successful.

Command %1 of device %2 has been successful.

-

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.

disk

Warn

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.

disk

Info

14

%1 of %2 with %3 option has started.

Command %1 of device %2 with option %3 specified has started.

-

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.

disk

Warn

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.

disk

Warn

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.

cl

Info

1

There was a request to start %1 from the %2.

A request to start %1 was issued from %2.

-

cl

Info

2

There was a request to stop %1 from the %2.

A request to stop %1 was issued from %2.

-

cl

Info

3

There was a request to suspend %1 from the %2.

A request to suspend %1 was issued from %2.

-

cl

Info

4

There was a request to resume %s from the %s.

A request to resume %1 was issued from %2.

-

cl

Error

11

A request to start %1 failed(%2).

A request to start %1 has failed.

Check the status of the cluster.

cl

Error

12

A request to stop %1 failed(%2).

A request to stop %1 has failed.

Check the status of the cluster.

cl

Error

13

A request to suspend %1 failed(%2).

A request to suspend %1 has failed.

Check the status of the cluster.

cl

Error

14

A request to resume %1 failed(%2).

A request to resume %1 has failed.

Check the status of the cluster.

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.

cl

Error

16

A request to start %1 failed on some servers(%2).

Starting %1 failed on some servers.

Check the status of %1.

cl

Error

17

A request to stop %1 failed on some servers(%2).

Stopping %1 failed on some servers.

Check the status of %1.

cl

Warn

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.

cl

Warn

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.

cl

Warn

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.

mail

Error

1

The license is not registered. (%1)

Purchase the license and then register it.

-

mail

Error

2

The trial license has expired in %1. (%2)

Register a valid license.

-

mail

Error

3

The registered license is invalid. (%1)

Register a valid license.

-

mail

Error

4

The registered license is unknown. (%1)

Register a valid license.

-

mail

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.

mail

Info

6

mail successed.(SMTP server: %s)

Mail report has been successful.

-

down

Info

1

There was a request to shutdown %1 from the %2.

There was a request to shut down %1 from %2.

-

down

Info

2

There was a request to reboot %1 from the %2.

There was a request to reboot %1 from %2.

-

down

Error

11

A request to shutdown %1 failed(%2).

A request to shut down %1 failed.

Check the status of the server.

down

Error

12

A request to reboot %1 failed(%2).

A request to reboot %1 failed.

Check the status of the server.

userw

Warn

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.

vipw

Warn

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.

ddnsw

Warn

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.

vmw

Warn

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.

bmcw

Warn

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 upon delay detection is %4 (tick count) which exceeds the delay warning rate %5 (%).

Check the load status of the server on which a monitoring delay was detected and then remove that load. If a monitoring timeout is likely to be detected, increase the monitoring timeout setting.

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

apisv

Info

13

There was a request to server panic from the %1(IP=%2).

A server panic request was issued from %1.

-

apisv

Info

14

There was a request to server reset from the %1(IP=%2).

A server reset request was issued from %1.

-

apisv

Info

15

There was a request to server sysrq from the %1(IP=%2).

An SYSRQ panic request was issued from %1.

-

apisv

Info

16

There was a request to KA RESET from the %1(IP=%2).

A keepalive reset request was issued from %1.

-

apisv

Info

17

There was a request to KA PANIC from the %1(IP=%2).

A keepalive panic request was issued from %1.

-

apisv

Info

18

There was a request to BMC reset from the %1(IP=%2).

A BMC reset request was issued from %1.

-

apisv

Info

19

There was a request to BMC PowerOff from the %1(IP=%2).

A BMC power-off request was issued from %1.

-

apisv

Info

20

There was a request to BMC PowerCycle from the %1(IP=%2).

A BMC power cycle request was issued from %1.

-

apisv

Info

21

There was a request to BMC NMI from the %1(IP=%2).

A BMC NMI request was issued from %1.

-

apisv

Info

22

There was a request to IO Fencing from the %1(IP=%2).

An I/O fencing request was received from %1.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

apisv

Info

39

There was a request to failover all groups from the %1(IP=%2).

A group failover request was issued from %1.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

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.

-

apisv

Error

101

A request to stop cluster was failed(0x%08x).

The cluster could not be stopped.

Check the status of the cluster.

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.

apisv

Error

103

A request to reboot cluster was failed(0x%08x).

The cluster could not be rebooted.

Check the status of the cluster.

apisv

Error

104

A request to suspend cluster was failed(0x%08x).

The cluster could not be suspended.

Check the status of the cluster.

apisv

Error

110

A request to stop server was failed(0x%08x).

The server could not be stopped.

Check the status of the server.

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.

apisv

Error

112

A request to reboot server was failed(0x%08x).

The server could not be rebooted.

Check the status of the server.

apisv

Error

113

A request to server panic was failed(0x%08x).

Server panic has failed.

Check the status of the server.

apisv

Error

114

A request to server reset was failed(0x%08x).

Server reset has failed.

Check the status of the server.

apisv

Error

115

A request to server sysrq was failed(0x%08x).

SYSRQ panic has failed.

Check the status of the server.

apisv

Error

116

A request to KA RESET was failed(0x%08x).

Keepalive reset has failed.

Check the status of the server.

apisv

Error

117

A request to KA PANIC was failed(0x%08x).

Keepalive panic has failed.

Check the status of the server.

apisv

Error

118

A request to BMC RESET was failed(0x%08x).

BMC reset has failed.

Check the status of the server.

apisv

Error

119

A request to BMC PowerOff was failed(0x%08x).

BMC power-off has failed.

Check the status of the server.

apisv

Error

120

A request to BMC PowerCycle was failed(0x%08x).

BMC power cycle has failed.

Check the status of the server.

apisv

Error

121

A request to BMC NMI was failed(0x%08x).

BMC NMI has failed.

Check the status of the server.

apisv

Error

122

A request to IO Fencing was failed(0x%08x).

I/O fencing has failed.

Check the status of the server.

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.

apisv

Error

131

A request to start all groups was failed(0x%08x).

Starting all groups has failed.

Same as above.

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.

apisv

Error

133

A request to stop all groups was failed(0x%08x).

Stopping all groups has failed.

Same as above.

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.

apisv

Error

135

A request to restart all groups was failed(0x%08x).

Restarting all groups has failed.

Same as above.

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.

apisv

Error

137

A request to move all groups was failed(0x%08x).

Moving all groups has failed.

Same as above.

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.

apisv

Error

139

A request to failover all groups was failed(0x%08x).

Failover for all groups has failed.

Same as above.

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.

apisv

Error

141

A request to migrate all groups was failed(0x%08x).

Migration of all groups has failed.

Same as above.

apisv

Error

142

A request to failover all groups was failed(0x%08x).

Failover for all groups has failed.

Same as above.

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.

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.

apisv

Error

151

A request to start all resources was failed(0x%08x).

Starting all resources has failed.

Same as above.

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.

apisv

Error

153

A request to stop all resources was failed(0x%08x).

Stopping all resources has failed.

Same as above.

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.

apisv

Error

155

A request to restart all resources was failed(0x%08x).

Restarting all resources has failed.

Same as above.

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.

apisv

Error

161

A request to resume monitor resource was failed(0x%08x).

The monitor resource could not be resumed.

Same as above.

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.

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.

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.

lamp

Error

1

The license is not registered. (%1)

The license is not registered.

Purchase the license and then register it.

lamp

Error

2

The trial license has expired in %1. (%2)

The validity term of the trial license has expired.

Register a valid license.

lamp

Error

3

The registered license is invalid. (%1)

The registered license is invalid.

Register a valid license.

lamp

Error

4

The registered license is unknown. (%1)

The registered license is unknown.

Register a valid license.

lamp

Info

5

Notice by the network warming light succeeded.

Report by the network warning light has been successful.

-

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.

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.

cfmgr

Info

1

The cluster configuration data has been uploaded by %1.

Cluster configuration data has been uploaded.

-

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.

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.

sra

Error

3

Reading a configuration file failed.

An error occurred in reading the SG file.

Check the message separately issued.

sra

Error

4

Trace log initialization failed.

The internal log file could not be initialized.

Restart the cluster, or execute the suspend and resume.

sra

Error

5

Creating a daemon process failed.

An external error has occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

sra

Error

6

Reading a service configuration file failed.

An error occurred in reading the SG file.

Check the message separately issued.

sra

Error

7

mlock() failed.

An external error has occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

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.

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.

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.

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.

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.

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.

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.

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.

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.

sra

Error

17

Internal error occurred.

A shared memory access error has occurred.

-

sra

Warn

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.

sra

Warn

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.

sra

Warn

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.

sra

Warn

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.

sra

Warn

105

realloc(3) fail. [%1].

%1:Function name

An external error has occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

sra

Warn

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.

sra

Warn

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.

sra

Warn

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.

sra

Warn

109

malloc(3) fail. [%1]

%1:Function name

An external error has occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

sra

Info

201

A script was executed. (%1)

%1:Script name

Script (%1) has been executed.

-

sra

Info

202

Running a script finished. (%1)

%1:Script name

Script has ended normally.

-

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.

-

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

sra

Warn

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.

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

-

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

-

lcns

Warn

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.

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.

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.

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.

lcns

Error

7

The registered license is unknown. (Product name:%1)

The registered license is unknown.

%1: Product name

Register a valid license.

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.

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

-

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.

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.

-

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.

-

webmgr

Warn

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.

forcestop

Info

1

Forced stop of server %1 has been requested.(%2, %3)

forced-stop requested (%1, %2, %3)

-

forcestop

Info

2

Forced stop of server %1 has completed.(%2, %3)

forced-stop completed (%1, %2, %3)

-

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.

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.

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.

forcestop

Error

6

Forced stop of server %1 failed.(%2, %3)

forced-stop failed (%1, %2, %3)

Check whether the command can be used.

Detailed information in activating and deactivating group resources

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

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.

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.

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.

NAS resources

Module Type

Type

Return value

Message

Description

Solution

nas

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.

nas

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.

nas

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.

nas

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.

nas

Error

1

Getting of config was failed.

Failed to obtain the cluster configuration data.

Check the cluster configuration data exists.

nas

Error

1

Mount point was already mounted. (%1)

The resource on the NAS server has already been mounted.

Check if the specified resource in the NAS server is unmounted.

nas

Error

1

Mount point was not mounted. (%1)

The mount point was not mounted.

The active resource may have been manually unmounted. Check its status.

nas

Error

1

Mount point was invalid. (%1)

The mount point is invalid.

Check the mount point exists.

nas

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.

nas

Error

1

Max recover retry over. (%1, retry=%2)

The number of retries made for mounting resource on the NAS server has exceeded the maximum retry count.

Check that the cluster configuration data is correct.

nas

Error

1

Command path was invalid. (%1)

The execution path is invalid.

Check the command execution path.

nas

Error

1

Command timeout. (%1, timeout=%2)

Detected an internal timeout.

The OS may be heavily loaded. Check its status.

nas

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.

nas

Error

1

Command failed. (%1(%2), errno=%3)

An error occurred while running the command.

Memory or OS resources may not be sufficient. Check them.

nas

Error

1

Internal error. (status=%1)

Other internal error has occurred.

Memory or OS resources may not be sufficient. Check them.

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.

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.

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.

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.

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

Warn

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.

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.

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.

VM resources

Module Type

Type

Return value

Message

Description

Solution

vm

Error

1 to 6, 8

Initialize error occurred.

An error was detected while initialization.

Check if the cluster configuration information is correct.

vm

Error

7

Parameter is invalid.

The parameter is invalid.

Check if the cluster configuration information is correct.

vm

Error

9 to 13

Failed to %s virtual machine %s.

Failed to control the virtual machine.

Check the status of the virtual machine.

vm

Error

22

Datastore must be setted.

The datastore name must be set for the Cluster WebUI.

Click the Details tab of VM Resources Properties in the Cluster WebUI, enter the name of data store containing the virtual machine configuration information to Data Store Name. And then click Apply the Configuration File.

vm

Error

23

VM configuration file path must be setted.

The VM configuration file path must be set for the Cluster WebUI.

Click the Details tab of VM Resources Properties in the Cluster WebUI, enter the path where the virtual machine configuration information is stored to VM Configuration File Path. And then click Apply the Configuration File.

vm

Error

Other

Internal error occurred.

Another internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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.

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.

AWS virtual ip resources

Module Type

Type

Return value

Message

Description

Solution

awsvip

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.

awsvip

Error

5

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

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.

awsvip

Error

6

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awsvip

Error

7

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

8

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

9

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

10

The VIP address %1 is already used.

The VIP address %1 is already used.

Check if the VIP address is already used.

awsvip

Error

11

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.

awsvip

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.

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.

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.

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.

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.

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.

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.

-

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.

Detailed info of monitor resource errors

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

Warn

102

Ping was failed. (ret=%1) IP=%2...

The ping command failed.

Memory or OS resources may not be sufficient. Check them.

ipw

Warn

106
108~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

Warn

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.

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

  1. Open was failed. (err=%1) File=%2

  2. Open was failed. (err=%1) Device=%2

  1. Opening the file failed.

  2. Opening the device failed.

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

Warn

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

Warn

101

  1. Open was failed by timeout. File=%1

  2. Open was failed by timeout. Device=%1

  1. Opening the file failed due to timeout.

  2. Opening the device 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

Warn

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

Warn

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

Warn

101

Bind was failed. Rawdevice=%1 Device=%2

Bind failed.

Bind failed. Check the RAW device name on the Cluster WebUI.

diskw

Warn

101

Stat was failed. (err=%1) Device=%2

Stat failed.

Stat failed. Check the device name on the Cluster WebUI.

diskw

Warn

101

Popen was failed. (err=%1)

Popen failed.

Popen failed. Memory or OS resources may not be sufficient. Check them.

diskw

Warn

101
190

Option was invalid.

The option is invalid.

Check the cluster configuration data by using the Cluster WebUI.

diskw

Warn

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

Warn

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

Warn

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

Warn

191

Ignored disk full error.

A disk full error has been ignored.

Check the usage of the device.

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

Warn

100

Resource %1 was not found.

The resource is not found.

Check the cluster configuration data by using the Cluster WebUI.

pidw

Warn

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.

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.

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

Error

others

Internal error. (status=%d)

Another internal error occurred.

-

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.

-

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

Warn

100

The mirror recovery is in progress. (%1)

Mirror recovery is in progress.

Wait until mirror recovery is successfully completed.

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

Warn

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.

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

Warn

189

Internal error occurred.

An internal error has occurred.

Execute cluster suspend and cluster resume.

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.

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.

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

Warn

100

The mirror recovery is in progress. (%1)

Mirror recovery is in progress.

Wait until mirror recovery is successfully completed.

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

Warn

101

One of the hybrid disk connection is disconnected.

The mirror disk connection is not connected.

Check the mirror disk connection status.

ARP monitor resources

Module Type

Type

Return value

Message

Description

Solution

arpw

Warn

102

Not found IP address.

Could not find the IP address.

Check the status of a resource to be monitored.

arpw

Warn

103

Socket creation error.

An error occurred in creating a socket.

Memory or OS resources may not be sufficient. Check them.

arpw

Warn

104

Socket I/O error.

A failure occurred in control request to the network driver.

-

arpw

Warn

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

Warn

180

Memory allocate error.

Failed to allocate the internal memory.

Memory or OS resources may not be sufficient. Check them.

arpw

Warn

182

Timeout.

Timeout has occurred in monitoring.

-

arpw

Warn

190

Initialize error.

A failure was detected during initialization.

Memory or OS resources may not be sufficient. Check them.

Virtual IP monitor resources

Module Type

Type

Return value

Message

Description

Solution

vipw

Warn

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

Warn

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

Warn

104

Socket creation error. (err=%1)

Failed to create a socket.

Memory or OS resources may not be sufficient. Check them.

vipw

Warn

105

Socket option error. (err=%1)

Failed to set the socket option.

Memory or OS resources may not be sufficient. Check them.

vipw

Warn

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

Warn

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

Warn

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

Warn

180

Memory allocation error. (err=%1)

Failed to allocate internal memory.

Memory or OS resources may not be sufficient. Check them.

vipw

Warn

182

Timeout.

Timeout occurred in monitoring.

-

vipw

Warn

189

Internal error. (status=%1)

Other internal error occurred.

-

vipw

Warn

190

Initialize error.

A failure was detected during initialization.

Memory or OS resources may not be sufficient. Check them.

VM monitor resources

Module Type

Type

Return value

Message

Description

Solution

vmw

Error

1

initialize error occurred.

An error was detected while initialization.

Memory or OS resources may not be sufficient. Check them.

vmw

Error

11

monitor success, virtual machine is not running.

Stop of the virtual machine was detected.

Check the status of the virtual machine.

vmw

Error

12

failed to get virtual machine status.

Failed to get the status of the virtual machine.

Check if the virtual machine exists.

vmw

Error

13

timeout occurred.

The monitoring timed out.

The OS may be highly loaded. Check it.

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

Warn

190

Option was invalid.

The option is invalid.

Check the cluster configuration information on the Cluster WebUI.

volmgrw

Warn

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

Warn

Others

Internal error. (status=%1)

Another internal error occurred.

-

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

Warn

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

Warn

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

Warn

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

Warn

105

nsupdate command has failed.

Executing the nsupdate command failed.

Analyze the error by referring to the command return value.

ddnsw

Warn

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

Warn

107

nslookup command has failed.

Executing the nslookup command failed.

Check the DNS server status.

ddnsw

Warn

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

Warn

182

Time out.

Monitoring timed out.

The OS might be heavily loaded. Check whether this is so.

ddnsw

Warn

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

Warn

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.

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

Warn

100

Monitoring timeout

Monitoring has timed out.

The OS may be highly loaded. Check that.

psw

Warn

101
190

Internal error

An internal error has occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

psw

Warn

190

Initialize error

An error has been detected during initialization.

Check the following possible causes: memory shortage or OS resource insufficiency.

BMC monitor resource

Module Type

Type

Return value

Message

Description

Solution

bmcw

Error

0

Success.

The monitoring process was successful.

bmcw

Error

1

Initialize error.

An error occurred when the monitor started.

Check the following possible causes: memory shortage, OS resource insufficiency, or failure to install the IPMI driver correctly.

bmcw

Error

32

Not supported platform. (code=%1)

The platform is not supported.

The hardware may be other than the NX7700x series.

bmcw

Error

32

BMC access denied.

The IPMI command for monitoring failed.

Check the operating status of the IPMI driver.

bmcw

Error

64

Internal error. (status=%1)

An internal error occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

bmcw

Warn

128

The registered license is invalid. (%1)

The registered license is invalid.

Register a valid license.

bmcw

Warn

129

The license is not registered. (%1)

The license is not registered.

Purchase and register a license.

bmcw

Warn

130

The trial license has expired in %.4s/%.2s/%.2s. (%1)

The trial license has expired.

Register a valid license.

bmcw

Warn

130

The trial license is valid from %.4s/%.2s/%.2s. (%1)

The current date is earlier than the valid period of the trial license.

Register a valid license.

bmcw

Warn

131

The registered license is unknown. (%1)

The registered license is unknown.

Register a valid license.

bmcw

Error

200

Timeout.

Monitoring caused a timeout.

The BMC is highly loaded or has stalled. Check the BMC.

Oracle Clusterware Synchronization Management monitor resource

Module Type

Type

Return value

Message

Description

Solution

osmw

Error

1

Initialize error.

An error occurred when the monitor started.

Check the following possible causes: memory shortage, OS resource insufficiency, or failure to install the IPMI driver correctly.

osmw

Error

1

Oracle Clusterware linkage is not enabled.

Oracle Clusterware linkage function is not enabled.

Enable the Oracle Clusterware linkage function.

osmw

Error

32

All registered Oracle processes do not exist.

A process of any watch targets doesn't exist.

Everything of a watch target process became extinct by some cause. Please check Oracle Clusterware processes.

osmw

Error

64

Internal error. (status=%1)

An internal error occurred.

Check the following possible causes: memory shortage or OS resource insufficiency.

osmw

Warn

128

The registered license is invalid. (%1)

The registered license is invalid.

Register a valid license.

osmw

Warn

129

The license is not registered. (%1)

The license is not registered.

Purchase and register a license.

osmw

Warn

130

The trial license has expired in %.4s/%.2s/%.2s. (%1)

The trial license has expired.

Register a valid license.

osmw

Warn

131

The trial license is valid from %.4s/%.2s/%.2s. (%1)

The current date is earlier than the valid period of the trial license.

Register a valid license.

osmw

Warn

132

The registered license is unknown. (%1)

The registered license is unknown.

Register a valid license.

osmw

Warn

160

Some registered Oracle processes do not exist.

A process of some watch targets doesn't exist.

Some of the watch target process became extinct by some cause. Please check Oracle Clusterware processes.

osmw

Error

200

Timeout.

Monitoring caused a timeout.

The OS may be highly loaded. Check that.

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

Warn

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

Warn

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

Warn

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

Warn

110

Timeout occurred.

A timeout occurred.

Check the load status of the server and remove the load.

fipw

Warn

189

Internal error occurred. (status=%d)

An internal error occurred.

Memory or OS resources may not be sufficient. Check them.

fipw

Warn

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

Warn

190

Parameter is invalid.

The parameter is invalid.

Check if the cluster configuration data is correct.

fipw

Warn

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.

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

Warn

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

Warn

106

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awseipw

Warn

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.

AWS virtual ip monitor resources

Module type

Type

Return value

Message

Description

Solution

awsvipw

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.

awsvipw

Error

6

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awsvipw

Error

7

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 ipconfig command.

awsvipw

Error

8

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

Warn

105

Failed in the AWS CLI command.

Failed in the AWS CLI command.

Check if the settings in the AWS CLI file are correct.

awsvipw

Warn

106

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awsvipw

Warn

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.

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

Warn

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.

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

Warn

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

Warn

105

Invalid availability zone: [%1]

The specified availability zone %1 does not exist.

Check if the settings of the availability zone are correct.

awsazw

Warn

106

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awsazw

Warn

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.

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

Warn

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

Warn

106

Timeout occurred.

Timeout occurred.

Check the load status of the server and remove the load.

awsdnsw

Warn

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.

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 probr port.
Please confirm or whether a network is connected with whether an error doesn't occur by a network adapter right.

azureppw

Warn

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 probr port.
Please confirm or whether a network is connected with whether an error doesn't occur by a network adapter right.

azureppw

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

Warn

189

Internal error.

An internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

Warn

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

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them. Check them.

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

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

-

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

Warn

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

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

Warn

189

Internal error. (status=%1)

Internal error occurred.

Memory or OS resources may not be sufficient. Check them.

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

Sybase monitor resource

sybasew

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)

Warn

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)

Warn

106

Detected authority error.

Failed in the user authentication.

Check the user name, password, and access right.

(see the list above)

Warn

111

Detected timeout error.

Communication timeout has occurred.

OS may be heavily loaded. Check it.

(see the list above)

Warn

112

Can not found install path. (install path=%1)

Can not found install path.

Check the install path.

(see the list above)

Warn

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)

Warn

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)

Warn

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)

Warn

189

Internal error. (status=%1)

An internal error was detected.

-

(see the list above)

Warn

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)

Warn

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)

Warn

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)

Warn

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)

Warn

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)

Warn

190

The license is not registered.

The license is not registered.

Check if the valid license is registered.

(see the list above)

Warn

190

The registration license overlaps.

The registered license already exists.

Check if the valid license is registered.

(see the list above)

Warn

190

The license is invalid.

The license is invalid.

Check if the valid license is registered.

(see the list above)

Warn

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)

Warn

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)

Warn

190

Not supported algorithm(%1).

The algorithm is not supported.
%1 represents the algorithm.

-

Details on checking cluster configuration data

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.

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.

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.

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.

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 the operating system startup time (Required)".

Checking if SELinux is disabled

5021

Failed.

Check if the getenforce command is available.

5022

SELinux has not been disabled.

Disable SELinux. For the procedure, see "Installation and Configuration Guide" - "SELinux settings (Required)".

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.

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.