PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System)

C.3 Detecting a Failed Resource

If a failure occurs in a resource, you can specify the resource by referring to the following:

• The message displayed if a failure occurs in the resource
• Resource Fault History
• Fault Resource List

To use the history function of the failed resource, the resource database must be set up correctly. Also, the "AutoStartUp" and "PersistentFault" attributes of userApplication must be set to yes(1).

For information on the resource database settings, see the "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."

To use the detection function of the failed resources, you must enable an operator intervention request. For information on the use of the operator intervention request, see "Setting Up Fault Resource Identification and Operator Intervention Request."

The operator intervention function and the failed resource history function are both dependent on the "clwatchlogd" daemon. This daemon can be started automatically with the "rc" script in multi-user mode. The "clwatchlogd" daemon uses the "RELIANT_LOG_PATH" environment variable of RMS. The value of this variable is set when the "rc" script starts up for the first time.

When this value is changed, you need to send the "SIGHUP" signal to clwatchlogd. When clwatchlogd receives this signal, clwatchlogd acquires the latest value of RELIANT_LOG_PATH. After completing the above processing, start RMS.

This manual is installed in the /etc/opt/FJSVcluster/man directory.

Before executing the "man (1)" command, add this directory to the beginning of MANPATH. Usually, a directory name is added to the line beginning with "setenv MANPATH" within the ".cshrc" file or the line beginning with "export MANPATH" within the ".profile" file.

---

C.3.1 Failed Resource Message

C.3.2 Resource Fault History

C.3.3 Fault Resource List