If an error message is output, analyze the log of the time zone in which the message was output from the "/var/adm/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.
Corrective action:
The text of the message that is correspondent to the message number is not available. Contact field engineers.
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 field engineers. See "Appendix C Troubleshooting."
code1, code2, code3, and code4 indicate the information that is required by field engineers.
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 "Appendix C 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 "A.5.1 CF Configuration."
Change the settings if necessary, and then reboot the system. If above actions do not help you solve the problem, contact field engineers.
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 "Appendix C 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 "A.5.1 CF Configuration". Change the settings if necessary, and then reboot the system.
If above actions do not help you solve the problem, contact field engineers.
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 the option, and then re-execute the operation.
option indicates an option.
Corrective action:
Specify the option, and then re-execute the operation.
option indicates an option.
Content:
When option option1 is specified, option option2 is required.
Corrective action:
Specify the options correctly, and re-execute the operation.
Content:
Two options specified with the command conflict.
Corrective action:
Re-execute the command by specifying either one of the options.
Content:
If one of the options option1 is specified, option option2 cannot be specified.
Corrective action:
Specify the options correctly, and re-execute the operation.
Corrective action:
Collect debugging information and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
target indicates a command name.
Content:
The specified resource does not exist. code1 and code2 indicate the information required for troubleshooting.
Corrective action:
Specify the resource correctly, and re-execute the operation.
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 field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
code1 and code2 indicate the debugging information required for field engineers.
Corrective action:
Collect debugging information, and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
code1 and code2 indicate the debugging information required for field engineers.
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 field engineers. For details on collecting debugging information, see "Appendix C 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(1M)" 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(1M)" command. Correct the insufficient resource problem, and do the operation again.
If the problem cannot be solved even by applying with the corrective actions, collect debugging information and then contact field engineers. For details on debugging information, see "Appendix C 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(1M)" command. However, if this occurs, collect debugging information and contact field engineers. For details on collecting debugging information, see "Appendix C Troubleshooting."
If hvw(1M) 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(1)" command. For details on the "clgettree(1)" command, see the manual page for clgettree(1M).
If the procedure resource is not registered to the resource database, register the procedure resource displayed in the message to the resource database. See "Part 7 PRIMECLUSTER Products."
If the procedure resource is registered to the resource database, collect debugging information and contact field engineers. For details on collecting debugging information, see "Appendix C 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.
Content:
Specify the option option with the absolute path name.
Corrective action:
Specify the option correctly, and re-execute the operation.
Content:
The specified resource is not being monitored. code represents debugging information.
Corrective action:
No action is necessary.
Content:
The specified process does not exist. pid represents the process ID of the specified process.
Corrective action:
Specify the process ID correctly, and re-execute the operation.
Content:
The specified command does not exist. command represents the specified command.
Corrective action:
Specify the command with a full path name, and then re-execute the operation.
Content:
The process did not terminate within the termination wait time of the process.
code1 and code2 indicate the information required for troubleshooting.
Corrective action:
Search for a cause. For information on the investigation, contact the creator of the process.
Corrective action:
Specify a correct directory, and then re-execute.
Corrective action:
userApplication or the resource is not registered as it is monitored by the patrol diagnosis.
Reexamine the configuration of the patrol diagnosis by referring to "6.9 Setting Up Patrol Diagnosis."
The specified userApplication or resource will be output to resource.
Corrective action:
Specify userApplication that is in the following state, and then re-execute:
Standby, Offline, Faulted, Deact
The state of userApplication will be output to status.
Corrective action:
Confirm that power is being supplied to the node on which patrol is enabled. Power on the node if necessary, and then re-execute.
Confirm that RMS is activated.
If RMS is not activated, start the RMS with Cluster Admin or the "hvcm(1M)" command and then re-execute operation.
Corrective action:
Confirm the state of userApplication in which the corrected resource is registered by using the RMS main window or executing the "hvdisp(1M)" 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(1M)" 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(1M)" 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(1M)" 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.
Content:
The "clmonproc" command failed to request start or stop monitoring of the process monitoring function.
Corrective action:
The daemon process for the process monitoring function might not be running. Check the "prmd" process by executing the "ps" command. If the "prmd" process does not exist, execute /etc/init.d/clprmd start to recover the process. If the "prmd" process exists, execute /etc/init.d/clprmd stop and then /etc/init.d/clprmd start, to recover the process.
Content:
A process to be monitored by specifying the "-g" option in the "clmonproc" command must satisfy the condition "process ends immediately after descendent processes are generated." However, the parent process did not end even after the specified time (default 10 seconds) elapsed after the process was started. If the system continues to monitor the process in this condition, the load on the system is getting high, so the process was removed from the processes to be monitored by the process monitoring function.
appli indicates the absolute path name of the monitored process.
Corrective action:
Take one of the following actions:
Do not monitor descendent processes. Do not specify the "-g" option in the "clmonproc" command.
If the monitored process can be changed, do not change the process group in the descendent processes, and do not specify the "-g" option in the "clmonproc" command.
If processes were generated, end the parent process immediately. Set up the process so that the first child process that is generated becomes the process leader immediately after it operates.
Content:
The command that was specified with the "-a" option of the "clmonproc" command could not be executed.
appli indicates the absolute path name of the process that has failed startup. error indicates the detailed code.
Corrective action:
Check whether the command that was specified with the "-a" option of the "clmonproc" command can be executed. Execute the command, and check whether an error occurs. If this message is output again even if the command could be executed, contact field engineers.
Since errno is output as a detail code, field engineers should investigate the cause from this message information. For example, if errno is 13 (EACCES), the most likely cause is that the command path that was specified in the "-a" option of the "clmonproc" command does not have execute permission.
Content:
The power to the disk unit may not be turned on or the disk may be disconnected. If an attempt is made to start userApplication, userApplication may not start normally.
Two messages, namely, this message and that of message number 6836 may be displayed depending on connection.
Corrective action:
Confirm that the power to the shared disk device is turned on and that the shared disk device is connected correctly. If power is not being supplied to the shared disk device, stop the node, turn on the power to the shared disk device, and then boot the node. If the connection of the shared disk device is incorrect, stop the node, rectify the connection, and then boot the node.
NodeID indicates the identification number of the node to which the disk unit was connected while disk indicates the shared disk that could not be detected.
Corrective action:
Collect debugging information and contact field engineers. For details on collecting debugging information, see "Appendix C Troubleshooting."
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
[Error cause details]
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.
[Corrective action]
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(1M)" command. To register the state transition procedure, execute the "clsetproc(1M)" 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 field engineers.
Content:
The wiring of the shared disk device could be incorrect. If an attempt is made to launch the userApplication in the current state, userApplication may not start up normally.
Two messages, namely, this message and that of message number 6807 may be displayed depending on connection.
Corrective action:
Confirm that the shared disk device is connected correctly. If the connection is incorrect, stop the node, correct the connection, and then boot the node.
NodeID indicates the node identification number to which the shared disk device is connected while disk indicates the shared disk in which an error has been detected.
Corrective action:
Take corrective action by referring to "7.4.2 Corrective Action when Patrol Diagnosis Detects a Fault."
The interface name of the LAN device for which a failure is diagnosed is output with altname. nodename, rid, and code indicate the information required for debugging.
Corrective action:
Collect debugging information, and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
An interface name of the LAN device for which a failure is diagnosed is output with altname. nodename, rid, and code indicate debugging information.
Corrective action:
Take corrective action by referring to "7.4.2 Corrective Action when Patrol Diagnosis Detects a Fault."
A device name for which a failure is diagnosed is output with altname. nodename, rid, and code indicate debugging information.
Corrective action:
Collect debugging information, and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
A shared device name for which a failure is diagnosed is output with altname. nodename, rid, and code indicate debugging information.
Corrective action:
Specify the available hardware in which patrol diagnosis is enabled. See "6.9 Setting Up Patrol Diagnosis."
The device name that could not found can be output with altname. nodename, rid, and code indicate debugging information.
Corrective action:
Specify the available hardware in which patrol diagnosis is enabled. See "6.9 Setting Up Patrol Diagnosis."
The interface name of the LAN device that could not be found can be output with altname. nodename, rid, and code indicate debugging information.
Corrective action:
The flag used when the LAN device is activated is in the inadequate state such as not UP and not BROADCAST. After confirming the system configuration, activate the device correctly. Confirm the flag by executing the "ifconfig(1M)" command.
UP must be set.
BROADCAST must be set.
LOOPBACK must not be set.
POINTOPOINT must not be set.
NOARP must not be set.
The network device name, which is in the inadequate state, can be output with altname. nodename, rid, and code indicates debugging information.
Corrective action:
Leave the operation undone for several minutes, and then re-execute accessing.
type indicates information for research.
Corrective action:
Contact field engineers to check whether the SCF is operating normally.
errno indicates an error number.
Corrective action:
Contact field engineers to check whether the SCF is operating normally.
errno indicates an error number.
Corrective action:
A line switching unit whose subclass cannot be identified is connected.
addr: Indicates the RCI address of the line switching unit.
no: Indicates the subclass of the line switching unit.
0x01: Indicates a 4-line switching unit.
0x02: Indicates a 16-line switching unit.
Confirm if the line switching unit is a supported product.
Corrective action:
No line switching unit that is specified with the RCI address exists.
Confirm with field engineers whether the RCI address of the specified line switching unit is correct or it is connected.
addr indicates an RCI address.
Corrective action:
Confirm if the power of the specified line switching unit is turned on and that the RCI cable is not disconnected.
addr indicates the RCI address of the line switching unit.
Corrective action:
Although no times of attempts were made to reserve the switching unit, which was specified with mask of the line switching unit that was specified with RCI address (addr), reservation failed.
Check whether the line switching unit has failed, whether the RCI connection has an error, and whether the power-supply voltage is abnormal. If errors occur frequently, contact field engineers.
addr indicates the RCI address of the line switching unit, while mask indicates a mask that represents a switching unit of the line switching unit and no indicates the retry count until an error is displayed.
Maintenance information (for system administrators)
Determine whether the specified line switching unit has an error.
Corrective action:
An error was detected in the switching control board of the line switching unit.
addr: Indicates the RCI address of the line switching unit in which an error was detected.
status: Indicates the internal status of the line switching unit by error type.
type: Indicates the error type.
1: Error in the switching control system (status: status 0)
status: Indicates the value of status 0 (see below) of the line switching unit.
0x80: QANS (0: normal, 1: abnormal)
Indicates that the switching line of QSC remains in the asserted state (abnormal) although other than switchover processing is being performed.
0x40: QAST (0: normal, 1: abnormal)
Indicates that the switching line of QSC cannot be asserted during switchover processing. Once an abnormal state arises, that state remains until the power supply is turned off.
2: Power/circuit error (status: status 0)
status: Indicates the value of status 0 (see below) of the line switching unit.
0x10: QENA (0: normal, 1: abnormal)
Indicates the QSC switchover function enabled state. If this Bit is ON, it indicates that every connected QSC is abnormal.
0x08: DCNV (0: normal, 1: abnormal)
Indicates that the output voltage of the DC-DC converter, which is mounted in the QSC, is normal. If this Bit is ON, it indicates that the output voltage of the DC-DC converter is abnormal.
Remark: This bit is enabled only for a 4-line switching unit.0x04: PW12
0 is indicated for a single power unit while 1 indicates two power units.
Remark: This bit is enabled only for a 16-line switching unit.0x02: PRY1 (0: normal, 1: abnormal)
0x01: PRY0 (0: normal, 1: abnormal)
Indicates whether the power supply is normal/abnormal. (Normal means that power is supplied without any failure.)
Remark: This Bit is enabled only for a 16-line switching unit.
3: QSC connection error (status: status 1)
status: Indicates the value of status 1 (see below) of the line switching unit.
0x80: HSC (0: 4-line switching unit, 1: 16-line switching unit)
Indicates if a 16-line switching unit is used.
0x20: QSC1 (slot 1 mounted)
0x10: QSC0 (slot 0 mounted)
Indicates the slot in which the QSC (switching control board) is mounted. Values other than 0x10 and 0x20 indicate errors.
0x02: OBSY
Indicates that the other side of the duplicated QSC is presently executing switchover processing (canceling of reserve, switchover command 0, and switchover command 1).
Check whether the line switching unit has a failure, if the RCI connection has an error, or whether the power-supply voltage is abnormal. If these errors occur frequently, contact field engineers.
Maintenance information (for system administrators)
Check whether the specified line switching unit has an error.
Corrective action:
An error was detected in the switching unit of the line switching unit.
addr: Indicates an RCI address of the line switching unit in to be controlled.
mask: Indicates an LSU mask which is the target of control
status: Indicates the internal status of the line switching unit by error type (for research).
type: Indicates an error type.
1: Indicates an erroneous state.
status: Indicates the abnormal state of each LSU, which is included in the switching unit, as the value of LSU mask.
0: Indicates that the relevant LSU is normal.
1: Indicates that the relevant LSU is abnormal.
2: Indicates that a request of canceling switchover/reserve has been sent to the unconnected LSU.
status: Indicates whether each LSU that is included in the switching unit is connected using the value of the LSU mask.
0: Indicates that the LSU is unconnected.
1: Indicates that the LSU is connected.
LSU mask value
LSU15 LSU14 LSU13 LSU12 ... LSU03 LSU02 LSU01 LSU00
0x8000 0x4000 0x2000 0x1000 ... 0x0008 0x0004 0x0002 0x0001
Check whether the line switching unit has a failure, if the RCI connection has an error, or if the power-supply voltage is abnormal. If these errors occur frequently, contact field engineers.
Maintenance information (for system administrators)
Check whether the specified line switching unit has an error.
Corrective action:
Collect information for troubleshooting for all nodes, and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
Reboot the node in which the error occurred. If you need to stop the node, execute the "shutdown(1M)" command.
code1 and code2 indicate information items for diagnosis.
Corrective action:
Collect information for troubleshooting for all nodes, and then contact field engineers. For details on how to collect information, see "Appendix C Troubleshooting."
Reboot the node in which an error occurred. If you need to stop the node, execute the "shutdown(1M)" command.
code1 and code2 indicate the information required for troubleshooting.
Corrective action:
Copy this message, collect debugging information, and then contact field engineers. For details on how to collect debugging information, see "Appendix C Troubleshooting."
After collecting debugging information from all nodes, reboot the node in which the error occurred. To reboot the node, use the shutdown(1M) command.
code1 and code2 indicate the information required for troubleshooting.
Corrective action:
Set the port number attribute (port) of the line switching unit used for the resource SWLine.
rid indicates the resource ID of SWLine in the line switching unit.
Corrective action:
Set up the correct port number.
rid indicates the resource ID of the SWLine in the line switching unit while port indicates a port number.
Corrective action:
Set up the mask (Isu_mask) attribute of the switching unit used for the shared resource SH_SWLine.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
Re-create the shared resource SH_SWLine as a child resource of shared resource SH_SWU.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
Set up the RCI address attribute (addr) of the line switching unit used for the shared resource SH_SWU.
rid indicates the resource ID of the shared resource SH_SWLine in the line switching unit.
Corrective action:
For the resource ID of the node that is connected to the specified port of the line switching unit, an incorrect resource ID of other than a node or nonexistent resource ID is specified. Set up the correct resource ID.
no indicates a port number in the line switching unit while rid indicates the resource ID.
Corrective action:
The same resource ID cannot be specified for port 0 and port 1 in the line switching unit. The same node cannot be specified as the operating and standby node.
Set up the correct resource ID of the node.
rid indicates the resource ID of the specified node.
Corrective action:
The specified resource ID cannot be deleted because it has been used for GDS
Confirm the resource ID to be deleted, and then set up the correct resource ID.
rid indicates the resource ID.
Corrective action:
Set up the correct resource ID.
rid indicates a resource ID while class indicates the class name of the shared resource class.
Corrective action:
Set up the correct resource ID.
name indicates a resource name while class indicates the class name of the shared resource class.
