| PRIMECLUSTER Installation and Administration Guide 4.2 (Linux for Itanium) |
|
Contents
Index
|
| Appendix D Messages |
If an error message is output, analyze the log of the time zone in which the message was output from the "/var/log/messages" message to check if any other error message had been output before that. If you found another error message, you need to take corrective action for this error message first.
Content:
An internal error occurred in the program. function, code1, code2, code3, and code4 indicate the debugging information for error diagnosis.
Corrective action:
Collect the debugging information. Then, contact your Fujitsu systems engineer (SE). See "Troubleshooting."
code1, code2, code3, and code4 indicate the information that is required by your Fujitsu systems engineer (SE).
Corrective action:
One of the following could be the case:
The memory resources are insufficient.
The kernel parameter has incorrect settings.
Collect information required for troubleshooting. For details on how to collect information, see "Troubleshooting."
Reexamine the estimation of the memory resources that are required for the entire system. For information on the amount of memory required for cluster control, see the "PRIMECLUSTER Installation Guide," which is provided with each product.
If you still have the problem, confirm that the kernel parameter setting is correct by referring to the "CF Configuration."
Change the settings if necessary, and then reboot the system. If above actions do not help you solve the problem, contact your Fujitsu systems engineer (SE).
code1 and code2 indicate the information required for troubleshooting.
Corrective action:
One of the following could be the case:
The disk resources are insufficient.
The kernel parameter has incorrect settings.
Collect the information required for troubleshooting. For details on how to collect information, see "Troubleshooting."
Confirm that there is sufficient disk space to enable the operation of PRIMECLUSTER. If necessary, delete any unnecessary files to create sufficient free space and then restart the system. For information on the amount of required disk space, see the "PRIMECLUSTER Installation Guide," which is provided with each product.
If you still have the problem, confirm that the kernel parameter settings are correct by referring to the "CF Configuration." Change the settings if necessary, and then reboot the system.
If above actions do not help you solve the problem, contact your Fujitsu systems engineer (SE).
code1 and code2 indicate the information required for troubleshooting.
Corrective action:
Specify the option correctly, and then re-execute the operation.
option indicates an option.
Corrective action:
Re-execute the process with system administrator's authority.
Corrective action:
Specify a correct option, and execute the command again.
option indicates an option.
Content:
Two options specified with the command conflict.
Corrective action:
Re-execute the command by specifying either one of the options.
Corrective action:
Collect debugging information and then contact your Fujitsu systems engineer (SE). For details on how to collect information, see "Troubleshooting."
target indicates a command name.
Corrective action:
Reboot the node on which this message is displayed and then reactivate the resource database. If this message appears again, collect debugging information and then contact your Fujitsu systems engineer (SE). For details on how to collect information, see "Troubleshooting."
code1 and code2 indicate the debugging information required for your Fujitsu systems engineer (SE).
Corrective action:
Collect debugging information, and then contact your Fujitsu systems engineer (SE). For details on how to collect information, see "Troubleshooting."
code1 and code2 indicate the debugging information required for your Fujitsu systems engineer (SE).
Corrective action:
Specify the state transition procedure file correctly, and then re-execute.
If the problem cannot be solved with this corrective action, collect debugging information and then contact your Fujitsu systems engineer (SE). For details on collecting debugging information, see "Troubleshooting."
Corrective action:
To overwrite the state transition procedure file, specify the "-o" option and then re-execute.
Corrective action:
Specify the resource class correctly, and then re-execute. The available resource classes are file names under /etc/opt/FJSVcluster/classes.
Confirm that the character string specified as the resource class contains no errors.
Corrective action:
Confirm the disk resource from which the state transition procedure is retrieved or the node resource of the file system is sufficient by executing the "df(1)" command. Correct the insufficient resource problem or change the location from which the state transition procedure is retried, and do the operation again.
Confirm the disk resource on which the cluster system is installed or the node resource of the file system is sufficient by executing the "df(1)" command. Correct the insufficient resource problem, and do the operation again.
If the problem cannot be solved even by applying the corrective actions, collect debugging information and then contact your Fujitsu systems engineer (SE). For details on debugging information, see "Troubleshooting."
code1 indicates debugging information while code2 indicates error number.
Corrective action:
You can delete only the state transition procedure file that was defined by a user. For information on how to delete it, refer to the manual of the product that provides the state transition procedure file.
Corrective action:
A procedure resource that is registered to the cluster application is not in the resource database. This message is not output if the cluster application was registered by using the userApplication Configuration Wizard(GUI) and executing the "hvw" command. However, if this occurs, collect debugging information and contact your Fujitsu system engineer. For details on collecting debugging information, see "Troubleshooting."
If hvw was used to register the procedure resource to the cluster application by FREECHOICE, check that the procedure resource displayed in the message text is not registered to the resource database by executing the "clgettree" command. For details on the "clgettree" command, see the manual page for clgettree.
If the procedure resource is not registered to the resource database, register the procedure resource displayed in the message to the resource database. See "PRIMECLUSTER Products."
If the procedure resource is registered to the resource database, collect debugging information and contact your Fujitsu system engineer. For details on collecting debugging information, see "Troubleshooting."
Resource indicates the resource name that is not registered to the resource database, and rid indicates the resource ID of the resource that is not registered to the resource database.
Content:
This message will not be displayed on a client system on which a browser is active. This message is displayed on the standard output when you respond to the operator intervention message with the CLI command (clreply). If a string other than yes or no is to be entered, this message will be displayed.
Corrective action:
Specify the option correctly, and then re-execute the processing.
Corrective action:
Specify a correct directory, and then re-execute.
Corrective action:
Confirm the state of userApplication in which the corrected resource is registered by using the RMS main window or executing the "hvdisp" command. You can also confirm the userApplication state by responding to the operator intervention message that is displayed after RMS is started. If userApplication is Faulted, you need to clear the Fault by using the RMS main window or specifying the "-c" option of the "hvutil" command.
SysNode indicates the name of SysNode in which a resource has failed. userApplication indicates the name of userApplication to which the failed resource belongs. resource indicates the name of the resource that has failed.
Corrective action:
Respond to the operator intervention message that is displayed after the node is started or confirm the state of userApplication running on the node in which the failure occurred, by using the RMS main window or executing the "hvdisp" command. If userApplication is Faulted, you need to clear the Fault by using the RMS main window or specifying the "-c" option of the "hvutil" command.
SysNode indicates the SysNode in which a failure occurred.
Content:
If you execute the RMS command (hvdisp) to enable the history function for the failed resource or the operation intervention function, and this fails, an error message will be displayed. Examine this error message and, after taking an appropriate correction, execute the required processing again.
Corrective action:
Confirm the contents of this message and, after taking the required corrective action, re-execute the processing.
Content:
Since the RMS command ended abnormally, the operator intervention function for the message failed.
Corrective action:
Note the contents of this message and, after applying an appropriate correction, re-execute the required processing.
number indicates the operator intervention message for which processing failed. action indicates the first response to the message from the operator with either yes or no. command indicates the RMS command which ended abnormally. "Error message from RMS command" indicates an error message that the RMS command transmits when a standard error occurs.
Corrective action:
This message is output in the following situations:
The operator specified a nonexistent message number when executing the "clreply" command. This problem can be solved by specifying a message number that is included in the unfinished message list.
The message for which a response was entered has been canceled. This occurs when the message gets old since the application state has been changed. You do not have to take any action.
The operator intervention function has automatically replaced the message for which a response has been entered with other message. For example, when the operator intervention function's message number 1422 is replaced by the message number 1423 and vice versa. In such a case, the operator intervention function responds to the first message, displays another message, and advises a user that the message number has been changed.
number indicates the number of operator intervention messages.
Content:
Since the node indicated by SysNode has stopped, the response to the operator intervention message failed.
Corrective action:
Reboot the node, and then confirm that RMS is running.
SysNode indicates the SysNode name of the node that is stopped. number indicates the number of the operator intervention messages that failed to respond. action indicates the operator's response by yes or no.
Corrective action:
The possible causes are as follows:
The state transition procedure (procedure) is not a Bourne shell script.
The state transition processes for the individual arguments (code1 to code6) of the state transition procedure (procedure) returned an error. The control program of the procedure resource determines the success or failure of the state transition processes based on the exit code (exit function) of the state transition procedure.
Exit code 0: The control program determines that the state transition process is normal.
Exit code other than 0: The control program determines that the state transition process failed.
Collect debugging information and contact your Fujitsu system engineer. For details on collecting debugging information, see "Troubleshooting."
Take the following actions:
Obtain the state transition procedure, and check that the state transition procedure (procedure) is a Bourne shell script. If the procedure is not a Bourne shell script, specify the following in the first line of the state transition procedure, and then register the state transition procedure again:
#!/bin/sh
To obtain the state transition procedure, execute the "clgetproc" command. To register the state transition procedure, execute the "clsetproc" command. For details on each command, see the corresponding manual page.
Check the return value of the state transition process for each argument (code1 to code6). If there is no process that sets up an exit code (exit function), you need to add this exit code process. If there is no process, the execution result of the last command in the state transition procedure becomes the return value.
If the problem is not resolved by the above action, contact your Fujitsu system engineer.
procedure indicates the state transition procedure in which the error occurred. If the state transition procedure indicated by procedure was created, see the subsequent information, and correct the state transition procedure.
code1, code2, code3, code4, code5, and code6 indicate the state transition instruction that resulted in an error. code7 represents debugging information.
code1: the first argument (state transition instruction type)
code2: the second argument (cluster service instance type)
code3: the third argument (state transition instruction timing)
code4: the fourth argument (resource ID)
code5: the fifth argument (state transition event type)
code6: the sixth argument (state transition event detail)
error indicates the error cause. The error causes include the following:
procedure file exit error
|
Contents
Index
|