ExpressCluster X 2.0 for Windows Reference Guide - Nec

Module
Type
Event
Type
Event
ID
rm Warning 1537
rm Warning 1571
rm Warning 1600
rm Information 1700
rm Information 1701
Section III Maintenance information
Messages Description Solution
Recovery will not be
executed since server is
suspending.
Monitor %1 was
delayed. (timeout=%2,
response time=%3,
rate=%4)
Shutdown count reached
the maximum number
(%1). Final action of
monitor %2 was ignored.
Script before final action
upon failure in %1
monitor resource started.
Script before final action
upon failure in %1
monitor resource
completed.
Script before final action
upon failure in %1
monitor resource failed.
not recovery(server
suspending)
monitor delayed
reached OS shutdown
limit
Script before final action
upon monitor resource
failure started.
Script before final action
upon monitor resource
failure completed.
Script before final action
upon monitor resource
Messages reported by event log and alert
Monitor resource is not
recovered if the server is
suspended (Network Partition
Unsolved). Check the cause
for being suspended (Network
Partition Unsolved) and
recover network partition
resources to normal status.
Check the load on the server
where monitoring delay was
detected and reduce the load.
Set longer time-out if the
monitoring time-out is
detected.
Alert
Event log
User log
807
Report Manager
setting Alive
Mail report
● ● ● ●
● ● ● ●
- ● ● ● ● ●
- ● ● ●
- ● ● ●
rm Information 1720
- ● ● ●
diskagent Information 2001 %1 service was started.
failure has failed.
Start service - ● ●
diskagent Information 2002 %1 service was stopped. Stop service
%1 service was not
- ● ●
diskagent Warning 2030
stopped successfully
due to stop time-out or
other errors of the
internal threads.
%1 service was not
started successfully
Fail to stop service
The system may not be able to
operate properly.
● ● ● ●
diskagent Error 2050
because the specified
parameter was invalid.
Confirm the cluster
configuration data.
%1 service was not
Fail to start service
Check the cluster configuration
data.
● ● ● ●
diskagent Error 2051
started because
Fail to start service
obtaining the policy data
failed. Check the data.
%1 service was not
started successfully
Check the policy file. ● ● ● ●
diskagent Error 2052
because dispatching to
service manager failed.
System may be unable
to operate correctly.
%1 service was not
started successfully
Fail to start service
The system may not be able to
operate properly.
● ● ● ●
diskagent Error 2053
because creating and
loading internal Fail to start service
resources failed. System
may be unable to
operate correctly.
System may be unable to
operate correctly.
● ● ● ●