The error messages of the userApplication Configuration Wizard GUI are described in message number sequence.
Content:
If this message is displayed during the creation of userApplication, possibly due to the minimum value is less than the value being set to the Timeout value of Fsystem resource.
Corrective action:
Change the Timeout value with the following procedure:
Check the minimum value of the Fsystem resource's Timeout value.
For the minimum value, refer to the "Creating 31 or more mount points in Fsystem resources" mentioned in the "Creating Fsystem Resources" of "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)," and check.
Check if the file below is existing in all of the nodes, if it exists, delete the file.
/opt/SMAW/SMAWRrms/build/wizard.d/config/subapplications
Start userApplication Configuration Wizard
The following message below may be displayed during the start-up, but this does not pose a problem.
0893 RMS Configuration generation failed.
Change the Timeout value of Fsystem resource.
For changing the Timeout value of each mount point of the Fsystem resource, follow "Fsystem" mentioned in "Changing the Attributes Used by a Resource or a Resource Interface" of "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
If the Timeout value is greater than the minimum value or the problem cannot be resolved by the action described above, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
An internal server contradiction or an event that caused a network disconnection between the Web browser and the cluster management server (restart, shutdown, emergency stop, and LAN cable disconnection) may have occurred.
Corrective action:
If a Web-Based Admin View message is displayed, take corrective action for that message.
If a Web-Based Admin View message is not displayed, respond to this message and restart the userApplication Configuration Wizard.
If the problem cannot be resolved by the action described above, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
A package having a different version from the package version required by the userApplication Configuration Wizard GUI is installed in the cluster node.
Corrective action:
See the information that was output to (detailed information), and reinstall the correct package for the cluster node.
Content:
The file cannot be edited because it is not a Bourne, C, or korn shell file.
Corrective action:
Specify another file.
Content:
A candidate list of the information to be set to Resource could not be obtained.
Corrective action:
Make sure the cluster resource management facility is operating and the automatic configuration (registration of the network unit) is performed.
After confirming that the network unit is registered to the cluster resource management facility, execute the process again.
For how to execute and how to confirm the process of automatic configuration, refer to "Automatic Configure" in "PRIMECLUSTER Installation and Administration Guide (Oracle Solaris)."
Content:
The command terminated abnormally. A message is output from the command.
Corrective action:
If the condition does not change even after you re-execute the same operation, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
The message that is output from the command may contain the "FJSVcluster" keyword and a message number. In this case, take the corrective action described in "Chapter 4 FJSVcluster Format Messages."
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The command execution failed. A message is output from the command.
Corrective action:
If the condition does not change even after you re-execute the same operation, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
When the three-layer configuration of Web-Based Admin View is used, no cluster node that can be accessed from the management server can be found.
Corrective action:
Check whether Web-Based Admin View is running on the cluster node. The operating status of Web-Based Admin View can be confirmed by executing /etc/opt/FJSVwvbs/etc/bin/wvstat.
If there is no problem in the environment of Web-Based Admin View and the condition does not change, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The RMS Configuration information cannot be analyzed.
Corrective action:
If the cluster application or a resource is not created, change to other Configuration information.
If the condition does not change, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Generation of RMS Configuration information failed. A message is output from the command.
Corrective action:
If this message is displayed while executing the corrective action of 0880, no action is required because there is no problem.
Otherwise if this message is displayed, start the operation again from the beginning.
If the problem is not resolved by the above action, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
Distribution of the RMS Configuration information failed. A message is output from the command.
Corrective action:
Check the following:
Whether there are resources that are not related to any cluster application.
Whether there cluster applications that do not have any resources.
If the above conditions are found, delete the unnecessary cluster applications and resources.
If the above conditions are not found, repeat the operation from the beginning.
If an error still occurs, collect the Java console information, a hard copy of the error dialog box, and the investigation information, and then contact field engineers.
For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The I/O fencing cannot be used during creation in the userApplication configuration.
Corrective action:
If using I/O fencing, you must recreate I/O fencing in the userApplication configuration which satisfies the following conditions.
Register the Gds resources.
Set 2 as SysNode count.
