4. 错误消息一览表¶
本章介绍EXPRESSCLUSTER X SingleServerSafe运行中显示的错误消息一览表。
本章包含以下内容。
4.1. 安装时的错误消息¶
模块类型 |
错误消息 |
对策 |
---|---|---|
setup |
Previous version of EXPRESSCLUSTER is installed. Upgrading from this version is not supported. Install after uninstalling the previous version of EXPRESSCLUSTER. |
请卸载旧版本EXPRESSCLUSTER后重新安装。 |
setup |
The SNMP service is running. You need to stop the SNMP service before you perform uninstallation. Do you want to stop the SNMP service now? |
选择[Yes],EXPRESSCLUSTER Setup将自动停止SNMP服务,继续安装。选择[No]则中断安装,手动停止SNMP服务后重新进行安装。 |
setup |
Setup has failed.
Error code : xxx
|
- 确认手册上记载的运行环境,安装步骤,注意事项,确认操作是否符合要求。
- 如果有其他启动的应用程序,请退出。
- 重启OS后,重新安装。
|
setup |
Setup has failed(xxx).
Error code : xxx
Please reboot the system and try again.
|
- 确认手册上记载的运行环境,安装步骤,注意事项,确认操作是否符合要求。
- 如果有其他启动的应用程序,请退出。
- 重启OS后,重新安装。
|
setup |
Unsupported environment. |
请在符合要求的运行环境中安装。 |
setup |
Cannot perform uninstallation because there is one or more EXPRESSCLUSTER services still running. Stop all EXPRESSCLUSTER services before you restart uninstallation. |
停止所有EXPRESSCLUSTER服务后再重新进行卸载。 |
setup |
Failed to start the installer. (errcode: xxx) |
- 确认手册上记载的运行环境,安装步骤,注意事项,确认操作是否符合要求。
- 如果有其他启动的应用程序,请退出。
- 请确认是否是安装程序文件损坏或不足。
|
setup |
Internal error.
(xxx)
|
- 确认手册上记载的运行环境,安装步骤,注意事项,确认操作是否符合要求。
- 如果有其他启动的应用程序,请退出。
|
4.2. 事件日志,警报消息¶
输出到应用程序事件日志,Cluster WebUI的警报日志等中的消息一览。Alert,Eventlog,Userlog的各列中带有●的消息分别记录到相应日志中。各日志的查看方法如下。
日志名 |
查看方法 |
文件名 |
---|---|---|
Alert |
输出到Cluster WebUI的警报日志中。使用"日志收集工具"可以收集。 |
Alertlog.alt |
Eventlog |
输出到OS的事件查看器(application log)中。事件源是"EXPRESSCLUSTER X"。可以使用"日志采集工具"收集日志,但因为在右侧的文件名中按照二进制形式进行收集,所以要参考其内容,需要在安装EXPRESSCLUSTER的环境中使用事件查看器打开文件。 |
AppEvent.Evt
SysEvent.Evt
|
Userlog |
记录详细信息的文本格式日志。使用"日志收集工具" 收集日志。收集的日志输出到log文件夹下的"userlog.00.log"文件中。 |
userlog.00.log |
Mail Report的列中带有●的消息在设置了警报服务的邮件通报功能时将被通报。
SNMP Trap的列中带有●的消息在设置了警报服务的SNMP Trap发送时将被通报。
通告设置是结合使用ESMPRO/AlertManager时的通告设置。Alive是ESMPRO/AlertManager输出Alive通告的设置。Manager向ESMPRO/AlertManager输出警报。具体内容请参考ESMPRO/AlertManager的手册。
关于邮件通报,SNMP Trap发送请参考《EXPRESSCLUSTER X SingleServerSafe 设置指南》的"其他设置的详细信息" 的 "集群属性" 的 "Alert服务标签页"。
带有×的消息根据《EXPRESSCLUSTER X SingleServerSafe 设置指南》的"其他设置的详细信息"的"集群属性"的"Alert服务标签页"无法进行通报设置。
关于Message Topic 列中标有●标记的消息在设置了Amazon SNS联动功能时会被通报。
关于Amazon SNS联动功能,请参考《EXPRESSCLUSTER X SingleServerSafe 设置指南》的"其他设置的详细信息"的"集群属性"的"云标签页"。
下表中使用的记号如下所示。
[1]Alert, [2]Eventlog, [3]Userlog, [4]Mail Report, [5]SNMP Trap, [6]Alive, [7]Manager, [8]Message Topic
模块类型 |
事件分类 |
事件ID |
消息 |
描述 |
对策 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
nm |
信息 |
1 |
The server %1 has been started. |
服务器已启动。 |
- |
● |
● |
||||||
nm |
信息 |
2 |
The server %1 has been stopped. |
服务器已停止。 |
检测出服务器宕机。请排除服务器故障后,将服务器恢复到集群中。 |
● |
● |
● |
● |
● |
● |
● |
|
nm |
信息 |
3 |
The resource %2 of the server %1 has been started. |
资源已启动。 |
- |
● |
|||||||
nm |
错误 |
4 |
The resource %2 of the server %1 has an error. |
资源异常。 |
请排除资源异常的原因。 |
● |
|||||||
nm |
信息 |
5 |
The resource %2 of the server %1 has been recovered to the normal status. |
资源复归。 |
- |
● |
|||||||
nm |
错误 |
6 |
The resource %2 of the server %1 is unknown. |
资源状态不明。 |
请确认集群配置信息。 |
● |
● |
● |
|||||
nm |
错误 |
7 |
Network partition was detected. Shut down the server %1 to protect data. |
网络分区检测。 |
所有心跳资源将无法使用。请确认网络适配器中是否有错误,网络连接是否正确。 |
● |
● |
● |
● |
● |
|||
nm |
错误 |
8 |
An error occurred while confirming the network partition. Shut down the server %1. |
不能确认网络分区 |
请参考事件日志确认资源中是否发生错误。 |
● |
● |
● |
● |
● |
|||
nm |
错误 |
9 |
An error occurred in confirming the network partition. To avoid failover on multiple servers, the server %1 suspended failover. |
保留了失效切换。 |
请参考事件日志,确认资源中是否发生错误。 |
● |
● |
● |
● |
● |
|||
nm |
信息 |
10 |
The server %1 canceled the pending failover. |
取消了保留的失效切换。 |
- |
● |
● |
● |
|||||
nm |
错误 |
11 |
Shut down the server %1. (reason:%2) |
关闭服务器 |
所有心跳资源将无法使用。请确认网络适配器中是否有错误,网络连接是否正确。 |
● |
● |
● |
● |
||||
nm |
错误 |
12 |
Cluster service will be stopped. (reason:%1) |
停止集群服务 |
请排除原因所示的故障。 |
● |
● |
● |
|||||
nm |
警告 |
13 |
The combination of the network partition resources is invalid. (server name:%1) |
NP资源的组合不正确 |
请确认集群配置信息。 |
● |
● |
● |
|||||
nm |
错误 |
14 |
The status of heartbeat %1 is abnormal. |
心跳异常。 |
请确认网络适配器是否发生了错误,网络连接是否正确。 |
● |
● |
● |
● |
||||
nm |
信息 |
15 |
The heartbeat %1 has been recovered to the normal status. |
心跳复归。 |
- |
● |
● |
||||||
nm |
错误 |
16 |
The network partition %2 of the server %1 has an error. |
网络分区异常。 |
请参考事件日志确认资源中是否发生错误。 |
● |
● |
● |
● |
||||
nm |
信息 |
17 |
The network partition %2 of the server %1 has been recovered to the normal status. |
网络分区复归。 |
- |
● |
● |
||||||
nm |
错误 |
18 |
Failed to start the resource %1. Server name:%2 |
资源启动失败 |
请参考事件日志确认资源中是否发生错误。 |
● |
● |
● |
● |
||||
nm |
信息 |
19 |
Waiting for startup of all servers has been canceled. |
取消服务器启动等待 |
- |
● |
● |
||||||
nm |
错误 |
20 |
Network partition was detected. Stop the cluster service on the server %1 to protect data. |
网络分区检测 |
不能使用所有心跳的状态。请检查网络连接器是否未发生错误或网络是否正确连接。 |
● |
● |
● |
|||||
nm |
错误 |
21 |
An error occurred while confirming the network partition. Stop the cluster service on the server %1. |
不能确认网络分区 |
请参考事件日志确认资源是否未发生错误。 |
● |
● |
● |
|||||
nm |
错误 |
22 |
Network partition was detected. Execute action(%1) on the server %2 for the cluster service to protect data. |
查出网络分区 |
不能使用所有心跳的状态。请确认网络适配器中是否有错误,网络连接是否正确。 |
● |
● |
● |
|||||
nm |
错误 |
23 |
An error occurred when checking for a network partition. Execute action(%1) on the server %2 for the cluster service to protect data. |
不能确认网络分区 |
参照事件日志确认是否有资源错误发生 |
● |
● |
● |
|||||
nm |
错误 |
24 |
Refer to the event logs to check whether an error has occurred in a resource. |
不能解决网络分区 |
不能使用所有心跳的状态。请确认网络适配器中是否有错误,网络连接是否正确。 |
● |
● |
● |
|||||
nm |
警告 |
25 |
NP resolution process at the cluster startup is disabled. |
禁用网络分区解决 |
禁用集群启动时的网络分区解决处理。 |
● |
● |
● |
|||||
pm |
信息 |
501 |
Cluster service has been started properly. |
集群服务已启动。 |
- |
● |
● |
● |
|||||
pm |
信息 |
502 |
Cluster service is shutting down. |
集群服务已停止。 |
- |
● |
● |
● |
|||||
pm |
错误 |
510 |
Cluster service has already been started. |
集群服务已双重启动。 |
请确认集群服务的状态。 |
● |
● |
● |
● |
||||
pm |
错误 |
511 |
Fatal error has occurred in the cluster service. |
集群服务中发生了致命错误。 |
可执行是没有使用拥有要求权限的帐号启动服务,或者系统无法正常运行。 |
● |
● |
● |
● |
● |
● |
● |
|
pm |
错误 |
512 |
An error is detected in xml library. |
检测出xml库异常。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
pm |
错误 |
513 |
An error is detected in configuration file. |
集群配置信息文件中检测出问题。 |
请确认集群配置信息。 |
● |
● |
● |
● |
● |
● |
● |
|
pm |
错误 |
514 |
Configuration file does not exist. |
集群配置信息文件不存在。 |
请上载集群配置信息。 |
● |
● |
● |
● |
||||
pm |
错误 |
515 |
My host name is not found in configuration file. |
集群配置信息文件中不存在自身服务器名。 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
pm |
警告 |
516 |
The recovery action is configured to change from an OS stop to an OS restart. |
确认集群属性设置。 |
- |
● |
● |
● |
|||||
pm |
错误 |
520 |
%1 process terminated abnormally. |
进程异常退出。 |
系统可执行无法正常运行。 即使nm进程异常结束,也不会影响业务,但是无法执行集群停止操作。 要复原,请使用Cluster WebUI或clpdown命令重新启动OS。 |
● |
● |
● |
● |
● |
● |
● |
|
pm |
错误 |
521 |
The cluster service process returned an error. (halting system) |
进程异常退出。(系统停止) |
原因可执行是组资源停止失败。请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
pm |
错误 |
522 |
An error has occurred while initializing %1 process. (return code:%2) |
初始化发生错误。 |
请排除初始化错误的原因。 |
● |
● |
● |
● |
● |
● |
● |
|
pm |
信息 |
523 |
The system will be shut down. |
系统关机。 |
- |
● |
● |
● |
|||||
pm |
信息 |
524 |
Cluster service will be stopped. |
将停止集群服务。 |
- |
● |
● |
● |
|||||
pm |
信息 |
525 |
System will be rebooted. |
将重启系统。 |
- |
● |
● |
● |
|||||
pm |
信息 |
526 |
%1 process will be restarted. |
将重启进程。 |
- |
● |
● |
● |
|||||
pm |
信息 |
527 |
Emergency shutdown is in progress. |
将紧急关机。 |
- |
● |
● |
● |
|||||
pm |
信息 |
528 |
Generating STOP error. |
发生STOP错误。 |
- |
● |
● |
● |
|||||
pm |
信息 |
529 |
Generating hardware reset. |
将发生硬件复位。 |
- |
● |
● |
● |
|||||
pm |
信息 |
530 |
There was a request to shut down the system from the %1. |
请求集群关机。 |
- |
● |
● |
● |
|||||
pm |
信息 |
531 |
There was a request to stop cluster service from the %1. |
请求停止集群服务。 |
- |
● |
● |
● |
|||||
pm |
信息 |
532 |
There was a request to reboot system from the %1. |
请求重启系统。 |
- |
● |
● |
● |
|||||
pm |
信息 |
533 |
There was a request to restart cluster service from the %1. |
请求重启集群服务。 |
- |
● |
● |
● |
|||||
pm |
信息 |
534 |
There was a request to resume cluster service from the %1. |
请求恢复集群服务。 |
- |
● |
● |
● |
|||||
pm |
信息 |
535 |
There was a request to suspend cluster service from the %1. |
请求挂起集群服务。 |
- |
● |
● |
● |
|||||
pm |
信息 |
536 |
There was a request of emergency shutdown from the %1. |
请求紧急关机。 |
- |
● |
● |
● |
|||||
pm |
信息 |
537 |
There was a request to generate STOP error from the %1. |
请求STOP错误。 |
- |
● |
● |
● |
|||||
pm |
信息 |
538 |
There was a request to generate hardware reset from the %1. |
请求硬件复位。 |
- |
● |
● |
● |
|||||
pm |
信息 |
540 |
Requesting shutdown to the automatic running control software. |
向自动运行软件提出系统关机的请求。 |
- |
● |
● |
● |
|||||
pm |
信息 |
541 |
Requesting shutdown (reboot) to the automatic running control software. |
向自动运行软件提出系统关机(重启)的请求。 |
- |
● |
● |
● |
|||||
pm |
信息 |
542 |
Shutdown request to the automatic running control software is completed. |
向自动运行软件提出系统关机的请求。 |
- |
● |
● |
● |
|||||
pm |
错误 |
543 |
The automatic running control software returned an error to the shutdown request. |
通过自动运行软件进行系统关机处理失败。 |
可执行自动运行软件设置不正确。请确认。 |
● |
● |
● |
● |
||||
pm |
错误 |
544 |
Communications with the automatic running control software failed. |
与自动软件的通信失败。 |
系统可执行无法正常操作。 |
● |
● |
● |
● |
||||
pmsvc |
错误 |
801 |
The system will be shutdown because cluster resume was failed. |
恢复失败导致关机 |
- |
● |
● |
● |
|||||
pmsvc |
错误 |
802 |
An attempt to shutdown the system failed. |
关机失败 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
pmsvc |
信息 |
810 |
The system shutdown was initiated by other than cluster service. Stopping cluster service. (timeout=%1 min). |
开始集群服务停止等待处理 |
- |
● |
● |
● |
|||||
pmsvc |
信息 |
811 |
Stopping cluster service has been completed. |
结束集群服务停止等待处理 |
- |
● |
● |
● |
|||||
pmsvc |
错误 |
812 |
Stopping cluster service has timed out. |
等待集群服务超时 |
- |
● |
● |
● |
|||||
pmsvc |
警告 |
813 |
Stopping cluster service has been canceled. |
取消集群服务停止等待处理 |
- |
● |
● |
● |
|||||
rc |
信息 |
1010 |
The group %1 is starting. |
开始启动组。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1011 |
The group %1 has been started. |
组启动完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1012 |
Failed to start the group %1. |
组启动失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
信息 |
1015 |
Waiting for group %1 to start has started. |
开始组启动等待处理 |
- |
● |
● |
● |
|||||
rc |
信息 |
1016 |
Waiting for group %1 to start has been completed. |
结束组启动等待处理 |
- |
● |
● |
● |
|||||
rc |
错误 |
1017 |
Group start was canceled because waiting for group %1 to start was timed out. (%2) |
终止组启动等待处理 |
请确认启动等待目标组的状态。
如果组未启动,请启动该组后,重新执行组的操作。
|
● |
● |
● |
|||||
rc |
警告 |
1018 |
Waiting for group %1 to start has timed out. However, group start continues. (%2) |
继续组启动处理 |
- |
● |
● |
● |
|||||
rc |
错误 |
1019 |
Server %1 is not in a condition to start group %2. |
组不能启动。 |
如果目标服务器为保留(宕机后重启),请执行服务器恢复操作。如果是保留(NP未解决),则请将NP资源恢复为正常状态。 |
● |
|||||||
rc |
信息 |
1020 |
The group %1 is stopping. |
开始停止组。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1021 |
The group %1 has been stopped. |
组停止完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1022 |
Failed to stop the group %1. |
组停止失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
信息 |
1025 |
Waiting for group %1 to stop has started. |
开始组启动等待处理 |
- |
● |
● |
● |
|||||
rc |
信息 |
1026 |
Waiting for group %1 to stop has started. |
结束组启动等待处理 |
- |
● |
● |
● |
|||||
rc |
错误 |
1027 |
Group stop has been canceled because waiting for group %1 to stop has timed out. (%2) |
终止组启动等待处理 |
请确认启动等待目标组的状态。
如果组未启动,请启动该组后,重新执行组的操作。
|
● |
● |
● |
|||||
rc |
警告 |
1028 |
Waiting for group %1 to stop has timed out. However, group stop continues. (%2) |
继续组启动处理 |
- |
● |
● |
● |
|||||
rc |
信息 |
1030 |
The resource %1 is starting. |
开始启动资源。 |
- |
● |
● |
||||||
rc |
信息 |
1031 |
The resource %1 has been started. |
资源启动完毕。 |
- |
● |
● |
||||||
rc |
错误 |
1032 |
Failed to start the resource %1. (%2 : %3) |
资源启动失败。 |
请排除资源启动失败的原因。
启动处理发生失速时,输出"资源 %1 启动失败。(99 : command is timeout)"。
|
● |
● |
● |
● |
● |
● |
● |
|
rc |
错误 |
1033 |
Failed to start the recovery script of resource %1. (%2 : %3) |
启动脚本资源失败。 |
请排除恢复脚本启动失败的原因。 |
● |
● |
● |
● |
||||
rc |
信息 |
1034 |
A request to activate %1 resource on server %2 has been started. |
对待机服务器请求资源启动 |
- |
● |
● |
● |
|||||
rc |
信息 |
1035 |
A request to activate %1 resource on server %2 has been completed. |
对待机服务器请求资源启动完成 |
- |
● |
● |
● |
|||||
rc |
错误 |
1036 |
A request to activate %1 resource on server %2 has been failed. |
对待机服务器请求资源启动失败 |
请确认网络是否发生异常,或者对方服务器是否发生异常。 |
● |
● |
● |
|||||
rc |
信息 |
1040 |
The resource %1 is stopping. |
开始停止资源。 |
- |
● |
● |
||||||
rc |
信息 |
1041 |
The resource %1 has been stopped. |
资源停止完毕。 |
- |
● |
● |
||||||
rc |
错误 |
1042 |
Failed to stop the resource %1. (%2 : %3) |
资源停止失败。 |
请排除资源停止失败的原因。
停止处理发生失速时,输出"资源 %1 停止失败。(99 : command is timeout)"。
|
● |
● |
● |
● |
● |
● |
● |
|
rc |
信息 |
1044 |
A request to stop %1 resource on server %2 has been started. |
对待机服务器请求资源停止 |
- |
● |
● |
● |
|||||
rc |
信息 |
1045 |
A request to stop %1 resource on server %2 has been completed. |
对待机服务器请求资源停止完成 |
- |
● |
● |
● |
|||||
rc |
错误 |
1046 |
A request to stop %1 resource on server %2 has been failed. |
对待机服务器请求资源停止失败 |
请确认网络是否发生异常,或者对方服务器是否发生异常。 |
● |
● |
● |
|||||
rc |
信息 |
1050 |
Moving the group %1. |
开始移动组。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1051 |
The group %1 has been moved. |
组移动完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1052 |
Failed to move the group %1. |
组移动失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1059 |
Server %1 is not in a condition to move group %2. |
组不能移动。 |
如果目标服务器为保留(宕机后重启),请执行服务器恢复操作。如果是保留(NP未解决),则请将NP资源恢复为正常状态。 |
● |
|||||||
rc |
信息 |
1060 |
Failing over the group %1. |
开始组失效切换。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1061 |
The group %1 has been failed over. |
组失效切换完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1062 |
Failed to fail over the group %1. |
组失效切换失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
信息 |
1070 |
Restarting the group %1. |
开始重启组。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1071 |
The group %1 has been restarted. |
组重启完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1072 |
Failed to restart the group %1. |
组重启失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1077 |
Group failover has failed because there is a server incapable of internal communication. |
组失效切换失败(不可以进行内部通信) |
请确认内核模式LAN心跳的状态。恢复内部通信后,请重启组。 |
● |
● |
● |
|||||
rc |
信息 |
1080 |
Restarting the resource %1. |
开始重启资源。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1081 |
The resource %1 has been restarted. |
资源重启完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1082 |
Failed to restart the resource %1. |
资源重启失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
信息 |
1090 |
Shutting down the cluster. |
集群关机。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1091 |
Shutting down the server. |
服务器关机。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1092 |
Group %1 is started on more than one server. |
组双重启动。 |
服务器将自动关机。请排除组在多个服务器上启动的原因。 |
● |
● |
● |
● |
● |
● |
● |
|
rc |
错误 |
1093 |
The system shutdown was performed by other than the cluster service. |
从集群之外发生关机。 |
从集群服务之外执行关闭系统操作时,视为异常。请在集群环境中按指定步骤执行关机操作。 |
● |
● |
● |
● |
||||
rc |
警告 |
1100 |
Shutdown count is reached the maximum number (%1). Final action of resource %2 was ignored. |
关机次数达到最大值。 |
- |
● |
● |
● |
● |
● |
● |
● |
|
rc |
警告 |
1101 |
Since there is no other normally running server, the final action for an activation error of group resource %1 was suppressed. |
控制启动异常的最终动作 |
- |
● |
● |
● |
|||||
rc |
警告 |
1102 |
Since there is no other normally running server, the final action for a deactivation error of group resource %1 was suppressed. |
控制停止异常的最终动作 |
- |
● |
● |
● |
|||||
rc |
警告 |
1103 |
Since server %1 is specified as that which suppresses shutdown at both-system activation detection, it ignored the shutdown request. |
通过双启动控制关机 |
- |
● |
● |
● |
|||||
rc |
警告 |
1104 |
A mismatch in the group %1 status occurs between the servers. |
产生组状态不匹配 |
执行组重启或集群重启。 |
● |
● |
● |
|||||
rc |
信息 |
1105 |
Since server %1 is not specified as that which suppresses shutdown at both-system activation detection, it executed the shutdown request. |
通过双启动关机 |
- |
● |
● |
● |
|||||
rc |
信息 |
1106 |
The number of reboots due to group resource errors has been reset. |
重置重启次数(组资源) |
- |
● |
● |
● |
|||||
rc |
信息 |
1110 |
Server %1 is returned to the cluster. |
服务器已复归。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1111 |
Server %1 is isolated from the cluster. |
服务器已分离。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1112 |
Server %1 started to return to the cluster. |
服务器已开始复归。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1113 |
Server %1 failed to return to the cluster. |
服务器复归失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rc |
信息 |
1120 |
Server %1 will notify the automatic running control software of shutdown start. |
开始关机的通知。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1121 |
The automatic running control software returned an error to the shutdown start notification in server %1. |
对开始关机的通知返回错误。 |
可执行自动运行软件设置不正确。请确认自动运行软件的设置。 |
● |
● |
● |
● |
||||
rc |
信息 |
1122 |
Server %1 notified the automatic running control software of shutdown start. |
已通知自动运行软件开始关机。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1123 |
The automatic running control software is checking the power status of shared disks. A server will be restarted after the power status is checked. |
等待确认电源接通。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1124 |
An error was returned from the automatic running control software. Failed to check the power status of shared disks. |
确认电源接通失败。 |
可执行自动运行软件的设置不正确。请确认自动运行软件的设置。或者可执行自动电源控制设备发生了异常。请确认自动电源控制设备。 |
● |
● |
● |
● |
||||
rc |
错误 |
1125 |
Server %1 failed to communicate with the automatic running control software. |
与自动运行控制软件的通信失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rc |
信息 |
1130 |
Starting a single resource %1. |
开始启动单一资源。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1131 |
A single resource %1 has been started. |
单一资源启动完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1132 |
Failed to start a single resource %1. |
单一资源启动失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1139 |
Server %1 is not in a condition to start a single resource %2. |
不能启动单一资源。 |
如果目标服务器为保留(宕机后重启),请执行服务器恢复操作。如果是保留(NP未解决),则请将NP资源恢复为正常状态。 |
● |
|||||||
rc |
信息 |
1140 |
Stopping a single resource %1. |
开始停止单一资源。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1141 |
A single resource %1 has been stopped. |
单一资源停止完毕。 |
- |
● |
● |
● |
|||||
rc |
错误 |
1142 |
Failed to stop a single resource %1. |
单一资源停止失败。 |
请按照组资源的消息进行处理。 |
● |
● |
● |
● |
||||
rc |
信息 |
1150 |
Migrating the group %1. |
开始组迁移 |
- |
● |
● |
● |
|||||
rc |
信息 |
1151 |
The group %1 has been migrated. |
组迁移完成 |
- |
● |
● |
● |
|||||
rc |
错误 |
1152 |
Failed to migrate the group %1. |
组迁移失败 |
请按组资源的提示进行处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1159 |
Server %1 is not in a condition to migrate group %2. |
不能迁移组 |
对象服务器保留(宕机后重启)时,请执行服务器恢复操作。保留(NP未解决)时,请将NP资源设成正常状态。 |
● |
● |
● |
|||||
rc |
信息 |
1170 |
Server %1 in the same server group (%2) has been set as the destination for the group %3. |
服务器组内失效切换 |
- |
● |
● |
● |
|||||
rc |
信息 |
1171 |
Server %1 not in the same server group (%2) has been set as the destination for the group %3. |
服务器组外失效切换 |
- |
● |
● |
● |
|||||
rc |
错误 |
1179 |
Can not fail over the group %1 because there is no appropriate destination in the same server group %2. |
不能进行服务器组内失效切换 |
服务器组内的其他服务器已经停止或关闭后再启动的状态。请重启相应的服务器或复归集群。 |
● |
● |
● |
|||||
rc |
信息 |
1200 |
The resource %1 will be restarted since starting the resource %2 failed. |
因为资源启动失败,重启资源。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1201 |
The group %1 will be failed over to server %2 since starting the resource %3 failed. |
因为资源启动失败,执行组的失效切换。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1202 |
The group %1 will be stopped since starting the resource %2 failed. |
因为资源启动失败,停止组。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1203 |
The cluster service will be stopped since starting the resource %1 failed. |
因为资源启动失败,停止服务。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1204 |
The system will be shut down since starting the resource %1 failed. |
因为资源启动失败,关闭系统。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1205 |
The system will be rebooted since starting the resource %1 failed. |
因为资源启动失败,重启系统。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1220 |
The resource %1 will be stopped again since stopping the resource %2 failed. |
因为资源停止失败,重新停止资源。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1223 |
The cluster service will be stopped since stopping the resource %1 failed. |
因为资源停止失败,停止集群服务。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1224 |
The system will be shut down since stopping the resource %1 failed. |
因为资源停止失败,关闭系统。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1225 |
The system will be rebooted since stopping the resource %1 failed. |
因为资源停止失败,重启系统。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1241 |
Hardware reset will be generated since starting the resource %1 failed. |
因为资源启动失败,重置硬件。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1242 |
STOP error will be generated since starting the resource %1 failed. |
因为资源启动失败,发生停止错误。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1281 |
Hardware reset will be generated since stopping the resource %1 failed. |
因为资源停止失败,产生重置。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1282 |
STOP error will be generated since stopping the resource %1 failed. |
因为资源停止失败,产生停止错误。 |
- |
● |
● |
● |
|||||
rc |
信息 |
1300 |
Script before final action upon activation failure in resource %1 started. |
资源启动异常时最终动作前脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1301 |
Script before final action upon activation failure in resource %1 completed. |
资源启动异常时最终动作前脚本结束 |
- |
● |
● |
● |
|||||
rc |
信息 |
1302 |
Script before final action upon deactivation failure in resource %1 started. |
资源停止异常时最终动作前脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1303 |
Script before final action upon deactivation failure in resource %1 completed. |
资源停止异常时最终动作前脚本结束 |
- |
● |
● |
● |
|||||
rc |
信息 |
1304 |
Script before activation in resource %1 started. |
资源启动前脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1305 |
Script before activation in resource %1 completed. |
资源启动前脚本结束 |
- |
● |
● |
● |
|||||
rc |
信息 |
1306 |
Script after activation in resource %1 started. |
资源启动后脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1307 |
Script after activation in resource %1 completed. |
资源启动后脚本结束 |
- |
● |
● |
● |
|||||
rc |
信息 |
1308 |
Script before deactivation in resource %1 started. |
资源停止前脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1309 |
Script before deactivation in resource %1 completed. |
资源停止前脚本结束 |
- |
● |
● |
● |
|||||
rc |
信息 |
1310 |
Script after deactivation in resource %1 started. |
资源停止后脚本开始 |
- |
● |
● |
● |
|||||
rc |
信息 |
1311 |
Script after deactivation in resource %1 completed. |
资源停止后脚本结束 |
- |
● |
● |
● |
|||||
rc |
错误 |
1340 |
Script before final action upon activation failure in resource %1 failed. |
资源启动异常时最终动作前脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1341 |
Script before final action upon deactivation failure in resource %1 failed. |
资源停止异常时最终动作前脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1342 |
Failed to execute script before activation in resource %1. |
资源启动前脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1343 |
Failed to execute script after activation in resource %1. |
资源启动后脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1344 |
Failed to execute script before deactivation in resource %1. |
资源停止前脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1345 |
Failed to execute script after deactivation in resource %1. |
资源停止后脚本失败 |
请确认脚本失败的原因,进行相应的处理。 |
● |
● |
● |
● |
||||
rc |
错误 |
1346 |
Failed to log on as a user. |
用户登录失败 |
请确认执行用户的域,账号,密码是否设置正确。 |
● |
● |
● |
|||||
rc |
信息 |
1400 |
The status of the regular check for a forced stop returned to normal. |
强制停止 状态正常 |
- |
● |
● |
● |
|||||
rc |
错误 |
1401 |
The regular check for a forced stop detected an abnormality. |
强制停止 状态异常 |
强制停止功能可能无法正常工作。请确认异常原因。 |
● |
● |
● |
|||||
rc |
错误 |
1402 |
The request for forcibly stopping the server has been timed out. |
强制停止 停止请求超时 |
请确认停止请求超时的原因,并采取对应措施。 |
● |
● |
● |
|||||
rc |
信息 |
1403 |
The request for forcibly stopping the server will be retried. |
强制停止 重试停止请求 |
- |
● |
● |
● |
|||||
rc |
错误 |
1404 |
The check of forcibly stopping the server has been timed out. |
强制停止 停止确认超时 |
请确认停止确认超时的原因,并采取对应措施。 |
● |
● |
● |
|||||
rc |
信息 |
1405 |
The check of forcibly stopping the server will be retried. |
强制停止 重试停止确认 |
- |
● |
● |
● |
|||||
rc |
警告 |
1427 |
Group failover has been canceled because forced stop of server %1 failed |
因强制停止失败失效切换控制。 |
请确认强制停止失败的原因,进行相应的处理。 |
● |
● |
● |
|||||
rc |
警告 |
1450 |
Cluster action is disabled. |
集群运行禁用中 |
- |
● |
● |
● |
|||||
rc |
警告 |
1451 |
Ignored the automatic start of groups because automatic group startup is disabled. |
自动启动未执行 |
- |
● |
● |
● |
|||||
rc |
警告 |
1452 |
Ignored the recovery action in resource activation because recovery action caused by group resource activation error is disabled. |
复归操作未执行 |
- |
● |
● |
● |
|||||
rc |
警告 |
1453 |
Ignored the recovery action in resource deactivation because recovery action caused by group resource deactivation error is disabled. |
复归操作未执行 |
- |
● |
● |
● |
|||||
rc |
信息 |
1454 |
Cluster action is set disabled. |
禁用集群运行 |
- |
● |
● |
● |
|||||
rc |
信息 |
1455 |
Cluster action is set enabled. |
启用集群运行 |
- |
● |
● |
● |
|||||
rc |
警告 |
1456 |
Cluster operation is forcibly disabled since a valid license has not been registered. |
强制禁用集群运行(License许可无效) |
请注册License许可。注册License许可后,最多可执行需要1小时才能解除强制禁用集群运行。如果想马上解除,注册License许可后请执行集群的挂起/恢复。 |
● |
● |
● |
|||||
rc |
信息 |
1457 |
The forcible disablement of cluster operation was canceled since the valid licenses are registered. |
解除强制禁用集群运行 |
- |
● |
● |
● |
|||||
rc |
警告 |
1458 |
Ignored the group failover because failover for a server failure is disabled. |
抑制失效切换 |
- |
● |
● |
● |
|||||
rc |
信息 |
1470 |
Server %1 has been set as the destination for the group %2 (reason: %3).) |
确定启动服务器。 |
- |
● |
● |
● |
|||||
rc |
警告 |
1471 |
There is no appropriate destination for the group %1 (reason: %2). |
没有合适的启动服务器。(启动集群,失效切换) |
在其他服务器上查出监视资源异常。请排除异常的原因并暂停监视。 |
● |
● |
● |
|||||
rc |
警告 |
1472 |
Server %1 is not in a condition to start group %2 (reason: %3). |
没有合适的启动服务器。(启动组) |
在相应的服务器上查出监视资源异常。请排除异常的原因并暂停监视。 |
● |
● |
● |
|||||
rc |
错误 |
1480 |
Group start has been canceled because waiting for group %1 to start has failed. (%2) |
启动等待失败(终止组启动) |
- |
● |
● |
● |
|||||
rc |
警告 |
1481 |
Waiting for group %1 to start has failed. However, group start continues. (%2) |
启动等待失败(继续组启动) |
- |
● |
● |
● |
|||||
rc |
错误 |
1482 |
Group start has been canceled because waiting for group %1 to start has canceled. |
启动等待终止(终止组启动) |
- |
● |
● |
● |
|||||
rc |
警告 |
1483 |
Waiting for group %1 to start has canceled. However, group start continues. |
启动等待终止(继续组启动) |
- |
● |
● |
● |
|||||
rc |
错误 |
1484 |
Group stop has been canceled because waiting for group %1 to stop has failed. (%2) |
停止等待失败(终止组停止) |
- |
● |
● |
● |
|||||
rc |
警告 |
1485 |
Waiting for group %1 to stop has failed. However, group stop continues. (%2) |
停止等待失败(继续组停止) |
- |
● |
● |
● |
|||||
rc |
错误 |
1486 |
Group stop has been canceled because waiting for group %1 to stop has canceled. |
停止等待终止(终止组停止) |
- |
● |
● |
● |
|||||
rc |
警告 |
1487 |
Waiting for group %1 to stop has canceled. However, group stop continues. |
停止等待终止(继续组停止) |
- |
● |
● |
● |
|||||
rc |
信息 |
1490 |
Group %1 started to check the double activation. |
双重启动检查开始 |
- |
● |
|||||||
rc |
信息 |
1491 |
Group %1 completed to check the double activation. |
双重启动检查结束 |
- |
● |
|||||||
rc |
错误 |
1492 |
Group %1 failed to check the double activation. |
双重启动检查失败 |
请确认组的状态。 |
● |
● |
● |
● |
||||
rc |
信息 |
1493 |
Waiting for group %1 to start for check the double activation. |
为了双重启动检查等待组启动 |
请确认组的状态。 |
● |
● |
● |
|||||
rm |
信息 |
1501 |
Monitor %1 has been started. |
监视已启动。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1502 |
Monitor %1 has been stopped. |
监视已停止。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1503 |
Monitor %1 does not monitor in this server. |
非对象服务器。 |
- |
● |
● |
● |
|||||
rm |
警告 |
1504 |
Monitor %1 is in the warning status. (%2 : %3) |
监视警告。 |
请确认警告的原因。 |
● |
● |
● |
● |
||||
rm |
警告 |
1505 |
The number of monitor resources reached the maximum number. (registered resource: %1) |
监视资源数不正确。 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
rm |
警告 |
1506 |
Configuration of %1 is invalid. (%2 : %3) |
监视资源不正确 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
rm |
错误 |
1507 |
Failed to start monitor %1. |
监视启动失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
● |
● |
● |
|
rm |
错误 |
1508 |
Failed to stop monitor %1. |
监视停止失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
错误 |
1509 |
Monitor %1 detected an error. (%2 : %3) |
监视失败 |
请确认监视异常的原因。 |
● |
● |
● |
● |
● |
● |
● |
|
rm |
信息 |
1510 |
Monitor %1 is not monitored. |
非监视。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1511 |
Monitor resource has not been registered. |
未登录的监视资源。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1512 |
%1 was stopped for failure in monitor %2. |
复归对象停止。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1513 |
%1 was restarted for failure in monitor %2. |
复归对象重启。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1514 |
%1 was failed over for failure in monitor %2. |
复归对象组失效切换。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1515 |
There was a request to stop cluster for failure in monitor %1. |
集群停止。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1516 |
There was a request to shut down the system for failure in monitor %1. |
系统关机。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1517 |
There was a request to restart the system for failure in monitor %1. |
系统重启。 |
- |
● |
● |
● |
|||||
rm |
错误 |
1518 |
Failed to stop %1 due to error detection of %2. |
停止复归对象失败。 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
rm |
错误 |
1519 |
Failed to restart %1 due to error detection of %2. |
重启复归对象失败。 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
rm |
错误 |
1520 |
Failed to fail over %1 due to error detection of %2. |
复归对象组失效切换失败。 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
rm |
错误 |
1521 |
Failed to stop the cluster due to error detection of %1. |
集群停止失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
错误 |
1522 |
Failed to shut down the system due to error detection of %1. |
操作系统关机失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
错误 |
1523 |
Failed to restart the system due to error detection of %1. |
操作系统重启失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
错误 |
1524 |
The group of monitor %1 is unknown. |
所属组不明。 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
rm |
警告 |
1525 |
No action is taken because %1 is not online. |
无法执行复归运行。 |
- |
● |
● |
● |
● |
||||
rm |
信息 |
1526 |
Status of monitor %1 was returned to normal. |
状态已恢复正常。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1527 |
Status of monitor %1 was changed into unknown. |
状态变为不明。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
rm |
错误 |
1528 |
Initialization error has occurred (%1 : %2) |
监视初始化时发生异常。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
信息 |
1529 |
Monitor %1 was suspended. |
暂停监视。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1530 |
Monitor %1 was resumed. |
恢复监视。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1531 |
All monitors were suspended. |
暂停所有监视。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1532 |
All monitors were resumed. |
恢复所有监视。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1533 |
The polling interval of monitor %1 was changed into %2*%3. |
更改轮询间隔。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1534 |
The polling interval ratio of all monitors was changed into %1. |
更改所有监视的轮询间隔。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1535 |
Causing intentional stop error was required because an error is detected by %1. |
发生停止错误。 |
- |
● |
● |
● |
|||||
rm |
错误 |
1536 |
Causing intentional stop error has failed because an error is detected by %1. |
发生停止错误失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
● |
||||
rm |
警告 |
1537 |
Recovery will not be executed since server is suspending. |
不能执行复归运行(服务器状态为保留)。 |
如果目标服务器为保留(NP未解决),则不能执行监视资源恢复操作。请确认导致保留(NP未解决)的原因,将NP资源恢复为正常状态。 |
● |
● |
● |
● |
||||
rm |
警告 |
1538 |
No action is taken because any recovery target is not online. |
不能执行复归动作(不存在启动的复归目标) |
- |
● |
● |
● |
|||||
rm |
警告 |
1539 |
No action is taken because the group is set for the recovery target %1 is not online. |
未能执行复归动作(组) |
- |
● |
● |
● |
|||||
rm |
警告 |
1571 |
Monitor %1 was delayed. (timeout=%2, response time=%3, rate=%4) |
监视发生延迟。 |
确认检测出监视延迟的服务器的负载情况,减少负载。 |
● |
● |
● |
● |
||||
rm |
警告 |
1572 |
Monitor %1 could not perform monitoring. |
内部处理发生延迟 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
rm |
警告 |
1600 |
Shutdown count reached the maximum number (%1). Final action of monitor %2 was ignored. |
关机次数已达到上限。 |
- |
● |
● |
● |
● |
● |
● |
||
rm |
警告 |
1601 |
Since there is no other normally running server, the final action (%1) for the error detection of monitor resource %2 was suppressed. |
控制查出异常的最终动作 |
- |
● |
● |
● |
|||||
rm |
信息 |
1602 |
The number of reboots due to monitor resource errors has been reset. |
重置重启次数(监视资源) |
- |
● |
● |
● |
|||||
rm |
信息 |
1700 |
Script before action(%1) upon failure in %2 monitor resource started. |
监视资源异常时最终动作前脚本开始 |
- |
● |
● |
● |
|||||
rm |
信息 |
1701 |
Script before action(%1) upon failure in %2 monitor resource completed. |
监视资源异常时最终动作前脚本结束 |
- |
● |
● |
● |
|||||
rm |
信息 |
1720 |
Script before action(%1) upon failure in %2 monitor resource failed. |
监视资源异常时最终动作前脚本失败 |
- |
● |
● |
● |
|||||
rm |
信息 |
1750 |
The collecting of detailed information triggered by monitoring %1 error has been started (timeout=%2). |
开始收集详细信息。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1751 |
The collection of detailed information triggered by monitoring %1 error has been completed. |
结束收集详细信息。 |
- |
● |
● |
● |
|||||
rm |
警告 |
1752 |
The collection of detailed information triggered by monitoring %1 error has been failed (%2). |
收集详细信息失败。 |
- |
● |
● |
● |
|||||
rm |
信息 |
1800 |
The %1 service will be started by cluster system. |
启动服务 |
- |
● |
● |
● |
|||||
rm |
信息 |
1801 |
The %1 service will be started again because the service has been stopped by cluster system. (retry: %2/%3) |
尝试启动服务 |
- |
● |
● |
● |
|||||
rm |
信息 |
1802 |
The %1 service will be resumed by cluster system. |
再次展开服务 |
- |
● |
● |
● |
|||||
rm |
信息 |
1803 |
The %1 service will be resumed again because the service has been suspended by cluster system. (retry: %2/%3) |
尝试再次展开服务 |
- |
● |
● |
● |
|||||
rm |
信息 |
1804 |
The %1 service will be stopped by cluster system. |
停止服务 |
- |
● |
● |
● |
|||||
rm |
信息 |
1805 |
The %1 service entered the running state. |
服务执行中状态 |
- |
● |
● |
● |
|||||
rm |
信息 |
1806 |
The %1 service entered the stopped state. |
服务停止状态 (正常) |
- |
● |
● |
● |
|||||
rm |
警告 |
1811 |
Start request of the %1 service failed. Check the service status. |
服务开始请求失败 |
请确认服务的状态。 |
● |
● |
● |
|||||
rm |
警告 |
1812 |
Resume request of the %1 service failed. Check the service status. |
服务再次展开请求失败 |
请确认服务的状况。 |
● |
● |
● |
|||||
rm |
警告 |
1813 |
Stop request of the %1 service failed. Check the service status. |
服务停止请求失败 |
请确认服务的状况。 |
● |
● |
● |
|||||
rm |
警告 |
1816 |
The %1 service has been stopped by other than cluster system. |
服务停止状况 (异常) |
请确认服务停止的状况。 |
● |
● |
● |
|||||
rm |
警告 |
1817 |
The %1 service has been suspended by other than cluster system. |
服务暂时停止状况 (异常) |
请确认服务暂时停止的状况。 |
● |
● |
● |
|||||
rm |
警告 |
1819 |
Start or resume retry count for the %1 service exceeded the threshold (%2). |
服务再启动处理次数超时 |
服务重新启动处理次数超时 |
● |
● |
● |
|||||
rm |
信息 |
1820 |
The cluster will be stopped because there was a failure in %1 service monitoring. |
集群服务停止 (服务监视错误) |
- |
● |
● |
● |
|||||
rm |
信息 |
1821 |
The system will be shut down because there was a failure in %1 service monitoring. |
系统关机 (服务监视错误) |
- |
● |
● |
● |
|||||
rm |
信息 |
1822 |
The cluster will be rebooted because there was a failure in %1 service monitoring. |
系统再启动 (服务监视错误) |
- |
● |
● |
● |
|||||
rm |
错误 |
1870 |
Monitor resource %1 can not be controlled because the license is invalid. |
不可操作(License不正确) |
请确认License的登录状况。 |
● |
● |
● |
|||||
rm |
信息 |
1890 |
Recovery script has executed because an error was detected in monitoring %1. |
复归脚本结束 |
- |
● |
● |
● |
|||||
rm |
错误 |
1891 |
Attempted to execute recovery script due to the error detected in monitoring %1, but failed. |
复归脚本失败 |
请确认复归脚本失败的原因,进行处理。 |
● |
● |
● |
|||||
rm |
错误 |
1892 |
Failed to log on as a user. |
用户登录失败 |
请确认执行用户的域,账号,密码是否设置正确。 |
● |
● |
● |
|||||
rm |
信息 |
1910 |
Dummy Failure of monitor resource %1 is enabled. |
发生模拟故障 |
- |
● |
● |
● |
|||||
rm |
信息 |
1911 |
Dummy Failure of monitor resource %1 is disabled. |
解除模拟故障 |
- |
● |
● |
● |
|||||
rm |
信息 |
1912 |
Dummy Failure of all monitors will be enabled. |
发生所有监视资源的模拟故障 |
- |
● |
● |
● |
|||||
rm |
信息 |
1913 |
Dummy Failure of all monitors will be disabled. |
解除解除所有监视资源的模拟故障 |
- |
● |
● |
● |
|||||
rm |
警告 |
1914 |
An attempt was made to enable Dummy Failure of monitor resource %1, but failed. |
发生模拟故障 |
请确认监视资源%1是否有对应故障检测功能。 |
● |
● |
● |
|||||
rm |
警告 |
1915 |
An attempt was made to disable Dummy Failure of monitor resource %1, but failed. |
解除模拟故障 |
请确认监视资源%1是否有对应故障检测功能。 |
● |
● |
● |
|||||
rm |
信息 |
1930 |
Recovery action caused by monitor resource error is disabled. |
使监视资源异常时的复归运行的抑制功能有效 |
- |
● |
● |
● |
|||||
rm |
信息 |
1931 |
Recovery action caused by monitor resource error is enabled. |
使监视资源异常时的复归运行的抑制功能无效 |
- |
● |
● |
● |
|||||
rm |
警告 |
1932 |
Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled. |
为抑制监视资源异常时的运行,不要执行复归运行。 |
- |
● |
● |
● |
|||||
rm |
警告 |
1933 |
Recovery action at timeout occurrence was disabled, so the recovery action of monitor %1 was not executed. |
由于将监视资源超时时的复归运行设为无效,因此不能执行复归运行。 |
- |
● |
● |
● |
|||||
event |
信息 |
2101 |
%1 service has been started. |
服务启动。 |
- |
● |
|||||||
event |
信息 |
2102 |
%1 service has been stopped. |
服务停止。 |
- |
● |
|||||||
event |
警告 |
2130 |
Time-out or other error has occurred while waiting for internal threads to stop. Detected internal error %1. |
结束等待超时。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2150 |
The specified parameters are invalid. Check the cluster configuration data. |
配置信息异常。 |
请确认集群配置信息。 |
● |
● |
● |
|||||
event |
错误 |
2151 |
Failed to obtain the policy data. Check the data. |
配置信息异常。 |
请确认策略文件的存在或配置内容。 |
● |
● |
● |
|||||
event |
错误 |
2152 |
Failed to obtain the registry data. System may be unable to operate correctly. |
注册表异常。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2153 |
Failed to dispatch to the service manager. System may be unable to operate correctly. |
调度异常。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2154 |
Failed to create an internal resource. System may be unable to operate correctly. |
资源创建失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2155 |
Failed to create communication sockets. System may be unable to operate correctly. |
Socket创建失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2156 |
Failed to control the shared memory. System may be unable to operate correctly. |
共享内存的控制失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2157 |
Failed to generate internal threads. System may be unable to operate correctly. |
内部线程的生成失败。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
event |
错误 |
2199 |
Other internal error has occurred. System may be unable to operate correctly. |
发生内部错误。 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
trnsv |
错误 |
2301 |
There was a notification from external (IP=%1), but it was denied. |
客户端IP地址连接限制 |
请确认客户端的IP地址的连接权限 |
● |
● |
● |
|||||
trnsv |
信息 |
2310 |
There was a notification (%1) from external (IP=%2). |
从外部接收异常发生通知 |
- |
● |
● |
● |
|||||
trnsv |
信息 |
2320 |
Recovery action (%1) of monitoring %2 has been executed because a notification arrived from external. |
执行异常发生时的恢复动作 |
- |
● |
● |
● |
|||||
trnsv |
信息 |
2321 |
Recovery action (%1) of monitoring %2 has been completed. |
异常发生时的恢复动作执行完毕 |
- |
● |
● |
● |
|||||
trnsv |
错误 |
2322 |
Attempted to recovery action (%1) of monitoring %2 due to the notification from external, but failed. |
异常发生时的恢复动作执行失败 |
请确认可以执行恢复动作的条件 |
● |
● |
● |
|||||
trnsv |
信息 |
2330 |
Action (%1) has been completed. |
要求的动作执行完毕 |
- |
● |
● |
● |
|||||
trnsv |
错误 |
2331 |
Attempted to execute action (%1), but it failed. |
要求的动作执行失败 |
请确认要求动作可以被执行的条件 |
● |
● |
● |
|||||
trnsv |
信息 |
2340 |
Script before action of monitoring %1 has been executed. |
开始执行脚本 |
- |
● |
● |
● |
|||||
trnsv |
信息 |
2341 |
Script before action of monitoring %1 has been completed. |
脚本执行完毕 |
- |
● |
● |
● |
|||||
trnsv |
错误 |
2342 |
Attempted to execute script before action of monitoring %1, but it failed. |
脚本执行失败 |
确认脚本失败的原因,执行相应处理。 |
● |
● |
● |
|||||
trnsv |
错误 |
2350 |
The system will be shutdown because cluster resume was failed. |
恢复失败导致关机 |
- |
● |
● |
● |
|||||
trnsv |
错误 |
2351 |
An attempt to shutdown the system failed. |
关机失败 |
系统可执行无法正常运行。 |
● |
● |
● |
|||||
lanknb |
错误 |
2851 |
Keep-alive timeout was detected on the server %1. |
检出Keep Alive超时。 |
存在检出Keep Alive超时的服务器。请清除服务器的故障。 |
● |
● |
● |
|||||
lankhb |
信息 |
2852 |
STOP error was detected on the server %1. (source:%2, exit code:%3) |
STOP错误 |
存在发生了STOP错误的服务器。请清除服务器的故障。 |
● |
● |
● |
● |
||||
lankhb |
信息 |
2853 |
Hardware reset was detected on the server %1. (source:%2, exit code:%3) |
STOP硬件复位 |
存在发生了硬件复位的服务器。请清除服务器的故障。 |
● |
● |
● |
● |
||||
ptun |
警告 |
3301 |
The parameter (%1) exceeded the threshold (%2 p.c.). Timeout value=%3(sec) Data=%4(sec) |
发生延迟警报 |
参数超出界限值。请将参数设置为适当的值。 |
● |
● |
● |
● |
||||
ptun |
警告 |
3302 |
The parameter (%1) exceeded the threshold (%2 p.c.). Timeout value=%3(sec) Data=%4(sec) Server=%5 Resource=%6 |
发生延迟警报 |
参数超出界限值。请将参数设置为适当的值。 |
● |
● |
● |
● |
||||
lcns |
信息 |
3551 |
The trial license is valid until %1. (Product name:%2) |
试用版License(在试用期间) |
- |
● |
● |
||||||
lcns |
错误 |
3552 |
The trial license has expired in %1. (Product name:%2) |
试用版License(超过试用期间) |
请注册License。 |
● |
● |
● |
● |
||||
lcns |
警告 |
3553 |
The number of licenses is insufficient. The number of insufficient licenses is %1. (Product name:%2) |
License不足。 |
请注册License。 |
● |
● |
● |
|||||
lcns |
错误 |
3554 |
The license is not registered. (Product name:%1) |
未注册License。 |
请注册License。 |
● |
● |
● |
● |
||||
lcns |
错误 |
3555 |
The same license is registered with other servers. (Product name:%1) |
相同License在其他服务器上已被登录。 |
请删除重复License。 |
● |
● |
● |
● |
||||
lcns |
错误 |
3556 |
Manufacturer or model of this server is invalid. |
厂商或者模式不正确。 |
请确认厂商或者模式。 |
● |
● |
● |
● |
||||
lcns |
错误 |
3558 |
The registered license is invalid. (Product name:%1, Serial No:%2) |
License无效 |
请注册有效License。 |
● |
● |
● |
● |
||||
lcns |
信息 |
3559 |
The fixed term license is effective until %1. (Product name:%2) |
期间定制版License(在使用期间) |
- |
● |
● |
● |
|||||
lcns |
错误 |
3560 |
The fixed term license has expired in %1. (Product name:%2) |
期间定制版License(超过使用期间) |
请注册License。 |
● |
● |
● |
● |
||||
logcmd |
信息 |
3601 |
日志命令。 |
- |
● |
× |
× |
× |
× |
× |
× |
× |
|
diskw |
警告 |
3701 |
Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4) |
监视延迟。 |
- |
● |
● |
● |
● |
||||
userw |
警告 |
3711 |
Monitor %1 was delayed. (timeout=%2 response time=%3 rate=%4) |
监视延迟。 |
- |
● |
● |
● |
● |
||||
错误 |
4101 |
mail failed(%1).(SMTP server: %2) |
邮件通知失败。 |
检查SMTP服务器是否发生错误,或者与其通信是否发生错误。 |
● |
● |
● |
● |
|||||
信息 |
4102 |
mail successed.(SMTP server: %1) |
邮件通知成功。 |
- |
● |
● |
|||||||
apisv |
信息 |
4301 |
There was a request to stop cluster from the %1(IP=%2). |
集群停止 |
- |
● |
● |
||||||
apisv |
信息 |
4302 |
There was a request to shutdown cluster from the %1(IP=%2). |
集群关闭 |
- |
● |
● |
||||||
apisv |
信息 |
4303 |
There was a request to reboot cluster from the %1(IP=%2). |
集群重启 |
- |
● |
● |
||||||
apisv |
信息 |
4304 |
There was a request to suspend cluster from the %1(IP=%2). |
集群挂起 |
- |
● |
● |
||||||
apisv |
信息 |
4310 |
There was a request to stop server from the %1(IP=%2). |
集群服务停止 |
- |
● |
● |
||||||
apisv |
信息 |
4311 |
There was a request to shutdown server from the %1(IP=%2). |
关闭 |
- |
● |
● |
||||||
apisv |
信息 |
4312 |
There was a request to reboot server from the %1(IP=%2). |
重启 |
- |
● |
● |
||||||
apisv |
信息 |
4330 |
There was a request to start group(%1) from the %2(IP=%3). |
组启动 |
- |
● |
● |
||||||
apisv |
信息 |
4331 |
There was a request to start all groups from the %1(IP=%2). |
全部组启动 |
- |
● |
● |
||||||
apisv |
信息 |
4332 |
There was a request to stop group(%1) from the %2(IP=%3). |
组停止 |
- |
● |
● |
||||||
apisv |
信息 |
4333 |
There was a request to stop all groups from the %1(IP=%2). |
全部组停止 |
- |
● |
● |
||||||
apisv |
信息 |
4334 |
There was a request to restart group(%1) from the %2(IP=%3). |
组重启 |
- |
● |
● |
||||||
apisv |
信息 |
4335 |
There was a request to restart all groups from the %1(IP=%2). |
全部组重启 |
- |
● |
● |
||||||
apisv |
信息 |
4336 |
There was a request to move group(%1) from the %2(IP=%3). |
组移动 |
- |
● |
● |
||||||
apisv |
信息 |
4337 |
There was a request to move all groups from the %1(IP=%2). |
全部组移动 |
- |
● |
● |
||||||
apisv |
信息 |
4338 |
There was a request to failover group(%1) from the %2(IP=%3). |
组失效切换 |
- |
● |
● |
||||||
apisv |
信息 |
4339 |
There was a request to failover all groups from the %1(IP=%2). |
全部组失效切换 |
- |
● |
● |
||||||
apisv |
信息 |
4340 |
There was a request to migrate group(%1) from the %2(IP=%3). |
组迁移 |
- |
● |
● |
||||||
apisv |
信息 |
4341 |
There was a request to migrate all groups from the %1(IP=%2). |
全部组迁移 |
- |
● |
● |
||||||
apisv |
信息 |
4342 |
There was a request to failover all groups from the %1(IP=%2). |
全部组失效切换 |
- |
● |
● |
||||||
apisv |
信息 |
4343 |
There was a request to cancel waiting for the dependence destination group of group %1 was issued from the %2. |
等待取消 |
- |
● |
● |
||||||
apisv |
信息 |
4350 |
There was a request to start resource(%1) from the %2(IP=%3). |
资源启动 |
- |
● |
● |
||||||
apisv |
信息 |
4351 |
There was a request to start all resources from the %1(IP=%2). |
全部资源启动 |
- |
● |
● |
||||||
apisv |
信息 |
4352 |
There was a request to stop resource(%1) from the %2(IP=%3). |
资源停止 |
- |
● |
● |
||||||
apisv |
信息 |
4353 |
There was a request to stop all resources from the %1(IP=%2). |
全部资源停止 |
- |
● |
● |
||||||
apisv |
信息 |
4354 |
There was a request to restart resource(%1) from the %2(IP=%3). |
资源重启 |
- |
● |
● |
||||||
apisv |
信息 |
4355 |
There was a request to restart all resources from the %1(IP=%2). |
全部资源重启 |
- |
● |
● |
||||||
apisv |
信息 |
4360 |
There was a request to suspend monitor resources from the %1(IP=%2). |
监视暂停 |
- |
● |
● |
||||||
apisv |
信息 |
4361 |
There was a request to resume monitor resources from the %1(IP=%2). |
恢复监视 |
- |
● |
● |
||||||
apisv |
信息 |
4362 |
There was a request to enable Dummy Failure of monitor resource(%1) from the %2(IP=%3). |
开始模拟故障 |
- |
● |
● |
||||||
apisv |
信息 |
4363 |
There was a request to disable Dummy Failure of monitor resource(%1) from the %2(IP=%3). |
停止模拟故障 |
- |
● |
● |
||||||
apisv |
信息 |
4364 |
There was a request to disable Dummy Failure of all monitor resources from the %1(IP=%2). |
停止全部模拟故障 |
- |
● |
● |
||||||
apisv |
错误 |
4401 |
A request to stop cluster was failed(%1). |
集群停止失败 |
请确认集群的状态 |
● |
● |
||||||
apisv |
错误 |
4402 |
A request to shutdown cluster was failed(%1). |
集群关闭失败 |
请确认集群的状态 |
● |
● |
||||||
apisv |
错误 |
4403 |
A request to reboot cluster was failed(%1). |
集群重启失败 |
请确认集群的状态 |
● |
● |
||||||
apisv |
错误 |
4404 |
A request to suspend cluster was failed(%1). |
集群挂起失败 |
请确认集群的状态 |
● |
● |
||||||
apisv |
错误 |
4410 |
A request to stop server was failed(%1). |
集群服务停止失败 |
请确认集群的状态 |
● |
● |
||||||
apisv |
错误 |
4411 |
A request to shutdown server was failed(%1). |
服务器关闭失败 |
请确认服务器的状态 |
● |
● |
||||||
apisv |
错误 |
4412 |
A request to reboot server was failed(%1). |
服务器重启失败 |
请确认服务器的状态 |
● |
● |
||||||
apisv |
错误 |
4430 |
A request to start group(%1) was failed(%2). |
组启动失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4431 |
A request to start all groups was failed(%1). |
全部组启动失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4432 |
A request to stop group(%1) was failed(%2). |
组停止失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4433 |
A request to stop all groups was failed(%1). |
全部组停止失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4434 |
A request to restart group(%1) was failed(%2). |
组重启失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4435 |
A request to restart all groups was failed(%1). |
全部组重启失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4436 |
A request to move group(%1) was failed(%2). |
组移动失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4437 |
A request to move all groups was failed(%1). |
全部组移动失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4438 |
A request to failover group(%1) was failed(%2). |
组失效切换失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4439 |
A request to failover all groups was failed(%1). |
全部组失效切换失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4440 |
A request to migrate group(%1) was failed(%2). |
组迁移失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4441 |
A request to migrate all groups was failed(%1). |
全部组迁移失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4442 |
A request to failover all groups was failed(%1). |
全部组失效切换失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4443 |
A request to cancel waiting for the dependency destination group of group %s has failed(%1). |
等待取消失败 |
请确认组的状态 |
● |
● |
||||||
apisv |
错误 |
4450 |
A request to start resource(%1) was failed(%2). |
资源启动失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4451 |
A request to start all resources was failed(%1). |
全部资源启动失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4452 |
A request to stop resource(%1) was failed(%2). |
资源停止失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4453 |
A request to stop all resources was failed(%1). |
全部资源停止失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4454 |
A request to restart resource(%1) was failed(%2). |
资源重启失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4455 |
A request to restart all resources was failed(%1). |
全部资源重启失败 |
请确认资源的状态 |
● |
● |
||||||
apisv |
错误 |
4460 |
A request to suspend monitor resource was failed(%1). |
监视暂停失败 |
请确认监视资源的状态 |
● |
● |
||||||
apisv |
错误 |
4461 |
A request to resume monitor resource was failed(%1). |
资源恢复失败 |
请确认监视资源的状态 |
● |
● |
||||||
apisv |
错误 |
4462 |
A request to enable Dummy Failure of monitor resource(%1) was failed(%2). |
模拟故障开始失败 |
请确认监视资源的状态 |
● |
● |
||||||
apisv |
错误 |
4463 |
A request to disable Dummy Failure of monitor resource(%1) was failed(%2). |
模拟故障停止失败 |
请确认监视资源的状态 |
● |
● |
||||||
apisv |
错误 |
4464 |
A request to disable Dummy Failure of all monitor resource was failed(%1). |
全部模拟故障停止失败 |
请确认监视资源的状态 |
● |
● |
||||||
apisv |
错误 |
4480 |
Initializing internal communication (%1) failed (port=%2). |
内部通信初始化失败 |
内部通信初始化失败。
请确认ExpressCluster以外的应用程序是否使用该端口。
|
● |
● |
||||||
userw |
警告 |
5001 |
Monitor %1 was delayed.(timeout=%2 response time=%3 rate=%4) |
监视延迟 |
- |
● |
● |
● |
● |
||||
genw |
警告 |
5151 |
The script(%1) was re-activated because it was disappeared.(%2) |
对象脚本重启
%1:脚本名
%2:监视资源名
|
- |
● |
● |
||||||
db2
ftp
http
imap4
odbc
oracle
otx
pop3
psql
smtp
sqlserver
tux
was
wls
|
警告 |
10001 |
%1 |
各个被监视的应用程序的错误消息。 |
根据错误消息处理应用程序错误。 |
● |
× |
× |
× |
× |
× |
× |
× |
db2w
ftpw
httpw
imap4w
odbcw
oraclew
otxw
pop3w
psqlw
smtpw
sqlserverw
tuxw
wasw
wlsw
db2
ftp
http
imap4
odbc
oracle
otx
pop3
psql
smtp
sqlserver
tux
was
wls
|
警告 |
10002 |
The API Error of Windows occurred.%1 |
发生WindowsAPI 错误。%1是API错误代码。 |
根据错误代码处理OS错误。 |
● |
× |
× |
× |
× |
× |
× |
× |
mrw |
警告 |
4901 |
Monitor %1 is in the warning status. (%2 : %3) |
监视警告 |
请确认警告的原因。 |
● |
● |
● |
● |
||||
mrw |
警告 |
4902 |
Configuration of %1 is invalid. (%2 : %3) |
监视资源不正确 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4903 |
Failed to start monitor %1. |
监视启动失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
● |
● |
● |
|
mrw |
错误 |
4904 |
Failed to stop monitor %1. |
监视停止失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4905 |
Monitor %1 detected an error. (%2 : %3) |
监视失败 |
请确认监视异常的原因。 |
● |
● |
● |
● |
● |
● |
● |
|
mrw |
信息 |
4906 |
Monitor resource has not been registered. |
未登录的监视资源 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4907 |
%1 was stopped for failure in monitor %2. |
复归对象停止 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4908 |
%1 was restarted for failure in monitor %2. |
重启复归对象 |
- |
● |
● |
● |
|||||
mrw |
情報 |
4909 |
%1 was failed over for failure in monitor %2. |
复归对象组 失效切换 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4910 |
There was a request to stop cluster for failure in monitor %1. |
集群停止 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4911 |
There was a request to shut down the system for failure in monitor %1. |
系统关闭 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4912 |
There was a request to restart the system for failure in monitor %1. |
系统重启 |
- |
● |
● |
● |
|||||
mrw |
错误 |
4913 |
Failed to stop %1 due to error detection of %2. |
复归对象停止失败 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4914 |
Failed to restart %1 due to error detection of %2. |
复归对象重启失败 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4915 |
Failed to fail over %1 due to error detection of %2. |
复归对象组 失效切换失败 |
请确认资源的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4916 |
Failed to stop the cluster due to error detection of %1. |
集群停止失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4917 |
Failed to shut down the system due to error detection of %1. |
OS关闭失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4918 |
Failed to restart the system due to error detection of %1. |
OS重启失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
错误 |
4919 |
The group of monitor %1 is unknown. |
所属组不明 |
请确认集群配置信息。 |
● |
● |
● |
● |
||||
mrw |
警告 |
4920 |
No action is taken because %1 is not online. |
不执行复归动作 |
- |
● |
● |
● |
● |
||||
mrw |
信息 |
4921 |
Status of monitor %1 was returned to normal. |
状态正常 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4922 |
Status of monitor %1 was changed into unknown. |
状态不明 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
|||||
mrw |
错误 |
4923 |
Initialization error has occurred (%1 : %2) |
进程初始化异常 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
信息 |
4924 |
Causing intentional stop error was required because an error is detected by %1. |
停止错误的发生 |
- |
● |
● |
● |
|||||
mrw |
错误 |
4925 |
Causing intentional stop error has failed because an error is detected by %1. |
停止错误的发生 失败 |
系统可执行处于不能正常运行的状态。 |
● |
● |
● |
● |
||||
mrw |
警告 |
4926 |
Recovery will not be executed since server is suspending. |
不执行复归动作(服务器保留) |
服务器的状态为保留 (NP 未解决) 时,不执行监视资源复归动作。确认保留 (NP 未解决) 的原因,将NP资源设置为正常状态。 |
● |
● |
● |
● |
||||
mrw |
警告 |
4927 |
Shutdown count reached the maximum number (%1). Final action of monitor %2 was ignored. |
达到关闭次数的上限 |
- |
● |
● |
● |
● |
● |
● |
● |
|
mrw |
信息 |
4928 |
Script before action(%1) upon failure in %2 monitor resource started. |
监视资源异常时,开始最终动作前脚本 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4929 |
Script before action(%1) upon failure in %2 monitor resource completed. |
监视资源异常时,结束最终动作前脚本 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4930 |
Script before action(%1) upon failure in %2 monitor resource failed. |
监视资源异常时,最终动作前脚本失败 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4931 |
Recovery script has executed because an error was detected in monitoring %1. |
复归脚本结束 |
- |
● |
● |
● |
|||||
mrw |
错误 |
4932 |
Attempted to execute recovery script due to the error detected in monitoring %1, but failed. |
复归脚本失败 |
确认复归脚本失败的原因,采进行处理。 |
● |
● |
● |
|||||
mrw |
警告 |
4933 |
Ignored the recovery action in monitoring %1 because recovery action caused by monitor resource error is disabled. |
为了控制监视资源异常时的复归动作,不执行复归动作。 |
- |
● |
● |
● |
|||||
mrw |
信息 |
4934 |
There was a notification (%1) from external. (detail: %2) |
接收来自外部的异常发生通知 |
- |
● |
● |
● |
|||||
tuxw |
警告 |
10004 |
The API Error of Application occurred.%1 |
发生应用程序API 错误。%1是API错误代码。 |
根据错误代码处理应用程序错误。 |
● |
|||||||
jra |
错误 |
20251 |
Failed to start Java Resource Agent(%1) |
发生了内部错误。
%1:内部错误代码
|
请确认JVM监视资源的运行状况。如果JVM监视资源未启动,请重启服务器。 |
● |
|||||||
jra |
错误 |
20252 |
Failed to start Java Resource Agent(%1) |
指定的设置值不正确。
%1:内部错误代码
|
请确认设置的Java安装路径是都正确。 |
● |
|||||||
sra |
错误 |
20301 |
Service was terminated because reading an SG file failed. |
在设置文件的读取处理中发生了异常。 |
请确认另外输出的消息 |
● |
|||||||
sra |
错误 |
20302 |
The installation folder name could not be acquired. |
获取安装文件夹失败。 |
请重启集群或者执行挂起/复原。 |
● |
|||||||
sra |
错误 |
20305 |
No IModules could be loaded. |
执行本产品所需的文件的一部分不存在,因此不能启动。 |
请重装本产品。 |
● |
|||||||
sra |
错误 |
20306 |
An unexpected error occurred. |
已启动本产品,但是由于某原因不能启动。 |
请重启集群或者执行挂起/复原。 |
● |
|||||||
sra |
错误 |
20307 |
Internal error occurred. |
本产品异常结束。 |
请参照之前输出的系统日志消息。 |
● |
|||||||
sra |
错误 |
20308 |
An error has occurred in issuing WMI. %1(ErrorID:0x%2 class:%3)
%1: Message
%2: Error code
%3: Information that could not be acquired
|
无法获取统计信息。
%1:消息
%2:错误代码
%3:不能获取的信息
|
请重启集群或者执行挂起/复原。 |
● |
|||||||
sra |
警告 |
20336 |
Script is timeout. (%1 %2)
%1: Script file name
%2: Argument
|
发生了内部错误。 |
请确认服务器的负载状况,消除负载。 |
● |
|||||||
sra |
信息 |
20346 |
%1 event succeeded.
%1: Event type (Boot, Shutdown, Stop, Start, or Flush)
|
执行运用管理名命令。
%1为输出执行的事件种类(Boot,Shutdown,Stop,Start,Flush)。
|
- |
● |
|||||||
sra |
警告 |
20347 |
%1 was smaller than %2, it changed to minimum value(%3). |
监视的设定值不正确。
%1:设置项目
%2:设置项目
%3:设定值
|
请通过Cluster WebUI确认设定值。 |
● |
|||||||
sra |
警告 |
20348 |
%1 was too long compared with %2, it changed to %1(%3). |
监视的设置值不正确。
%1:设置项目
%2:设置项目
%3:设置值
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20349 |
%1 was smaller than %2, it changed to %2 value(%3).(%4) |
监视的设置值不正确。
%1:设置项目
%2:设置项目
%3:设置值
%4:监视资源名
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20350 |
%1 was larger than %2, it changed to %2 value(%3).(%4) |
监视的设置值不正确。
%1:设置项目
%2:设置项目
%3:设置值
%4:监视资源名
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20351 |
%1 was over than Total disk size, (%2 %3). |
监视的设置值不正确。
%1:设置项目
%2:监视资源名
%3:设置值
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20352 |
%1 was over than Total disk size, (%2 %3). |
监视的设置值不正确。
%1:设置项目
%2:监视资源名
%3:设置值
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20353 |
Delete MOUNT[%1] in DiskCapacity list.(%2) |
监视的设置值不正确。
%1:设置值
%2:监视资源名
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20354 |
%1 was illegal value (%2).(%3) |
监视的设置值不正确。
%1:设置项目
%2:设置值
%3:监视资源名
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
警告 |
20355 |
The DriveLetter of %1 is not ready, or Drive type was not fixed.(%2 DriveLetter = %3) |
监视的设置值不正确。
%1:设置项目
%2:监视资源名
%3:设置值
|
请通过Cluster WebUI确认设置值。 |
● |
|||||||
sra |
错误 |
20358 |
A process resource error was detected. (%1 type = cpu, pid = %2, %3) |
特定进程的CPU使用率监视中查出异常。
%1:监视资源名
%2:进程ID
%3:进程名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20358 |
A process resource error was detected. (%1 type = memory leak, pid = %2, %3) |
特定进程的内存使用量监视中查出异常。
%1:监视资源名
%2:进程ID
%3:进程名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20358 |
A process resource error was detected. (%1 type = file leak, pid = %2, %3) |
特定进程的打开文件数监视中查出异常。
%1:监视资源名
%2:进程ID
%3:进程名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20358 |
A process resource error was detected. (%1 type = thread leak, pid = %2, %3) |
特定进程的线程数监视中查出异常。
%1:监视资源名
%2:进程ID
%3:进程名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20358 |
A process resource error was detected. (%1 type = same name process, pid = %2, %3) |
同一名进程监视中查出异常。
%1:监视资源名
%2:进程ID
%3:进程名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20359 |
A system resource error was detected. (%1 type = cpu) |
系统的CPU使用率监视中查出异常。
%1:监视资源名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20359 |
A system resource error was detected. (%1 type = memory) |
系统的总内存使用量监视中查出异常。
%1:监视资源名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20359 |
A system resource error was detected. (%1 type = swap) |
系统的总虚拟内存使用量监视中查出异常。
%1:监视资源名
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20360 |
A disk resource error was detected. (%1 type = used rate, level = NOTICE, %2) |
磁盘使用率监视中查出通知级别异常。
%1:监视资源名
%2:逻辑驱动器
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20360 |
A disk resource error was detected. (%1 type = used rate, level = WARNING, %2) |
磁盘使用率监视中查出警告级别的异常。
%1:监视资源名
%2:逻辑驱动器
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20360 |
A disk resource error was detected. (%1 type = free space, level = NOTICE, %2) |
磁盘空余容量监视中查出通知级别的异常。
%1:监视资源名
%2:逻辑驱动器
|
请确认监视异常的原因。 |
● |
● |
||||||
sra |
错误 |
20360 |
A disk resource error was detected. (%1 type = free space, level = WARNING, %2) |
磁盘空余容量监视中查出警告级别的异常。
%1:监视资源名
%2:逻辑驱动器
|
请确认监视异常的原因。 |
● |
● |
||||||
webmgr |
警告 |
5121 |
HTTPS configuration isn't correct, HTTPS mode doesn't work. Please access WebManager by HTTP mode. |
HTTPS 设置不正确 |
- |
● |
● |
● |
|||||
sss |
错误 |
20004 |
系统驱动器字符获取失败。 |
系统驱动器字符获取失败。 |
系统可执行处于无法正常运行的状态。 |
● |
|||||||
sss |
错误 |
20005 |
服务器名取得失败。 |
服务器名取得失败。 |
系统可执行处于无法正常运行的状态。 |
● |
|||||||
sss |
信息 |
20006 |
服务器名取得失败。 |
服务器名取得失败。 |
- |
● |
● |
||||||
sss |
错误 |
20007 |
配置文件的更新失败。 |
配置文件的更新失败。 |
请确认集群配置信息。 |
● |
● |
||||||
sss |
信息 |
20008 |
配置文件被更新。 |
配置文件被更新。 |
- |
● |
|||||||
sss |
错误 |
20009 |
配置文件的内容无效。 |
配置文件的内容无效。 |
请确认集群配置信息。 |
● |
|||||||
sss |
错误 |
20010 |
%1无法启动服务。 |
%1无法启动服务。 |
系统可执行处于无法正常运行的状态。 |
● |
● |
||||||
sss |
信息 |
20012 |
%1服务启动了。 |
%1服务启动了。 |
- |
● |
|||||||
sss |
信息 |
20013 |
%1服务停止了。 |
%1服务停止了。 |
- |
● |
|||||||
sss |
信息 |
20014 |
启动了LAN卡的双重化模块。 |
启动了LAN卡的双重化模块。 |
可执行是内存不足或OS资源不足。请确认。 |
● |
|||||||
sss |
错误 |
20015 |
启动了LAN卡的双重化模块。 |
启动了LAN卡的双重化模块。 |
- |
● |
● |
||||||
ncctl |
错误 |
20101 |
查出LAN卡%1的异常。 |
查出LAN卡%1的异常。 |
确认是否适当设置了待机中的LAN卡。 |
● |
● |
||||||
ncctl |
警告 |
20102 |
LAN卡%1切换为LAN卡%2。 |
LAN卡%1切换为LAN卡%2。 |
- |
● |
● |
||||||
ncctl |
错误 |
20103 |
LAN卡%1的操作失败了。 |
LAN卡%1的操作失败了。 |
- |
● |
● |
4.3. 驱动程序事件日志消息¶
4.3.1. 内核模式LAN心跳驱动程序¶
以下事件在系统事件日志中通过"clphb"记录。
模块类型 |
事件分类 |
事件ID |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
clphb |
错误 |
3001 |
Fatal error occurred in the driver. |
在驱动程序内部发生致命的错误。 |
可执行是内核内存不足,OS资源不足。请用性能监视器确认。 |
clphb |
信息 |
1001 |
Signal has been set to the shutdown event due to the keep alive timeout. |
用户空间处于停止状态。 |
可执行是内存不足,OS资源不足。请确认。 |
clphb |
信息 |
1002 |
Signal has been set to the shutdown event due to the FILTER closing action. |
接受关闭FILTER口的动作。 |
可执行是内核内存不足,OS资源不足。请用性能监视器确认。 |
4.4. 组资源启动/停止时的详细信息¶
以下信息在资源启动或停止处理失败时作为记录到事件日志和警报日志中的消息内的详细信息来显示。
4.4.1. 应用程序资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
appli |
错误 |
5 |
The application path is invalid. |
应用程序的路径无效。 |
请确认应用程序的路径是否正确。 |
appli |
错误 |
7 |
Failed to start application. |
应用程序的启动失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
appli |
错误 |
8 |
Failed to stop application. |
应用程序的停止失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
appli |
错误 |
10 |
Timeout occurred. |
发生超时。 |
请确认应用程序是否在超时时间内退出。 |
appli |
错误 |
11 |
Failed to log on as a user. |
用户登录失败。 |
请确认执行用户的域,帐号,密码是否正确设置。 |
appli |
错误 |
12 |
Returned termination code %1. |
非常驻型程序返回了非法终止代码。 |
请确认程序返回非法终止代码的原因。 |
appli |
错误 |
其他 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.4.2. 脚本资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
script |
错误 |
6 |
Failed to execute start script. |
开始脚本的启动失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
script |
错误 |
7 |
Failed to execute stop script. |
结束脚本的启动失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
script |
错误 |
8 |
Returned termination code %1. |
同步类型脚本返回了非法终止代码。 |
请确认脚本返回非法终止代码的原因。 |
script |
错误 |
9 |
Timeout occurred. |
发生超时。 |
请确认脚本是否在超时时间内结束。 |
script |
错误 |
10 |
Failed to log on as a user. |
用户登录失败。 |
请确认执行用户的域,账号,密码是否设置正确。 |
script |
错误 |
其他 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.4.3. 服务资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
service |
错误 |
5 |
Failed to get service control right. |
服务控制权的获取失败。 |
请确认服务名是否正确。 |
service |
错误 |
6 |
Failed to start service. |
服务的启动失败。 |
请确认服务的状态。 |
service |
错误 |
7 |
Failed to stop service. |
服务的停止失败。 |
请确认服务的状态。 |
service |
错误 |
8 |
Service has already been running. |
服务已经启动。 |
请确认服务的状态。如果服务启动完毕,可执行是没有将其作为错误设置。 |
service |
错误 |
10 |
Timeout occurred. |
发生超时。 |
请确认服务是否在超时时间内开始或停止。 |
service |
错误 |
13 |
Computer name related to service that is running is different from virtual computer name of target VCOM resource. |
正在启动的服务相关联的计算机名和对象VCOM资源的虚拟计算机名不同。 |
如果在多个服务资源中设置相同服务,请不要设置对象VCOM资源名。 |
service |
错误 |
其他 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5. 监视资源异常时的详细信息¶
以下信息在查出监视资源异常时作为输出到事件日志和警报日志中的消息内的详细信息而显示。
4.5.1. 应用程序监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
appliw |
错误 |
9 |
Process did not exist.(Exit code:%1) |
不存在进程。(仅限无法获取结束码时显示。) |
由于某种原因,监视对象应用程序资源的进程消失。请确认。 |
appliw |
错误 |
11 |
Failed to log on as a user. |
用户的登录失败。 |
请确认执行用户的域,帐号,密码是否正确设置。 |
appliw |
警告 |
其他 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.2. DB2监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
db2w |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。可执行是内存分配等的失败。
%1中可执行显示初始化的内容。
|
可执行是由于OS自身异常,请重新启动服务器。 |
db2w |
警告 |
102 |
The configured value is not correct. |
监视的设置值不正确。 |
可执行是由于在Cluster WebUI上的设置值不正确,请确认设置值。 |
db2w |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或者OS异常。请确认系统状态。 |
db2w |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(数据库名等)。如果没有问题,请确认数据库是否异常。 |
db2w |
警告 |
112 |
An error was detected in user authentication. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认数据库是否异常。 |
db2w |
警告 |
113 |
An application error was detected. |
检出数据库异常。 |
请参考另外显示的数据库错误消息,清除故障。 |
db2w |
错误 |
14 |
An error was detected in executing SQL statement [%1]. |
SQL文的执行失败。
%1中将显示执行的SQL文。
|
请参考另外显示的数据库错误消息,清除故障。 |
db2w |
错误 |
15 |
A data error was detected. |
数据库表内的值异常。 |
数据库可执行破损,请中止数据库的运行进行调查。另外,用相同监视表名同时执行多个监视也可执行发生错误。请特别确认双向环境的设置值是否有问题。 |
db2w |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
db2w |
警告 |
160 |
Failed to obtain the configuration data. |
显示无法获取设置值。 |
可执行OS异常,请重新启动服务器等。 |
db2w |
警告 |
190 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.3. 磁盘RW监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
diskw |
错误 |
5 |
Failed to open the file. |
文件打开处理失败。 |
请确认是否已经加载监视目标磁盘的设备驱动,是否存在监视目标磁盘的设备,监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是内存不足或者OS的资源不足。请确认。
|
diskw |
错误 |
6 |
Failed to write in the file. |
文件写入处理失败。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是内存不足或者OS的资源不足。请确认。
|
diskw |
错误 |
7 |
Failed to synchronize the disk of the file. |
文件的磁盘同步处理失败。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是内存不足或者OS的资源不足。请确认。
|
diskw |
错误 |
8 |
Failed to close the file. |
文件关闭处理失败。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是内存不足或者OS的资源不足。请确认。
|
diskw |
错误 |
71 |
Timeout has occurred when opening the file. |
文件打开处理检出超时。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是系统高负荷,内存不足,或者OS的资源不足。请确认。
|
diskw |
错误 |
72 |
Timeout has occurred when writing in the file. |
文件写入处理检出超时。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是系统高负荷,内存不足,或者OS的资源不足。请确认。
|
diskw |
错误 |
73 |
Timeout has occurred when synchronizing the disk of the file. |
文件的磁盘同步处理检出超时。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是系统高负荷,内存不足,或者OS的资源不足。请确认。
|
diskw |
错误 |
74 |
Timeout has occurred when closing the file. |
文件关闭处理检出超时。 |
请确认监视目标磁盘连接是否正确,监视目标磁盘的电源是否打开,或者监视目标磁盘上是否有其他异常发生。
可执行是系统高负荷,内存不足,或者OS的资源不足。请确认。
|
diskw |
警告 |
100 |
Failed to add keep alive drive when initializing keep alive driver. |
由于Keep Alive驱动程序的初始化处理,Keep Alive的添加失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
diskw |
警告 |
101 |
There is not enough disk space. |
磁盘空间不足。 |
请确认监视对象磁盘空间是否足够。 |
diskw |
警告 |
102 |
Timeout has occurred when initializing internal resources. |
内部资源的初始化处理检出超时。 |
可执行是内存不足或者OS的资源不足。请确认。 |
diskw |
警告 |
103 |
Timeout has occurred when other timing. |
检测到由于其他不一致导致的超时。 |
系统可执行处于高负荷或者内存或OS资源可执行不足。请进行检查。 |
diskw |
警告 |
104 |
Failed to allocate memory. |
内存空间的分配失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
diskw |
警告 |
105 |
Internal error occurred. |
检出其他内部异常。 |
可执行是内存不足或者OS的资源不足。请确认。 |
diskw |
警告 |
190 |
Initialization error has occurred in internal resource. |
内部资源的初始化发生异常。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.4. FTP监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
ftpw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,请确认监视应用程序是否异常。 |
ftpw |
错误 |
12 |
An error was detected in user authentication. |
用户认证失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
ftpw |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
ftpw |
警告 |
113 |
An application error was detected. |
检出监视应用程序的异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
ftpw |
警告 |
115 |
A data error was detected. |
应答数据的值异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
ftpw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
ftpw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
ftpw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.5. 自定义监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
genw |
错误 |
5 |
Failed to start script. |
脚本启动失败。 |
请确认脚本是否可以启动。 |
genw |
错误 |
6 |
Script did not exist. |
非同步类型的脚本异常结束。 |
请确认脚本结束的原因。 |
genw |
错误 |
8 |
Returned termination code %1. |
同步类型的脚本返回了不正确的结束代码。 |
请确认脚本返回不正确的结束代码的原因。 |
genw |
错误 |
9 |
Failed to log on as a user. |
用户登录失败。 |
请确认执行用户的域,账号,密码是否设置正确。 |
genw |
警告 |
100 |
Failed to start script. |
脚本启动失败。 |
请确认脚本是否可以启动。 |
genw |
警告 |
100 |
Returned termination code %1. |
同步类型的脚本返回了不正确的退出码。 |
请确认脚本返回不正确的退出码的原因。 |
genw |
警告 |
100
190
|
Script path is invalid. |
脚本的路径不正确。 |
请通过Cluster WebUI确认设定值。 |
genw |
警告 |
100
190
|
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
genw |
警告 |
190 |
Parameter is invalid. |
监视的设定值不正确。 |
请通过Cluster WebUI确认设定值。 |
genw |
警告 |
190 |
Resource does not exist in cluster configuration data. |
集群配置信息不正确。 |
请通过Cluster WebUI确认配置信息。 |
genw |
警告 |
190 |
Failed to get the value from cluster configuration data. |
集群配置信息不正确。 |
请通过Cluster WebUI确认配置信息。 |
genw |
警告 |
190 |
Script did not exist. |
非同步类型的脚本异常退出。 |
请确认脚本退出的原因。 |
genw |
错误 |
200 |
Timeout occurred. |
同步类型的脚本在超时时间内没有结束。 |
请确认脚本结束延迟的原因。 |
4.5.6. HTTP监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
httpw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,请确认监视应用程序是否异常。 |
httpw |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
httpw |
警告 |
113 |
An application error was detected. |
检出监视应用程序的异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
httpw |
警告 |
115 |
A data error was detected. |
应答数据的值异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
httpw |
警告 |
116 |
The algorithm is not supported. (%1) |
不支持的算法。
%1中包含算法。
|
- |
httpw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
httpw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
httpw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值的失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.7. IMAP4监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
imap4w |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,请确认监视应用程序是否异常。 |
imap4w |
错误 |
12 |
An error was detected in user authentication. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
imap4w |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
imap4w |
警告 |
113 |
An application error was detected. |
检出监视应用程序的异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
imap4w |
警告 |
115 |
A data error was detected. |
应答数据的值异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
imap4w |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
imap4w |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
imap4w |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.8. IP监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
ipw |
错误 |
4 |
Ping could not reach. |
Ping不通。 |
请确认该IP地址的[ping]命令是否成功。如果[ping]命令失败,请确认拥有该IP地址的机器状态,或者网络界面的状态。 |
ipw |
警告 |
105 |
Timeout occurred. |
发生超时。 |
可执行是内存不足或者OS的资源不足。请确认。 |
ipw |
警告 |
189 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.9. NIC Link Up/Down监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
miiw |
错误 |
4 |
IP address does not exist. |
IP地址不存在。 |
可执行已经将NIC设为无效。请用[ipconfig]命令确认指定NIC的IP地址是否存在。 |
miiw |
错误 |
8 |
Detected NIC Link Down. |
检出NIC的Link Down。 |
请确认LAN线缆是否正确连接。 |
miiw |
警告 |
105 |
Failed to get IP address table. |
IP地址一览的获取失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
miiw |
警告 |
106 |
Failed to get the NIC interface name. |
NIC接口名称的获取失败。 |
可执行是内存不足或者OS的资源不足。请确认。 |
miiw |
警告 |
107 |
Failed to get the NIC status. |
NIC状态的获取失败。 |
确保NIC设备支持设备I/O控制。 |
miiw |
警告 |
189 |
An internal error has occurred. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.10. 多任务监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
mtw |
错误 |
其他 |
Internal error occurred.(status:%1) |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
mtw |
错误 |
5 |
Status of resources is abnormal. |
资源的状态异常。 |
请确认监视资源一览内设置的监视资源的状态。 |
mtw |
错误 |
1 |
This option is invalid. |
无效选项。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.11. 进程名监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
psw |
错误 |
4 |
Process [%1, pid=%2] down. |
查出监视对象进程消失。 |
请确认监视对象进程是否正常运行。 |
psw |
错误 |
5 |
The number of processes to be monitored is less than the minimum process count. Process cout %1/%2 (%3) |
监视对象进程的启动进程数低于指定的下限值。 |
请确认监视对象进程是否正常运行。 |
psw |
警告 |
100 |
Internal error occurred. |
发生内部错误。 |
可执行是内存不足或OS资源不足。请确认。 |
psw |
警告 |
190 |
Parameter is invalid. |
监视的设置值不正确。 |
可执行是Cluster WebUI中的设置值不正确,请确认设置值。 |
4.5.12. ODBC监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
odbcw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。可执行是内存分配等的失败。
%1中将可执行显示初始化的内容。
|
由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
odbcw |
警告 |
102 |
The configured value is not correct. |
监视的设置值不正确。 |
可执行Cluster WebUI上的设置值不正确,请确认。 |
odbcw |
警告 |
110 |
A function error was detected. |
函数发生异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
odbcw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(数据库名等)。如果没有问题,请确认监视应用程序是否异常。 |
odbcw |
警告 |
112 |
An error was detected in user authentication. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
odbcw |
警告 |
113 |
An application error was detected. |
检出数据库异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
odbcw |
错误 |
14 |
An error was detected in executing SQL statement [%1]. |
SQL文的执行失败。
%1中将显示执行的SQL文。
|
请参考另外显示的监视应用程序的错误消息,清除故障。 |
odbcw |
错误 |
15 |
A data error was detected. |
数据库表内的值异常。 |
数据库可执行破损,请中止数据库的运行进行调查。另外,用相同监视表名同时执行多个监视也可执行发生错误。请特别确认双向环境的设置值是否有问题。 |
odbcw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
odbcw |
警告 |
160 |
Failed to obtain the configuration data. |
显示无法获取设置值。 |
由于OS可执行处于异常状态,请执行重启服务器等操作。 |
odbcw |
警告 |
190 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.13. Oracle监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
oraclew |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。可执行是内存分配等的失败。
%1中可执行显示初始化的内容。
|
由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
oraclew |
警告 |
102 |
The configured value is not correct. |
监视的设置值不正确。 |
可执行Cluster WebUI上的设置值不正确,请确认。 |
oraclew |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
oraclew |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(数据库名等)。如果没有问题,请确认监视应用程序是否异常。 |
oraclew |
警告 |
112 |
An error was detected in user authentication. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
oraclew |
警告 |
113 |
An application error was detected. |
检出数据库异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
oraclew |
错误 |
14 |
An error was detected in executing SQL statement [%1]. |
SQL文的执行失败。
%1中将显示执行的SQL文。
|
请参考另外显示的监视应用程序的错误消息,清除故障。 |
oraclew |
错误 |
15 |
A data error was detected. |
数据库表内的值异常。 |
数据库可执行破损,请中止数据库的运行进行调查。另外,用相同监视表名同时执行多个监视也可执行发生错误。请特别确认双向环境的设置值是否有问题。 |
oraclew |
警告 |
140 |
No license is registered. |
未注册License。 |
未注册License。 |
oraclew |
警告 |
160 |
Failed to obtain the configuration data. |
显示无法获取设置值。 |
由于OS可执行处于异常状态,请执行重启服务器等操作。 |
oraclew |
警告 |
190 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.14. POP3监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
pop3w |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,请确认监视应用程序是否异常。 |
pop3w |
错误 |
12 |
An error was detected in user authentication. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
pop3w |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
pop3w |
警告 |
113 |
An application error was detected. |
检出监视应用程序的异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
pop3w |
警告 |
115 |
A data error was detected. |
应答数据的值异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
pop3w |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
pop3w |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
pop3w |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.15. PostgreSQL监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
psqlw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。可执行是内存分配等的失败。
%1中可执行显示初始化的内容。
|
由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
psqlw |
警告 |
102 |
The configured value is not correct. |
监视的设置值不正确。 |
可执行Cluster WebUI上的设置值不正确,请确认。 |
psqlw |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
psqlw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(数据库名等)。如果没有问题,请确认监视应用程序是否异常。 |
psqlw |
警告 |
112 |
An error was detected in user authentication. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
psqlw |
警告 |
113 |
An application error was detected. |
检出数据库异常。 |
请参考另外显示的数据库的错误消息,清除故障。 |
psqlw |
错误 |
14 |
An error was detected in executing SQL statement [%1]. |
SQL文的执行失败。
%1中将显示执行的SQL文。
|
请参考另外显示的数据库的错误消息,清除故障。 |
psqlw |
错误 |
15 |
A data error was detected. |
数据库表内的值异常。 |
数据库可执行破损,请中止数据库的运行进行调查。另外,用相同监视表名同时执行多个监视也可执行发生错误。请特别确认双向环境的设置值是否有问题。 |
psqlw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
psqlw |
警告 |
160 |
Failed to obtain the configuration data. |
显示无法获取设置值。 |
由于OS可执行处于异常状态,请执行重启服务器等操作。 |
psqlw |
警告 |
190 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.16. 服务监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
servicew |
错误 |
9 |
Service has been stopped. |
服务处于停止状态。 |
请确认服务的状态。 |
servicew |
警告 |
100 |
Failed to obtain the service control right. |
服务控制权的获取失败。 |
请确认服务名是否正确。 |
servicew |
警告 |
其他 |
An internal error has occurred. |
发生内部错误。 |
可执行是内存不足或OS的资源不足。请确认。 |
4.5.17. SMTP监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
smtpw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,请确认监视应用程序是否异常。 |
smtpw |
错误 |
12 |
An error was detected in user authentication. |
连接监视应用程序失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
smtpw |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
smtpw |
警告 |
113 |
An application error was detected. |
检出监视应用程序的异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
smtpw |
警告 |
115 |
A data error was detected. |
应答数据的值异常。 |
请参考另外显示的监视应用程序的错误消息,清除故障。 |
smtpw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
smtpw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
smtpw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值的失败。 |
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。
%1中显示初始化的内容。
|
4.5.18. SQL Server监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
sqlserverw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。可执行是内存分配等的失败。
%1中可执行显示初始化的内容。
|
由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
sqlserverw |
警告 |
102 |
The configured value is not correct. |
监视的设置值不正确。 |
可执行Cluster WebUI上的设置值不正确,请确认。 |
sqlserverw |
警告 |
110 |
A function error was detected. |
发生函数异常。 |
可执行监视应用程序或OS处于异常状态。请确认系统状态。 |
sqlserverw |
错误 |
11 |
An error was detected in accessing the monitor target. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(数据库名等)。如果没有问题,请确认监视应用程序是否异常。 |
sqlserverw |
警告 |
112 |
An error was detected in user authentication. |
连接数据库失败。 |
首先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,请确认监视应用程序是否异常。 |
sqlserverw |
警告 |
113 |
An application error was detected. |
检出数据库异常。 |
请参考另外显示的数据库的错误消息,清除故障。 |
sqlserverw |
错误 |
14 |
An error was detected in executing SQL statement [%1]. |
SQL文的执行失败。
%1中将显示执行的SQL文。
|
请参考另外显示的数据库的错误消息,清除故障。 |
sqlserverw |
错误 |
15 |
A data error was detected. |
数据库表内的值异常。 |
数据库可执行破损,请中止数据库的运行进行调查。另外,用相同监视表名同时执行多个监视也可执行发生错误。请特别确认双向环境的设置值是否有问题。 |
sqlserverw |
警告 |
140 |
No license is registered. |
未注册License。 |
请注册License。 |
sqlserverw |
警告 |
160 |
Failed to obtain the configuration data. |
显示无法获取设置值。 |
由于OS可执行处于异常状态,请执行重启服务器等操作。 |
sqlserverw |
警告 |
190 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
4.5.19. Tuxedo监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
tuxw |
错误 |
11 |
An error was detected in accessing the monitor target. |
监视应用程序连接失败。 |
先确认Cluster WebUI的设置值(TUXCONFIG文件等)。如果没有问题,再确认是否有监视应用程序的异常。 |
tuxw |
警告 |
110 |
A function error was detected. |
函数发生了异常。 |
可执行是监视应用程序或者是OS异常状态。请确认系统状态。 |
tuxw |
警告 |
113 |
An application error was detected. |
检测出监视应用程序的异常。 |
请参考其他表示的监视应用程序错误信息,清除故障。 |
tuxw |
警告 |
140 |
No license is registered. |
License未注册。 |
请注册License。 |
tuxw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
tuxw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值的失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.20. WebSphere监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
wasw |
错误 |
12 |
An error was detected in user authentication. |
监视应用程序连接失败。 |
先确认Cluster WebUI的设置值(TUXCONFIG文件等)。如果没有问题,再确认是否有监视应用程序的异常。 |
wasw |
警告 |
110 |
A function error was detected. |
函数发生了异常。 |
可执行是监视应用程序或者是OS异常状态。请确认系统状态。 |
wasw |
警告 |
113 |
An application error was detected. |
检测出监视应用程序的异常。 |
请参考其他表示的监视应用程序错误信息,排除故障。 |
wasw |
警告 |
140 |
No license is registered. |
License未注册。 |
请注册License。 |
wasw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
wasw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.21. WebLogic监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
wlsw |
错误 |
11 |
An error was detected in accessing the monitor target. |
监视应用程序连接失败。 |
先确认Cluster WebUI的设置值(IP地址等)。如果没有问题,再确认是否有监视应用程序的异常。 |
wlsw |
错误 |
12 |
An error was detected in user authentication. |
监视应用程序连接失败。 |
先确认Cluster WebUI的设置值(用户名,密码等)。如果没有问题,再确认是否有监视应用程序的异常。 |
wlsw |
警告 |
110 |
A function error was detected. |
函数发生了异常。 |
可执行是监视应用程序或者是OS异常状态。请确认系统状态。 |
wlsw |
警告 |
113 |
An application error was detected. |
检测出监视应用程序的异常。 |
请参考其他表示的监视应用程序错误信息,消除故障。 |
wlsw |
警告 |
140 |
No license is registered. |
License未注册。 |
请注册License。 |
wlsw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
wlsw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值的失败。
%1中可执行显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.22. WebOTX监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
otxw |
错误 |
11 |
An error was detected in accessing the monitor target. |
监视应用程序访问失败。 |
先确认Cluster WebUI的设置值(例如服务器名)。如果没有问题,再确认是否有监视应用程序的异常 |
otxw |
错误 |
12 |
An error was detected in user authentication. |
监视应用程序访问失败。 |
先确认Cluster WebUI的设置值(例如用户名或密码)。如果没有问题,再确认是否有监视应用程序的异常 |
otxw |
警告 |
110 |
A function error was detected. |
函数发生了异常。 |
可执行是监视应用程序或者是OS异常状态。请确认系统状态。 |
otxw |
警告 |
113 |
An application error was detected. |
检测出监视应用程序的异常。 |
请参考另外显示的监视应用程序错误信息,排除故障。 |
otxw |
警告 |
140 |
No license is registered. |
License未注册。 |
请注册License。 |
otxw |
警告 |
188 |
Internal error. |
发生内部错误。 |
可执行是内存不足或者OS的资源不足。请确认。 |
otxw |
警告 |
190 |
Initialization has failed[%1]. |
初始化处理失败。原因可执行是内存分配或取得设定值失败。
%1中显示初始化的内容。
|
可执行Cluster WebUI上的设置值不正确,请确认。设置值正确时,由于OS自身可执行处于异常状态,请执行重启服务器等操作。 |
4.5.23. JVM 监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
jraw |
错误 |
11 |
An error was detected in accessing the monitor target. |
无法连接监视对象 |
请确认监视对象Java VM是否已启动。 |
jraw |
错误 |
12 |
JVM status changed to abnormal. cause = %1. |
在Java VM的监视中查出异常 |
请根据消息,确认在监视对象Java VM上运行的Java应用程序。 |
jraw |
警告 |
192 |
Internal error occurred. |
发生内部错误 |
请执行集群挂起和集群复原。 |
4.5.24. 系统监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
sraw |
错误 |
11 |
Monitor sraw has detected an error. (11: A system resource error has been detected.) |
在系统资源的监视中查出异常。 |
资源出现某种异常。请确认。 |
4.5.25. 进程资源监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
psrw |
错误 |
11 |
Monitor psrw has detected an error. (11: Detected an error in monitoring process resource.) |
在进程资源的监视中查出异常。 |
资源出现某种异常。请确认。 |
4.5.26. 用户空间监视资源¶
模块类型 |
分类 |
返回值 |
消息 |
描述 |
对策 |
---|---|---|---|---|---|
userw |
错误 |
71 |
Timeout has occurred when creating dummy thread. |
生成dummy线程处理发生超时。 |
可执行是系统高负荷,内存不足或OS的资源不足。请确认。 |
userw |
警告 |
100 |
Timeout has occurred when initializing internal resources. |
初始化内部资源处理发生超时。 |
可执行是内存不足或者OS资源不足。请确认。 |
userw |
警告 |
101 |
Timeout has occurred when closing dummy thread handle. |
关闭dummy线程句柄处理发生超时。 |
可执行是系统高负荷,内存不足或OS的资源不足。请确认。 |
userw |
警告 |
102 |
Timeout has occurred when other timing. |
检测到由于其他不一致导致的超时。 |
系统可执行处于高负荷或者内存不足或OS资源不足。请进行检查。 |
userw |
警告 |
190 |
Initialization error has occurred in internal resource. |
内部资源的初始化发生异常。 |
可执行是内存不足或者OS资源不足。请确认。 |
4.6. 磁盘RW监视资源STOP代码列表¶
以下的情况是磁盘RW监视资源在"查出Stall异常时的动作"里选择了[生成主动停止错误]的情况下发生STOP代码列表。
STOP代码 |
内容 |
---|---|
0xE0000000 |
组资源启动/停止失败时,监视资源检出异常时的最终动作发生的STOP错误 |
0xE000FF** |
Keep alive timout(磁盘RW监视的timeout)发生的STOP错误
后8位(**的部分)在下面(timeout时执行的可执行性比较高的处理)表示。
|
0xE000FF00 |
EXPRESSCLUSTER的内部处理 |
0xE000FF01 |
free(), SetWaitableTimer(), GetTickCount(), WaitForMultipleObjects() |
0xE000FF02 |
CreateFile(), _beginthreadex() |
0xE000FF03 |
malloc(), WriteFile() |
0xE000FF04 |
FlushFileBuffers() |
0xE000FF05 |
CloseHandle() |
0xE000FF06 |
EXPRESSCLUSTER的内部处理 |
4.7. JVM监视资源输出日志消息¶
以下消息为JVM监视资源独有的日志文件——JVM操作日志的消息列表。
生成位置如下所示。
JVM操作日志
<EXPRESSCLUSTER X安装路径>\log\ha\jra\jragent*.log (*为0开始的数字)
4.7.1. JVM操作日志¶
消息 |
发生原因 |
处理方法 |
---|---|---|
Failed to write the %1.stat. |
JVM统计日志写入失败。
%1.stat:JVM统计日志文件名
|
请确认磁盘剩余空间是否足够。 |
%1: analyze finish[%4]. state = %2, cause = %3 |
(监视对象Java VM状态异常时)监视对象Java VM的资源使用量超过阈值。
%1:监视对象Java VM名称
%2:监视对象Java VM状态
(1=正常,0=异常)
%3:发生异常时的错误部分
%4:测量线程名
|
请修改在监视对象Java VM上运行的Java应用程序。 |
thread stopped by UncaughtException. |
JVM监视资源的线程已停止。 |
请执行集群挂起/集群复原,重新启动JVM监视资源。 |
thread wait stopped by Exception. |
JVM监视资源的线程已停止。 |
请执行集群挂起/集群复原,重新启动JVM监视资源。 |
%1: monitor thread can't connect to JVM. |
无法连接监视对象Java VM。
%1:监视对象Java VM名称
|
请确认监视对象Java VM是否已启动。 |
%1: monitor thread can't get the JVM state. |
无法从监视对象Java VM获取资源使用量。
%1:监视对象Java VM名称
|
请确认监视对象Java VM是否已启动。 |
%1: JVM state is changed [abnormal -> normal]. |
监视对象Java VM状态由异常变为正常。
%1:监视对象Java VM名称
|
- |
%1: JVM state is changed [normal -> abnormal]. |
监视对象Java VM状态由正常变为异常。
%1:监视对象Java VM名称
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: Failed to connect to JVM. |
无法连接监视对象Java VM。
%1:监视对象Java VM名称
|
请确认监视对象Java VM是否已启动。 |
Failed to write exit code. |
JVM监视资源无法写入记录退出代码的文件。 |
请确认磁盘剩余空间是否足够。 |
Failed to be started JVM Monitor. |
启动JVM监视资源失败。 |
请确认JVM操作日志,消除无法启动的原因后,执行集群挂起/集群复原,重新启动JVM监视资源。 |
JVM Monitor already started. |
JVM监视资源已启动。 |
请执行集群挂起/集群复原,重新启动JVM监视资源。 |
%1: GARBAGE_COLLECTOR
_MXBEAN_DOMAIN_TYPE is invalid.
|
从监视对象Java VM获取GC信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: GarbageCollectorMXBean is invalid. |
从监视对象Java VM获取GC信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: Failed to measure the GC stat. |
从监视对象Java VM获取GC信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: GC stat is invalid. last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5. |
从监视对象Java VM获取GC发生次数,测量执行时间失败。
%1:监视对象Java VM名称
%2:上次测量时的GC发生次数
%3:上次测量时的GC总执行时间
%4:此次测量时的GC发生次数
%5:此次测量时的GC总执行时间
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: GC average time is too long. av = %6, last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5. |
监视对象Java VM中GC的平均执行时间超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的GC发生次数
%3:上次测量时的GC总执行时间
%4:此次测量时的GC发生次数
%5:此次测量时的GC总执行时间
%6:上次测量到此次测量之间,GC的平均执行时间
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: GC average time is too long compared with the last connection. av = %6, last.getCount = %2, last.getTime = %3, now.getCount = %4, now.getTime = %5. |
重新连接监视对象Java VM后,监视对象Java VM中,GC的平均执行时间超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的GC发生次数
%3:上次测量时的GC总执行时间
%4:此次测量时的GC发生次数
%5:此次测量时的GC总执行时间
%6:上次测量到此次测量之间,GC的平均执行时间
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: GC count is too frequently. count = %4 last.getCount = %2, now.getCount = %3. |
监视对象Java VM中GC的发生次数超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的GC发生次数
%3:此次测量时的GC发生次数
%4:上次测量到此次测量之间的GC发生次数
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: GC count is too frequently compared with the last connection. count = %4 last.getCount = %2, now.getCount = %3. |
重新连接监视对象Java VM后,监视对象Java VM中,GC的发生次数超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的GC发生次数
%3:此次测量时的GC发生次数
%4:上次测量到此次测量之间的GC发生次数
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: RuntimeMXBean is invalid. |
从监视对象Java VM获取信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: Failed to measure the runtime stat. |
从监视对象Java VM获取信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。
请确认监视对象Java VM中,处理负载是否过高。
|
%1: MEMORY_MXBEAN_NAME is invalid. %2, %3. |
从监视对象Java VM获取内存信息失败。
%1:监视对象Java VM名称
%2:内存池的名称
%3:内存的名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: MemoryMXBean is invalid. |
从监视对象Java VM获取内存信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: Failed to measure the memory stat. |
从监视对象Java VM获取内存信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。
请确认监视对象Java VM中,处理负载是否过高。
|
%1: MemoryPool name is undefined. memory_name = %2. |
无法从监视对象Java VM获取内存信息。
%1:监视对象Java VM名称
%2:测量对象的Java内存池名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: MemoryPool capacity is too little. memory_name = %2, used = %3, max = %4, ratio = %5. |
监视对象Java VM的Java内存池剩余空间小于阈值。
%1:监视对象Java VM名称
%2:测量对象的Java内存池名称
%3:Java内存池的使用量
%4:Java内存池的最大使用量
%5:Java内存池的利用率
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: THREAD_MXBEAN_NAME is invalid. |
从监视对象Java VM获取线程信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: ThreadMXBean is invalid. |
从监视对象Java VM获取线程信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: Failed to measure the thread stat. |
从监视对象Java VM获取线程信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: Detect Deadlock. threads = %2. |
监视对象Java VM的线程发生死锁。
%1:监视对象Java VM名称
%2:死锁的线程ID
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: Thread count is too much(%2). |
监视对象Java VM中启动的线程数超过阈值。
%1:监视对象Java VM名称
%2:测量时的线程启动数
|
请修改在监视对象Java VM上运行的Java应用程序。 |
%1: ThreadInfo is null.Thread count = %2. |
从监视对象Java VM获取线程信息失败。
%1:监视对象Java VM名称
%2:测量时的线程启动数
|
请确认监视对象Java VM的版本的操作环境是否正确。 |
%1: Failed to disconnect. |
切断监视对象Java VM失败。
%1:监视对象Java VM名称
|
- |
%1: Failed to connect to WebLogicServer. |
连接监视对象WebLogic Server失败。
%1:监视对象Java VM名称
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Failed to connect to Sun JVM. |
连接监视对象Java VM,WebOTX失败。
%1:监视对象Java VM名称
|
请修改在监视对象Java VM,WebOTX上运行的Java应用程序。 |
Failed to open the %1. |
输出JVM统计日志失败。
%1:HA/JVMSaverJVM 统计日志文件名称
|
请确认磁盘剩余空间是否足够,是否超出能打开文件的上限数。 |
%1: Can't find monitor file. |
无法监视。
%1:监视对象Java VM名称
|
- |
%1: Can't find monitor file, monitor stopped[thread:%2]. |
停止监视。
%1:监视对象Java VM名称
%2:测量线程的类型
|
- |
%1: Failed to create monitor status file. |
创建内部文件失败。
%1:监视对象Java VM名称
|
请确认是否超出磁盘剩余空间或卷的最大文件数。 |
%1: Failed to delete monitor status file. |
删除内部文件失败。
%1:监视对象Java VM名称
|
请确认硬盘是否有问题。 |
%1: com.bea:Type=ServerRuntime is invalid. |
从监视对象Java VM获取信息失败。
%1:监视对象Java VM名称
|
请确认监视对象Java VM的操作环境是否正确。 |
%1: WorkManagerRuntimeMBean or ThreadPoolRuntimeMBean is invalid. |
从监视对象WebLogic Server获取信息失败。
%1:监视对象Java VM名称
|
请确认监视对象WebLogic Server的操作环境是否正确。 |
%1: Failed to measure the WorkManager or ThreadPool stat. |
从监视对象WebLogic Server获取信息失败。
%1:监视对象Java VM名称
|
请确认监视对象WebLogic Server的操作环境是否正确。 |
%1: ThreadPool stat is invalid. last.pending = %2, now.pending = %3. |
测量监视对象WebLogic Server线程池的待机请求数失败。
%1:监视对象Java VM名称
%2:上次测量时的待机请求数
%3:此次测量时的待机请求数
|
请确认监视对象WebLogic Server版本的操作环境是否正确。 |
%1: WorkManager stat is invalid. last.pending = %2, now.pending = %3. |
测量监视对象WebLogic Server运行管理的待机请求数失败。
%1:监视对象Java VM名称
%2:上次测量时的待机请求数
%3:此次测量时的待机请求数
|
请确认监视对象WebLogic Server版本的操作环境是否正确。 |
%1: PendingRequest count is too much. count = %2. |
监视对象WebLogic Server线程池的待机请求数超过阈值。
%1:监视对象Java VM名称
%2:此次测量时的待机请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: PendingRequest increment is too much. increment = %4, last.pending = %2, now.pending = %3. |
监视对象WebLogic Server线程池的待机请求数增量超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的待机请求数
%3:此次测量时的待机请求数
%4:上次测量到此次测量之间,待机请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: PendingRequest increment is too much compared with the last connection. increment = %4, last.pending = %2, now.pending = %3. |
与监视对象WebLogic Server重新连接后,监视对象WebLogic Server线程池的待机请求数增量超过阈值。
%1:监视对象Java VM名称
%2:上次测量时的待机请求数
%3:此次测量时的待机请求数
%4:上次测量到此次测量之间,待机请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Throughput count is too much. count = %2. |
监视对象WebLogic Server线程池在单位时间内执行的请求数超过阈值。
%1:监视对象Java VM名称
%2:此次测量时在单位时间内执行的请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Throughput increment is too much. increment = %4, last.throughput = %2, now.throughput = %3. |
监视对象WebLogic Server线程池在单位时间内执行的请求数增量超过阈值。
%1:监视对象Java VM名称
%2:上次测量时在单位时间内执行的请求数
%3:此次测量时在单位时间内执行的请求数
%4:上次测量到此次测量之间,单位时间内执行请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Throughput increment is too much compared with the last connection. increment = %4:, last.throughput = %2, now.throughput = %3. |
与监视对象WebLogic Server重新连接后,监视对象WebLogic Server线程池在单位时间内执行请求数的增量超过阈值。
%1:监视对象Java VM名称
%2:上次测量时在单位时间内执行的请求数
%3:此次测量时在单位时间内执行的请求数
%4:上次测量到此次测量之间,单位时间内执行请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: PendingRequest count is too much. appName = %2, name = %3, count = %4. |
监视对象WebLogic Server运行管理的待机请求数超过阈值。
%1:监视对象Java VM名称
%2:应用程序名
%3:运行管理名
%4:待机请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: PendingRequest increment is too much. appName = %2, name = %3, increment = %6, last.pending = %4, now.pending = %5. |
监视对象WebLogic Server运行管理的待机请求增量超过阈值。
%1:监视对象Java VM名称
%2:应用程序名
%3:运行管理名
%4:上次测量时的待机请求数
%5:此次测量时的待机请求数
%6:上次测量到此次测量之间,待机请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: PendingRequest increment is too much compared with the last connection. AppName = %2, Name = %3, increment = %6, last.pending = %4, now.pending = %5. |
与监视对象WebLogic Server重新连接后,监视对象WebLogic Server运行管理的待机请求增量超过阈值。
%1:监视对象Java VM名称
%2:应用程序名
%3:运行管理名
%4:上次测量时的待机请求数
%5:此次测量时的待机请求数
%6:上次测量到此次测量之间,待机请求数的增量
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Can't find WorkManager. appName = %2, name = %3. |
无法从WebLogic Server获取已设置的运行管理。
%1:监视对象Java VM名称
%2:应用程序名
%3:运行管理名
|
请修改[监视对象WebLogic的运行管理]的设置。 |
%1: analyze of average start[%2]. |
平均值分析已开始。
%1:监视对象Java VM名称
%2:线程名
|
- |
%1: analyze of average finish[%2].state = %3. |
平均值分析已结束。
%1:监视对象Java VM名称
%2:线程名
%3:监视对象的状态
|
- |
%1: Average of PendingRequest count is too much. count = %2. |
监视对象WebLogic Server线程池的待机请求数的平均值超过阈值。
%1:监视对象Java VM名称
%2:此次测量时的待机请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Average of Throughput count is too much. count = %2. |
监视对象WebLogic Server线程池在单位时间内执行的请求数平均值超过阈值。
%1:监视对象Java VM名称
%2:此次测量时在单位时间内执行的请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
%1: Average of PendingRequest count is too much. AppName = %2, Name = %3, count = %4. |
监视对象WebLogic Server运行管理的待机请求数平均值超过阈值。
%1:监视对象Java VM名称
%2:应用程序名
%3:运行管理名
%4:此次测量时的待机请求数
|
请修改在监视对象WebLogic Server上运行的Java应用程序。 |
Error: Failed to operate clpjra_bigip.[%1] |
%1:错误代码 |
请修改设定内容。 |
4.8. 用户空间监视资源的STOP代码列表¶
以下信息是在用户空间监视资源的"查出Stall异常时的动作"中选择"生成主动停止错误"时发生的STOP代码列表。
STOP代码 |
内容 |
---|---|
0xE0000000 |
作为检测到监视资源异常时的最终动作发生的STOP错误 |
0xE000FF** |
因KeepAlive超时(用户空间监视超时)而发生的STOP错误
后8位(**的部分)表示下述Check Point(超时时被执行的可执行性高的处理)。
|
0xE000FF00 |
EXPRESSCLUSTER的内部处理 |
0xE000FF01 |
SetWaitableTimer(), GetTickCount(), WaitForMultipleObjects() |
0xE000FF02 |
_beginthreadex(),WaitForMultipleObjects() |
0xE000FF05 |
CloseHandle() |
0xE000FF06 |
EXPRESSCLUSTER的内部处理 |