Top
PRIMECLUSTER Messages
FUJITSU Software

4.4 Warning Messages

This section explains the FJSVcluster format warning messages in the order of message numbers.

Note

When the message number 6206 or 6209 is output, see "6206" or "6209."

2207  Process (appli) has stopped.

Content:

This message warns that the monitoring target with the process monitoring feature was stopped by other than the correct processing for stopping by the execution of the Offline script.
appli indicates the absolute path name of the monitored process that has been stopped.

Corrective action:

If the process was stopped because of an error, search for the cause by checking the process specification or core file error. The core file is written to the current directory of the process or the directory set for the kernel parameter of the system. (If the file is written-enabled, the normal access control is applied.).

Check the value of the kernel parameter by executing the following command.

# sysctl -a | grep kernel.core_pattern
kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e

The core file is not generated for the process that has an effective user ID different than the actual user ID. For detailed investigations, contact the creator of this process.

4250 The line switching unit cannot be found because FJSVclswu is not installed

Content:

This message indicates that the line switching unit cannot be detected, as the FJSVclswu is not installed.

Corrective action:

Devices other than the line switching unit register an automatic resource.

Install the FJSVclswu package and conduct the automatic resource registration of the line switching unit for using the line switching unit.

5001 The RCI address has been changed. (node:nodename address:address)

Content:

Change of RCI address is detected during operation.
nodename indicates the node name of which RCI address is changed. address represents the RCI address after change.

Corrective action:

Review the RCI address setting of the detected node.

5021 An error has been detected in part of the transmission route to MMB. (node:nodename mmb_ipaddress1:mmb_ipaddress1 mmb_ipaddress2:mmb_ipaddress2 node_ipaddress1:node_ipaddress1 node_ipaddress2:node_ipaddress2)

Content:

This message indicates that an error has been detected in part of the transmission route to MMB.

Corrective action:

An error was detected in part of the transmission route to MMB, or MMB may be in high load.

Check the following points:

  • Check if the normal lamp of the port connected to the HUB and the LAN cable is ON.

  • Check if the LAN cable is connected to the MMB port connector or the HUB-side connector.

  • Check if the load to MMB is high.

If one of the above items is found to be the cause, the MMB monitoring agent or the iRMC asynchronous monitoring agent recovers automatically after the corrective action is taken. Automatic recovery takes up to 10 minutes.

If the automatic recovery message 3082 (MMB monitoring agent) or 3122 (iRMC asynchronous monitoring agent) is displayed, and this message is not displayed again after 10 minutes has passed, MMB may have been in temporally high load. In this case, no action is required.

If the connection fails after the above items are checked, contact field engineers because there may be a network failure or a failure in hardware such as MMB or HUB. If this corrective action does not work, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

5100 An error was detected in the failover unit of the line switching unit. (RCI:addr LSU:mask status:status type:type)

Content:

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.

mask: Indicates the LSU mask to be controlled.

status: Indicates the an internal status of the line switching unit by error type.

type: Indicates an error type.

  • 3: Indicates that the reserved status was not canceled.

    status: The reserved status of each LSU included in the switching unit is indicated by the value of the LSU mask.

    0: Indicates that the LSU is in the released status.

    1: Indicates that the LSU is in the reserved status.

  • 4: Indicates that the connection has not changed.

    status: The status of the connection of each LSU included in the switching unit is indicated by the LSU mask value.

    0: Indicates that the LSU is connected to port 0.

    1: Indicates that the LSU is connected to port 1.

  • 5: Indicates that the reserved status could not be created.

    status: The reserved status of each LSU included in the switching unit is indicated by the value of the LSU mask.

    0: Indicates that the LSU is in the released status.

    1: Indicates that the LSU is in the reserved status.

LSU mask value

    LSU15 LSU14 LSU13 LSU12 ... LSU03 LSU02 LSU01 LSU00
    0x8000 0x4000 0x2000 0x1000 ... 0x0008 0x0004 0x0002 0x0001

Corrective action:

No corrective action is required because processing is retried. If, however, retries fail repeatedly and if this warning occurs frequently, contact field engineers.

5200 There is a possibility that the resource controller does not start.
(ident::ident command:command, ....)

Content:

Notification of the completion of startup has not yet been posted from the resource controller. ident indicates a resource controller identifier while command indicates the startup script of the resource controller.

Corrective action:

It is possible that startup of GDS resource controller is delayed. If an error message is output after this warning message, take the corrective action instructed by the error message.

If the message is displayed again, collect the investigation information. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."

If no error messages are output, there are no problems as GDS resource controller operates later.

7130  The specified resource ID (rid ) cannot be deleted because it is being used.

Content:

The specified resource ID cannot be deleted because it has been used for GDS, and so on.
rid indicates the resource ID.

Corrective action:

Confirm the resource ID to be deleted, and then set up the correct resource ID.

ccmtrcstr: FJSVclerr Onltrc start fail

Content:

Failed to start an online trace.

When this message is output, the following messages are also output:

FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.mst Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.lck Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.dbc Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.dbu Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.com Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.syn Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.svlib Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmhty Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmslb Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.evmmtx Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cem Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cemtm Onltrc start fail
FJSVcldbm: WARNING: ccmtrcstr: FJSVcldbm.cemlck Onltrc start fail

Corrective action:

Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."