Top
PRIMECLUSTER Messages
FUJITSU Software

5.1.2 Information Messages; Corrective Action Required

block %x, obj %x

Content:

An internal error occurred in the program.

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."

cf: elmlog ELM:001: cluster size n

Content:

The CF is connected as n-node.
This message is displayed when a node constituting the cluster system joins the cluster system.

Corrective action:

This message is not output for a system under continuous operation. If this message appears on a continuously operating system, it means that the node is stopped or started for some reasons. If the node is stopped or started unintentionally, the cause should be isolated.

CF: (TRACE): CFSF: Duplicate open attempt. (#xxxx)

Content:

SF (Shutdown Facility) already has the device open, and a second open was attempted.

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."

CF: (TRACE): CFSF: Invalid event for broadcast. (#xxxx n1)

Content:

An internal error occurred in the program.

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."

CF: (TRACE): CFSF: Invalid nodeid for broadcast. (#xxxx n1)

Content:

An internal error occurred in the program.

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."

CF: (TRACE): Link is DOWN for device: <devicename>. (#0000 N)

Content:

Indicates the specified cluster interconnect transitioned from link UP to DOWN.

Corrective action:

Determine why the cluster interconnect is transitioning from link UP to DOWN. If no causes were found, 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."

CF: (TRACE): Link is UP for device: <devicename>. (#0000 N)

Content:

Indicates the specified cluster interconnect transitioned from link DOWN to UP.

Corrective action:

If the message is continuously output, investigation should be done to determine why the link on the cluster interconnect is transitioning between UP and DOWN. If no causes were found, 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."

close failed: bad handle %x type=0x%x val=0x%x

Content:

An internal error occurred in the program.

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."

config nack failed: NOSPACE, state %s stage %s

Content:

An internal error occurred in the program.

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."

config nreq %s to %d: NOBIGBUFF

Content:

An internal error occurred in the program.

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."

Deleting mlock during remaster: %x %x %x

Content:

An internal error occurred in the program.

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."

dir nreq failed: NOSPACE: dnode: %d

Content:

An internal error occurred in the program.

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."

ELM:0003: rebuild: state: %d stage: %d  NOSPACE

Content:

An internal error occurred in the program.

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."

ELM:0004: %d DISAGREE (nack) from %d  lm_visible: 0x%x 0x%x 0x%x 0%x

Content:

Indicates that the cluster membership is changed and an ELM (enhanced lock manager) lock table is not rebuilt. The rebuild will be attempted again until it is successfully completed.

Corrective action:

If the message is continuously output, 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."

ELM:0006: %d DISAGREE (nreq) lm_visible:  0x%x 0x%x 0x%x 0%x nreq: 0x%x 0x%x 0x%x 0x%x from %d

Content:

Indicates that the cluster membership is changed and an ELM (enhanced lock manager) lock table is not rebuilt. The rebuild will be attempted again until it is successfully completed.

Corrective action:

If the message is continuously output, 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."

ELM: destroying inactive resource %x

Content:

An internal error occurred in the program.

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."

ELM: invalid query paramater

Content:

An internal error occurred in the program.

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."

elm_mrpc_configure failed, reason=#%lx

Content:

An internal error occurred in the program.

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."

elm_mrpc_register failed, reason=#%lx

Content:

An internal error occurred in the program.

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."

ELM: Multiple rdomains for one resource %lx, %lx, %lx

Content:

An internal error occurred in the program.

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."

ELM: query 0x%x from %d failed, reason: 0x%x

Content:

An internal error occurred in the program.

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."

ELM: Running out of recovery domains!

Content:

An internal error occurred in the program.

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."

ELM: Unknown  query 0x%x from nid %d

Content:

An internal error occurred in the program.

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."

fixup failed: bad handle %x

Content:

An internal error occurred in the program.

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."

freeze failed: bad resource handle 0x%x\ntype=0x%x status=0x%x mlockp=0x%x

Content:

An internal error occurred in the program.

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."

handle failed: bad handle %x

Content:

An internal error occurred in the program.

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."

instance of cfregd already running

Content:

Indicates a start of cfreg daemon was attempted, but cfreg daemon is already running.

Corrective action:

If cfregd is being started manually, first stop cfregd. For the specifications of cfregd, refer to the manual page of cfregd. If cfregd was not started manually, 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."

Invalid ELM domain for server: %d, ignored.

Content:

An internal error occurred in the program.

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."

lfreeze failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

lfreeze from %d failed: lock closed %x

Content:

An internal error occurred in the program.

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."

lk_srv_cancel_nack: stale cv_cid %d for lock %x

Content:

An internal error occurred in the program.

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."

lk_srv_notify_nack: Stale procp for lock %x

Content:

An internal error occurred in the program.

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."

lk_swap_config_nreg: unknown convert stage: %d

Content:

An internal error occurred in the program.

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."

lock destroy failed: NOSPACE for dir close

Content:

An internal error occurred in the program.

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."

look_new: kdomain %x has rdomainp %x

Content:

An internal error occurred in the program.

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."

mopen/convert failed: bad handle %x

Content:

An internal error occurred in the program.

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."

mopen failed: bad handle %x

Content:

An internal error occurred in the program.

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."

mopen failed:  %x %x: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

mopen master lock open failed : MAXLOCK

Content:

An internal error occurred in the program.

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."

plock destroy failed: bad lock %x %x

Content:

An internal error occurred in the program.

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."

plock destroy failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

rdomain failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

rdomain procp: %x exit, msgp: %x

Content:

An internal error occurred in the program.

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."

rdomainp %x != NULL for kernel domains

Content:

An internal error occurred in the program.

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."

Rdomains:  %lx and %lx for one single resource %lx

Content:

An internal error occurred in the program.

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."

rebuild failed: NOSPACE for config_nreq, nid=%d

Content:

An internal error occurred in the program.

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."

rebuild_pconvert_start: NOSPACE, state %s

Content:

Indicates ELM (enhanced lock manager) block allocation failed due to insufficient resources.

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."

Recovery was not registered yet: rdomainp %x

Content:

An internal error occurred in the program.

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."

refopened %x %x convert failed: NOSPACE

Content:

An internal error occurred in the program.

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."

refopen failed: MAXLOCK

Content:

An internal error occurred in the program.

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."

resp %x: Bad resource type or rdomain

Content:

An internal error occurred in the program.

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."

rfreeze failed: bad directory handle %x

Content:

An internal error occurred in the program.

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."

rfreeze failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

rm_sequence failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."

Running out of recovery domains

Content:

An internal error occurred in the program.

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."

send_cancel_cack_queue: invalid procp %x for lock %x

Content:

An internal error occurred in the program.

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."

send_convert_cack: bad procp: %x for lock %x

Content:

An internal error occurred in the program.

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."

send_queue: invalid proc: %x for lock %x

Content:

An internal error occurred in the program.

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."

unfreeze failed: bad res handle %x from %d

Content:

An internal error occurred in the program.

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."

val nreq gq: lock %x closed

Content:

An internal error occurred in the program.

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."

value failed: bad handle %x from %d

Content:

An internal error occurred in the program.

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."

value failed: NOSPACE for msg buffers

Content:

An internal error occurred in the program.

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."