PRIMECLUSTER Messages

5.1.4 Error Messages

cannot get data file configuration : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

Corrective action:

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

cfconfig: dl_bind: DL_SYSERR error
cfconfig: get_net_dev: dl_bind failed: /dev/<network interface name>

Content:

This is a message that is output when there is a network interface where CF cannot be used.

Corrective action:

No action is required if a message is output under the following environments when the OS in the global zone where the CF has not been set is restarted.

• Oracle Solaris kernel zone environment

• Oracle Solaris zone environment with an exclusive IP zone configuration network in the non-global zone

If this message is output in other cases than the above, record the 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."

cfrecon: dl_bind: DL_SYSERR error
cfrecon: get_net_dev: dl_bind failed: /dev/<network interface name>

Content:

This is a message that is output when there is a network interface where CF cannot be used.

Corrective action:

No action is required if a message is output when any of cfrecon -s, fjsnap, and fjqss_collect commands is executed in the global zone under the following environments.

• Oracle Solaris kernel zone environment

• Oracle Solaris zone environment with an exclusive IP zone configuration network in the non-global zone

If this message is output in other cases than the above, record the 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."

cfset: cfset_getconf_kernel: malloc failed : '#xxxx: %s : %s

Content:

Memory allocation failed during cfset processing.

Corrective action:

Determine why OS memory is depleted resulting in memory allocation failures.

If the error remains unsolved, 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."

cfset: /etc/default/cluster.config is not loaded successfully : '#xxxx: %s : %s

Content:

The cfset command was executed by using the option-r to load the value again from /etc/default/cluster.config file to the kernel. The operation failed.

Corrective action:

Allocation failure of OS resources due to insufficient memory or other causes is the cause of the error. Check additional messages that show the root cause of the error, to find a solution.

If no OS error was found or the problem cannot be identified, 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."

cfset_get_conf: malloc failed

Content:

Memory allocation failed during cfset processing.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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: carp_broadcast_version: Failed to announce version cip_version

Content:

