PRIMECLUSTER Messages

4.2 Operator Intervention Messages

This section explains messages that request responses in the order of message numbers.

There are two response methods:

• Response by GUI (Cluster Admin)

• Response by "clreply" command from command prompt

1421 The userApplication "userApplication" did not start automatically because not all of the nodes where it can run are online.
Do you want to force the userApplication online on the SysNode "SysNode"?
Message No.: number
Do you want to do something? (yes/no)
Warning: Forcing a userApplication online ignores potential error conditions. Used improperly, it can result in data corruption. You should not use it unless you are certain that the userApplication is not running anywhere in the cluster.

Content:

Solaris PRIMECLUSTER 4.2A00 or earlier and Linux PRIMECLUSTER 4.3A20 or earlier

The cluster application was not started automatically because all SysNodes that make up the cluster application were not started within the prescribed time.

This message inquires if the cluster application is to be forcibly started.

SysNode indicates SysNode on which userApplication will be online if you select yes.

number indicates a message number.

1421 The userApplication "userApplication" did not start automatically because not all of the nodes where it can run are online.
Forcing the userApplication online on the SysNode "SysNode" is possible.
Warning: When performing a forced online, confirm that RMS is started on all nodes in the cluster, manually shutdown any nodes where it is not started and then perform it.For a forced online, there is a risk of data corruption due to simultaneous access from several nodes.In order to reduce the risk, nodes where RMS is not started maybe forcibly stopped.
Are you sure wish to force online? (no/yes)
Message No.: number

Content:

Solaris PRIMECLUSTER 4.3A10 or later and Linux PRIMECLUSTER 4.3A30 or later

The cluster application was not started automatically because all SysNodes that make up the cluster application were not started within the prescribed time. This message inquires if the cluster application is to be forcibly started.

SysNode indicates SysNode on which userApplication will be online if you select yes.

number indicates a message number.

Make sure to check "Notes on Switching a Cluster Application Forcibly" in "PRIMECLUSTER Installation and Administration Guide" when starting the cluster application forcibly.

1422 On the SysNode "SysNode", the userApplication "userApplication" is in the Faulted state due to a fault in the resource "resource". Do you want to clear fault?
Message No.: number
Do you want to do something? (yes/no)

Content:

This message inquires if the Faulted state of the Faulted userApplication caused by faulty resource is to be cleared or not.

SysNode represents the SysNode name where the failure occurred. The userApplication indicates the faulty userApplication name. The resource indicates the resource name that caused the failure to the userApplication. The number indicates the message number.

Corrective action:

If the failure has been recovered, select "yes."
If not, select "no", remove the failure cause, and clear the Faulted state by using the "hvutil" command.

• When you select "yes"
  If you select yes, the operator intervention function will execute the "hvutil" command by specifying the clear option in the "hvutil" command and also brings userApplication Offline. Confirm whether the userApplication is in the Offline state by using Cluster Admin or executing the "hvdisp" command.

• When you select "no"
  The operator intervention function does not execute the RMS command that sets the userApplication to Offline.

1423 On the SysNode "SysNode", the userApplication "userApplication" has the faulted resource "resource". The userApplication "userApplication" did not start automatically because not all of the nodes where it can run are online.
Do you want to force the userApplication online on the SysNode "SysNode"?
Message No.: number
Do you want to do something? (yes/no)
Warning: Forcing a userApplication online ignores potential error conditions. Used improperly, it can result in data corruption. You should not use it unless you are certain that the userApplication is not running anywhere in the cluster.

Content:

For Solaris PRIMECLUSTER 4.2A00 or earlier and Linux PRIMECLUSTER 4.3A20 or earlier

The cluster application was not started automatically because the cluster application resource failed and also all SysNodes that make up the cluster application were not started within the prescribed time.

This message inquires if the cluster application is to be forcibly started.

SysNode indicates the name of SysNode in which the failure occurred. userApplication indicates the name of userApplication in which the failure occurred.

resource indicates the name of the resource that caused the failure in userApplication. number indicates the message number.

1423 On the SysNode "SysNode", the userApplication "userApplication" has the faulted resource "resource". The userApplication "userApplication" did not start automatically because not all of the nodes where it can run are online.
Forcing the userApplication online on the SysNode "SysNode" is possible.
Warning:  When performing a forced online, confirm that RMS is started on all nodes in the cluster, manually shutdown any nodes where it is not started and then perform it. For a forced online, there is a risk of data corruption due to simultaneous access from several nodes. In order to reduce the risk, nodes where RMS is not started maybe forcibly stopped.
Are you sure wish to force online? (no/yes)
Message No.: number

Content:

For Solaris PRIMECLUSTER 4.3A10 or later and Linux PRIMECLUSTER 4.3A30 or later

The cluster application was not started automatically because the cluster application resource failed and also all SysNodes that make up the cluster application were not started within the prescribed time. This message inquires if the cluster application is to be forcibly started.

SysNode indicates the name of SysNode in which the failure occurred. userApplication indicates the name of userApplication in which the failure occurred. resource indicates the name of the resource that caused the failure in userApplication.

number indicates the message number.

Make sure to check "Notes on Switching a Cluster Application Forcibly" in "PRIMECLUSTER Installation and Administration Guide" when starting the cluster application forcibly.