This message will occur if CIP fails to initialize successfully, caused by mismatch between CIP and CF.

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: ens_nicf_input Error:unknown msg type received. (#0000 msgtype)

Content:

This message is generated by ENS when a garbled message is received from ICF. The message is dropped.

Corrective action:

As it is an information message, no action is required. However, confirm no other messages are generated before or after this message.

CF: Icf Error: (service err_type route_src route_dst). (#0000 service err-type route_src route_dst )

Content:

Communications by CF heartbeat have been failed.

Corrective action:

The heartbeat will return to its normal operation when the load is reduced. The heartbeat will return to its normal operation when the load is reduced. You can usually ignore this message if the high CPU load lasts for only a short time.

CF: Join Error: Invalid configuration: asymmetric cluster.

Content:

This message is generated when a node is joining a cluster that has a active node that does not support asymmetric clustering, and has configured an incompatible (asymmetric) set of cluster interconnects.

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: Join Error: Invalid configuration: multiple devs on same LAN.

Content:

This message is generated when a node is attempting to join or form a cluster. Multiple network interconnects cannot be attached to the same LAN segment.

Corrective action:

Change the network configuration or the interconnect device so that different LAN segments are allocated to respective inter-connects.

CF: Join postponed: received packets out of sequence from servername.

Content:

This message is generated when a node is attempting to join a cluster, but is having difficulty communicating with the node acting as the join server. Both nodes will attempt to restart the join process.

Corrective action:

No action is required.

CF: Join postponed, server servername is busy.

Content:

This message is generated when a node is attempting to join a cluster, but the join server is busy with another client node. (Only one join may be active in/on the cluster at a time.) Another reason for this message to be generated is that the client node is currently in LEFTCLUSTER state. A node cannot re-join a cluster, unless its state is DOWN. (For details on the " cftool -k" command, see the manual pages of "cftool".)

Corrective action:

If the client node is in the LEFTCLUSTER state, change to the DOWN state.
For details on how to change the state, for details on the " cftool -k" command, see the manual pages of "cftool". In other cases, no corrective action is required.

CF: Join timed out, server servername ...

Content:

There are the following messages that begin with "CF: Join time out, server servername."

CF: Join timed out, server servername did not send node number:retrying.

CF: Join timed out, server servername did not send nsm map: retrying.

CF: Join timed out, server servername did not send welcome message.

These messages are generated when a node is attempting to join a cluster, but is having difficulty communicating with the node acting as the join server. The join client node will attempt to continue the join process.

Corrective action:

This is an information message. Thus, no corrective action is required. However, when several retries fail to join a cluster check the network configuration. If possible, reboot each cluster node to see if the problem is cleared. If above actions do not help you solve the problem, 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: Local node is missing a route from node:nodename
CF: missing route on local device:devicename

Content:

These messages are generated when an asymmetric join has occurred in a cluster, and the local node is missing a route to the new node. The nodename and devicename of the associated cluster interconnect are displayed, in case this is not the desired result.

Corrective action:

To solve the problem, check if LANs (NIC, cables, and switches) that configure cluster interconnects have no problem.
Reboot the node once the error is solved.

CF: Local Node nodename Created Cluster clustername. (#0000 nodenum)

Content:

This message is generated when a node forms a new cluster.

Corrective action:

No action is required.

CF: Local Node nodename Left Cluster clustername.

Content:

This message is generated when a node leaves a cluster.

Corrective action:

No action is required.

cf:mipc  : ib_available gethostbyname: No such file or directory

Content:

This is the debug message that is generated in the RAC environment when the CF node name is different

from uname -n.

Corrective action:

To avoid display of this message, register the CF node name to /etc/inet/hosts.

CF: This kernel version is not supported.

Content:

This message is output when CF does not support the kernel version of the OS.

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): cip: Announcing version cip_version

Content:

This message is generated when a CIP initialization is complete.

Corrective action:

No action is required.

check_matching_key: malloc failed

Content:

During CF cfset processing, the configuration lookup failed due to a memory allocation failure.

Corrective action:

To solve the problem, check if an OS error that indicates why memory requirements by OS failed exists. You may need to reboot the node to recover OS memory. If no OS error was found or the problem cannot be identified, 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."

If no OS error was found or the problem cannot be identified, 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."

cluster file last updated by %s on node %s at %.24s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

cluster is using empty data file

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

cms_ack_event failed : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

cms_post_event failed: check commit event : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

commit event received without active transaction

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

compare error: key read "%s", expected key "%s"

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

compare error: key "%s" entry size = %d, expected size %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

configuration not set for remote execution request: src node %d: cmd = %s

Content:

A cfsh configuration is not set for remote command execution.

Corrective action:

Add the following entry to /etc/default/cluster.config file:

CFSH "cfsh"

Reload the values using 'cfset -r' or restart CF then retry cfsh command.

configuration not set for remote file copy request

Content:

File copy requirements by cfcp command failed on a remote node. CFCP setting variable is not set for /etc/default/cluster.config.

Corrective action:

Add the following entry to /etc/default/cluster.config file:

CFCP "cfcp"

Reload the values using 'cfset -r' or restart CF then retry cfsh command.

control event notification failed

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

corrupt file entry: key "%s" : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

corrupt sync data: key "%s": '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

data compare error: key "%s"

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

data file closed during sync

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

data file closed during transaction

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

data/temp file closed during update

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

duplicate name %s: line %d: ignored

Content:

During CF cfset processing of the /etc/default/cluster.config file, an invalid entry was found. A duplicate entry was found.

Corrective action:

Correct the specified invalid entry in /etc/default/cluster.config file and restart CF.

empty sync reply without EOF

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

ENS events dropped

Content:

An internal error occurred during the cfreg daemon process.. Cfregd will terminate.

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

error setting data file gen num : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

expected EOF

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to associate user event (index = %d) : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to chmod remote file copy tmp file : '#xxxx: %s : %s

Content:

Remote file copy failed. This is because executing chmod command could not change the permission mode of a temporary file in a destination directory to be equal to the permission mode of a source file.

Corrective action:

Check the temporary file in the destination directory to find an OS error that indicates why chmod command was not executed successfully.

If no OS error was found or the problem cannot be identified, 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."

failed to chown remote file copy tmp file : '#xxxx: %s : %s

Content:

Remote file copy failed. This is because executing chmod command could not change the owner and the group of a temporary file in a destination directory to be equal to the owner and the group of a source file.

Corrective action:

Check the temporary file in the destination directory to find an OS error that indicates why chmod command was not executed successfully.

If no OS error was found or the problem cannot be identified, 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."

failed to close remote file copy tmp file : '#xxxx: %s : %s

Content:

Remote file copy failed because a temporary file in a destination directory was not closed successfully.

Corrective action:

Check the temporary file in the destination directory to find an OS error that indicates why the temporary file was not closed successfully.

If no OS error was found or the problem cannot be identified, 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."

failed to end daemon transaction : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to find signaled event (index = %d)

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to get daemon request : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to get ENS event (index = %d) : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to get node details : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to get node id : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to get node name : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to handle left cluster : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to init user event (index = %d) : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to open remote file copy tmp file : '#xxxx: %s : %s

Content:

.A temporary file in a destination directory was not opened successfully during remote file copying.

Corrective action:

Make sure you have the write permission as a root user for the temporary file in the destination directory. To solve the problem, search the OS error that indicates why stat() system call was not executed successfully in the destination file.

If no OS error was found or the error remains unsolved, 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."

failed to register for user event (index = %d) : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to set daemon state to ready : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to set daemon state to sync : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to start daemon transaction : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failed to stat remote file copy dst : '#xxxx: %s : %s

Content:

Remote file copy by cfcp failed because stat() system call was not executed successfully in a destination file.

Corrective action:

Make sure the destination file is accessible. To solve the problem, search the OS error that indicates why stat() system call was not executed successfully in the destination file. If no OS error was found or the problem cannot be identified, 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."

failed to write to remote file copy tmp file : '#xxxx: %s : %s

Content:

Remote file copy failed as write to a temporary file in a destination directory failed.

Corrective action:

Make sure you have the read and write permissions as a root user for the temporary file in the destination directory. To solve the problem, search the OS error that indicates the cause of the failure in writing to the file in the destination directory.

If no OS error was found or the error remains unsolved, 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."

failure to ack commit event : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

failure to open cfrs device : '#xxxx: %s : %s

Content:

Remote command execution failed because the cfrs device was not opened successfully.

Corrective action:

To solve the problem, search /dev/cfrs device file or search the OS error that indicates why the device file was not opened successfully, or the OS error that indicates why the device file does not exist.

If no OS error was found or the error remains unsolved, 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."

failure to rename dstpath to %s : '#xxxx: %s : %s

Content:

Remote file copy failed as rename on the destination file failed.

Corrective action:

To solve the problem, search the OS error that indicates whey the destination file name was not renamed successfully.

If no OS error was found or the error remains unsolved, 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."

failure to set daemon info : '#xxxx: %s : %s

Content:

Failed to get the cfreg data file configuration. Cfregd will terminate.

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

failure to spawn: %s : '#xxxx: %s : %s

Content:

Remote command execution failed to spawn a process.

Corrective action:

To solve the problem, search the OS error that indicates why the process was not spawned successfully.

If no OS error was found or the problem cannot be identified, 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."

first sync request return pkg size = 0

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

fork failure : '#xxxx: %s : %s

Content:

Remote command execution failed to fork a new process.

Corrective action:

To solve the problem, search the OS error that indicates why a new process was not forked successfully.

If no OS error was found or the problem cannot be identified, 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."

fread temp output file error : '#xxxx: %s : %s

Content:

Due to remote command execution, fread on a temporary file that was created by stdio tmpfile function failed.

Corrective action:

To solve the problem, search the OS error that indicates why fread failed on the temporary file that was created by stdio tmpfile function.

If no OS error was found or the problem cannot be identified, 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."

fseek temp output file error : '#xxxx: %s : %s

Content:

fseek()on temp file created by stdio tmpfile() function failed. Because of that remote command execution with cfsh failed. Due to remote command execution, fseek on a temporary file that was created by stdio tmpfile function failed.

Corrective action:

To solve the problem, search the OS error that indicates why fseek failed on the temporary file that was created by stdio tmpfile function.If no OS error was found or the error remains unsolved,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_notification(): id %ld get a null pointer

Content:

An internal error occurred in the ELM 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_notification(): wrong context owner %ld

Content:

An internal error occurred in the ELM 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."

invalid transaction timeout node id NodeID

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

invalid usage of %s: %s

Content:

An internal error occurred when the remote command is executed.

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

line %d: name %s missing value

Content:

An invalid entry was found in /etc/default/cluster.config file. The name does not have a value.

Corrective action:

Correct the invalid entry that is specified for /etc/default/cluster.config file, and then restart CF.

line %d: name %s value too long

Content:

An invalid entry was found in /etc/default/cluster.config file. The value is too long.

Corrective action:

Correct the invalid entry that is specified for /etc/default/cluster.config file, and then restart CF.

line %d: name too long (%d max)

Content:

An invalid entry was found in /etc/default/cluster.config file. The name is too long.

Corrective action:

Correct the invalid entry that is specified for /etc/default/cluster.config file, and then restart CF.

line %d: premature EOF: last value ignored

Content:

The /etc/default/cluster.config file was not analyzed successfully.

Corrective action:

Search if the /etc/default/cluster.config file includes invalid entries. Correct the invalid entries and then restart CF.

If the error remains unsolved, 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."

line %d: value without a name: ignored

Content:

An invalid entry was found in /etc/default/cluster.config file. The combination of value and name is invalid.

Corrective action:

Correct the invalid entry that is specified for /etc/default/cluster.config file, and then restart CF.

lk_wait(): Error wrong connection

Content:

An internal error occurred in the ELM 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_wait(): Error wrong Owner

Content:

An internal error occurred in the ELM 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_wait(): wrong context owner %ld

Content:

An internal error occurred in the ELM 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."

local file last updated by %s on node %s at %.24s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

memory allocation failed (header: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (init file copy req: size = %d)

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (old data file: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (remote file copy queue entry: size = %d)

Content:

Memory allocation failed during remote file copying. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (req return: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (sub file copy req: size = %d)

Content:

Memory allocation failed during remote file copying. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (sync entry key: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (sync reply: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (sync req: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (sync request: size = %d)

Content:

Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

memory allocation failed (update infos: size = %d)

Content:

During cfreg daemon synchronization, an attempt to allocate memory failed. Memory allocation failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

missing entry with key "%s"

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

missing entry with key "%s" for delete

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

missing entry with key "%s" for modify

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

name %s: line %d: too many configuration entries (%d max) remaining entries ignored

Content:

Entries in the /etc/default/cluster.config file reached the maximum allowable numbers.

Corrective action:

Check the number of entries in the /etc/default/cluster.config file and correct the problem. Restart CF.

next sync request return pkg size = 0

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nodegroup load failed due to malloc failure

Content:

During CF initialization, memory allocation failed.

Corrective action:

To solve the problem, search the OS error that indicates why memory requirements by OS failed. You may need to reboot the node to recover OS memory.

If no OS error was found or the problem cannot be identified, 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."

nodegroup load failed due to nsi failure

Content:

An internal error occurred during CF initialization.

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

nodegroup load failed : '#xxxx: %s : %s

Content:

During the initialization of nodegroups, loading of the default values from kernel failed. Communication with cfreg subsystem failed.

Corrective action:

Check additional messages that indicate why the failure occurred.

If the error remains unsolved, 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."

nsi_getarrcnt error: init file copy data

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_getarrcnt error: request key

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_getarrcnt error: sub file copy data

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_getarrcnt error: sync reply data

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_getarrcnt error: update event data

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: check commit

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: control event

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: first sync request

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: next sync request

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: remote file copy response

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack error: sync reply

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack_buffer error: header

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack_buffer response error

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack_size error: header

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_pack_size error: sync reply

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_setarrcnt error: init file copy data

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_setarrcnt error: request key

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_setarrcnt error: sub file copy data

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_setarrcnt error: sync reply data

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_setarrcnt error: sync request key

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_setarrcnt error: update event data

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: commit event

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: daemon down event

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: first sync request return

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: init file copy request

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_unpack error: next sync request return

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: sub file copy request

Content:

An internal error occurred during remote file copying. Cfregd will terminate.

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

nsi_unpack error: sync reply

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: sync request

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

nsi_unpack error: update event

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

open %s : '#xxxx: %s : %s

Content:

During cfset processing, an open of the cfset file /etc/default/cluster.config failed.

Corrective action:

Check that the file exists and file permissions then retry command.

If the error remains unsolved, 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."

OSDU_open_symsrv: failed to open /dev/symsrv: #%04x: %s: %s

Content:

Open of the /dev/symsrv device failed.

Corrective action:

Check for /dev/symsrv device file and any associated OS messages indicating why the device file open failed or is not present. 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."

OSDU_select_nic: %s not a selectable device

Content:

While managing a cluster device, an internal error occurred. The specified cluster device could not be added to the configuration.

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

OSDU_start: CF configured invalid IP address %s

Content:

The CF startup routine has failed. This error message usually indicates that IP address described in the CF configuration file (/etc/default/cluster) is invalid.

Corrective action:

Review the settings in the CF configuration file (/etc/default/cluster).

OSDU_start: CF configured IP device %s not available

Content:

During CF startup of a CF over IP configuration, the specified IP device is not valid.

Corrective action:

Refer to the cfconfig man page. Valid IP devices are /dev/ip0, /dev/ip1, /dev/ip2, or /dev/ip3. Correct the invalid configuration and restart CF.

OSDU_start: CF configured too many IP addresses %s

Content:

The CF startup routine has failed. This error message usually indicates that too many IP addresses are described in the CF configuration file (/etc/default/cluster).

Corrective action:

Review the settings in the CF configuration file (/etc/default/cluster).

OSDU_start: Could not get configuration:
The fast start option requires a valid configuration file.

Content:

During CF startup with option '-L', the /etc/default/cluster file was not analyzed successfully.

Corrective action:

Check that the file exists and file permissions then restart CF.

If the error remains unsolved, 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."

OSDU_start: failed to load the driver

Content:

The cf driver could not be loaded into the kernel. CF cannot start.

Corrective action:

Check OS messages that indicate why driver load failed.

If no OS error was found or the problem cannot be identified, 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."

OSDU_start: failed to load the symsrv driver

Content:

The symsrv driver could not be loaded into the kernel. CF cannot start.

Corrective action:

Check OS messages that indicate why driver load failed.

If no OS error was found or the problem cannot be identified, 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."

OSDU_start: failed to open /dev/linux (%s)

Content:

During CF start processing, an open the /dev/linux failed. CF startup cannot continue.

Corrective action:

Check OS messages that indicate why device open failed.

If no OS error was found or the problem cannot be identified, 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."

OSDU_start: failure to determine boot time

Content:

During CF startup, determination of node boot time using /proc/uptime failed. The boot time cannot be determined.

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

OSDU_start: LINUX_IOCTL_SETCONF ioctl failed

Content:

During CF startup, initialization of cluster device configuration failed. CF startup cannot continue.

Corrective action:

Check additional messages to identify the problem.

A specified cluster device may not be found due to an invalid configuration. Check the configuration that specifies the cluster device names.

If the error remains unsolved, 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."

OSDU_stop: enable unload failed

Content:

During CF stopping process, the driver unload failed. A CF device file may be open.

Corrective action:

Check the message file for additional information on which process still opens the CF device file and prevents the unload. Stop the specified process or product to shut down CF again.

rcqconfig failed to configure qsm due to cfreg failure.

Content:

An internal error occurred during CF initialization.

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

rcqconfig failed to configure qsm due to cfreg_put failure.

Content:

An internal error occurred during CF initialization.

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

rcqconfig failed to configure qsm due to ens post eventy failure.

Content:

An internal error occurred during CF initialization.

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

read entry with key "%s"

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

received remote service request during sync phase

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

received sync request during sync phase

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

received transaction timeout request during sync phase

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

received wrong ENS event (received 0x%x, expected 0x%x)

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

remote file copy destination not regular file

Content:

The destination file specified for CF remote copy (cfcp) is not a regular file.

Corrective action:

Either specify a different location as destination for remote copy or rename the existing destination file.

response buffer size too large: %d

Content:

An internal error occurred when the remote command is executed.

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_request: bogus return value %d

Content:

An internal error occurred in the ELM 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."

starting transaction without empty temp file

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

starting transaction without open data file

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync compare data overflow: size %d expected 0

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync data overflow: %d expected 0

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync data too small for compare: %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync reply data size corrupt: entsize = %d, datasize = %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync reply data size corrupt: size = %d, datasize = %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

sync reply data too small: %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

temp file not open

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

transaction handle validation error : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

uev_wait failed : '#xxxx: %s : %s

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

unknown update type %d

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

wait failure : '#xxxx: %s : %s

Content:

Wait process failed while the remote command is executed to end the child process.

Corrective action:

To solve the problem, search the OS error that indicates why the wait process failed.

If no OS error was found or the problem cannot be identified, 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."

%s: cannot create

Content:

A file was not opened successfully during cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the open process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: close failure

Content:

The cfreg data file was not closed successfully by the cfreg daemon. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the close process failed. Reboot of the node may be necessary to resolve IO problems. If no OS error was found or the problem cannot be identified, 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."

%s: failed to open for read

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

%s: failure to remove : '#xxxx: %s : %s

Content:

Old cfreg data files were not deleted successfully. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why the data files were not deleted successfully.

If no OS error was found or the problem cannot be identified, 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."

%s: failure to rename to %s

Content:

The cfreg data file was not renamed successfully during the cfreg daemon process. Cfregd will terminate.

Corrective action:

To solve the problem, search the OS error that indicates why the file was not renamed successfully. Reboot of the node may be necessary to resolve IO problems.

If no OS error was found or the problem cannot be identified, 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."

%s: failure to rename to dstpath : '#xxxx: %s : %s

Content:

Remote file copy failed as rename on the destination file failed.

Corrective action:

Check for OS errors that may indicate why rename on the temporary file in destination directory is failing. To solve the problem, search the OS error that indicates why the temporary file in the destination directory was not renamed successfully.

If no OS error was found or the problem cannot be identified, 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."

%s: fseek 0 failed

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

%s: fwrite entry returned %d, expected %d

Content:

The write process failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the write process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: fwrite entsize returned %d, expected %d

Content:

The write process failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the write process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: fwrite header returned %d, expected %d

Content:

The write process failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the write process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: fwrite sync data returned %d, expected %d

Content:

The write process failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the write process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: fwrite update info returned %d, expected %d

Content:

The write process failed during the cfreg daemon process. Cfregd will terminate.

Corrective action:

Search the OS error that indicates why the write process failed. If the problem is identified and corrected, restart the cfreg daemon.

If no OS error was found or the problem cannot be identified, 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."

%s: not open for write

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

%s: read error : '#xxxx: %s : %s

Content:

The cfreg data file cannot be read. Cfregd will terminate. Either the file is corrupted or there are IO related OS problems.

Corrective action:

Make sure the cfreg data file has read/write permissions for root. Check for OS errors that may indicate why reading a file failed. Make sure you have the read and write permissions as a root user for the cfreg data file. If you have the root permissions, search the OS error that indicates why the file was not read successfully, to solve the problem.

If no OS error was found or the problem cannot be identified, 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."

%s: synchronization failed

Content:

An internal error occurred during the cfreg daemon process. Cfregd will terminate.

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

/etc/default/cluster.config is not loaded successfully : '#xxxx: %s : %s

Content:

During the cfset process, en entry was not loaded to the kernel successfully.

Corrective action:

This may be a result of a OS resource allocation failure such as memory depletion. Check for other messages that may further indicate the cause of the problem. If the problem cannot be identified, 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."