2652-511 | Error: file file type does not match type of CFM file. file will not be updated. |
Explanation: The file types are different: perhaps one is a directory and the other is a file.
User Response: Ensure that both files are of the same type (both directories or both files).
2652-512 | Error: Unable to make destination directory directory. |
Explanation: None.
User Response: Check the permissions on the parent directory.
2652-513 | Error: Cannot close directory directory. |
Explanation: None.
User Response: None.
2652-514 | Copy copy command reported exit code exit code and gave this error: error message. |
Explanation: Command failed.
User Response: None.
2652-515 | This command command name reported this exit status: exit code, and this error: error message. |
Explanation: Command failed.
User Response: None.
2652-516 | Error: cannot transfer file: file. It does not have the same owner or group as the version on the management server. |
Explanation: The user and group are not consistent with the version of the file on the management server.
User Response: None.
2652-517 | Error: Cannot open directory: directory. |
Explanation: None.
User Response: None.
2651-526 | There is a version of file file for a group as large as the entire cluster as well as a version of it for all nodes. CFM will disregard the all node version and only transfer the group version. |
Explanation: If there is a group as large as the cluster, it contains all the nodes in the cluster. Therefore you should not need to have filename._group since this has the same destination as filename.
User Response: Ensure that you do not have two files with the same CFM destination. Make sure that if there are multiple versions of a single file, that each of their destinations is unique.
2651-527 | There are 2 groups of the same size, node group and node group, that both receive different versions of the file file. Any nodes common to both groups will receive the node groupversion. |
Explanation: Since both groups are the same size, CFM does not know which to consider more specific and, therefore, it arbitrarily chooses a group in which to include the common nodes.
User Response: None.
2651-528 | File filedoes not have a Group Name extension. |
Explanation: The filename includes a ._ but the text following it does not match a defined group name. This file will be sent to all nodes, and no extension will be removed.
User Response: To stop this error from occurring, rename the file so that it does not include a ._
2651-529 | Warning: file is wrong type. It will not be distributed. |
Explanation: The target is not a file or directory.
User Response: Check the format of the file and remove it from the /cfmroot directory if it is not a valid type (directory, file, or symbolic link).
2651-530 | Rdist: rdist error. |
Explanation: Displays error reported by rdist.
User Response: None.
2651-531 | Error: Cannot open file. errorerror. Please ensure you have permission to read and write to this file (if you do not, contact the system administrator). |
Explanation: None.
User Response: None.
2651-533 | Node hostname is offline (Status = Status). CFM files will not be distributed to it. |
Explanation: The ManagedNodeStatus attribute of the node is not 1. This indicates that something is wrong with the node.
User Response: Try running the updatenode command to the node. If this does not fix the problem, ensure the node is reachable on the network.
2651-534 | Error: Cannot open file: error error. |
Explanation: None.
User Response: None.
2651-535 | Error: Cannot close file: error error. |
Explanation: None.
User Response: None.
2651-538 | Cluster System Management nodegrp command could not resolve node group node group. |
Explanation: Either an underlying resource manager is down, or you specified an invalid node group.
User Response: Ensure that the specified node group exists. Check to make sure that the relevant resource managers are running with lssrc -a.
2651-539 | CFM cannot resolve hostname hostname. No files will be sent to this machine! |
Explanation: Either the Domain Management resource manager is down, or you specified an invalid node name.
User Response: Ensure that the specified node is a CSM ManagedNode. Then, check to make sure that the Domain Management resource manager is running with lssrc -a.
2651-540 | No valid destinations. CFM will not run! |
Explanation: None.
User Response: None.
2651-541 | The file or directory file has more than one ._groupname extension. CFM does not know where to send it. file will not be distributed! |
Explanation: None.
User Response: Make sure that no file names or paths contain multiple ._groupname extensions.
2651-542 | Both file and file have the same destination! In order to keep the wrong files from going to this destination, CFM will not send either version. Please fix your /cfmroot directory to ensure each destination file has a unique CFM file. |
Explanation: None.
User Response: None.
2651-543 | Host hostname is probably out of file system space. CFM received this error: errorerror. CFM will not be able to distribute files to hostname at this time. |
Explanation: A file system on the node is full.
User Response: Ensure that there is room on the file system to which CFM is copying and /var/opt/csm (where the temporary files are stored).
2651-544 | No space left on host hostname. CFM files were not successfully distributed. |
Explanation: A file system on the node is full.
User Response: Ensure that there is room on the file system to which CFM is copying and /var/opt/csm (where the temporary files are stored).
2651-545 | File file name failed to transfer to hostname. command name will retry distribution of this file one time. |
Explanation: None.
User Response: None.
2651-546 | There is a current execution of command name. Please wait until this existing process exits before trying to run command name. Otherwise remove the file file name. |
Explanation: The /tmp file that corresponds to the command is locked.
User Response: Remove the file, if no other execution of cfmupdatenode is running.
2651-547 | Cannot run /usr/bin/rdist: error codeexit code. |
Explanation: An error occurred while running /usr/bin/rdist.
User Response: None.
2651-548 | The dsh command returned this exit code: exit code. It probably failed to reach some nodes. |
Explanation: None.
User Response: Ensure that you can run the dsh command to all nodes. Run a command similar to /opt/csm/bin/dsh -a hostname.
2651-549 | Rdist returned this exit code: rdist exit code. Some files may not have been distributed to all nodes! |
Explanation: There was a problem distributing the files.
User Response: Run cfmupdatenode again to ensure that all files transfer.
2651-550 | There is no target for the cfmupdatenode command. Please specify a target with the -a, -N or host positional arguments. |
Explanation: None.
User Response: None.
2651-551 | Deletion of temporary CFM files failed on node hostname. No file transfer to this node will take place. |
Explanation: CFM distributes temporary files to the /var/opt/csm/cfmlocal directory on each destination machine. When the corresponding files are removed from /cfmroot on the management server, CFM tries to delete them from the /var/opt/csm/cfmlocal directory.
User Response: Manually delete all files from the /var/opt/csm/cfmlocal directory on the specified node.
2651-552 | The file file is either not a file or it does not reside in the /cfmroot directory. It will not be distributed. |
Explanation: You ran cfmupdatenode -f filename with an invalid file.
User Response: Ensure that the file exists in the /cfmroot directory, and is a valid file type (directory, file, or symbolic link).
2651-553 | CSM: :CLOG call subroutine name failed with return code return code. |
Explanation: Problem with the CSM CLOG component. It is possible that logging the sys/audit logs was unsuccessful.
User Response: None.
2651-554 | Command child command failed with error error message. |
Explanation: None.
User Response: None.
2651-556 | The user group numeric user of or group id does not exist on some target nodes. Files owned by this user or group will not be distributed. |
Explanation: Users and groups of files in /cfmroot must exist on all machine in the cluster (with the same user and group identifier).
User Response: Ensure that the user or group exists on all target nodes with the same numeric identifier.
2651-557 | clocal reported exit code exit codeon node hostname. File transfer may have failed on that node. |
Explanation: None.
User Response: None.
2651-558 | The following two groups, node group and node group, contain common nodes, but have different versions of the same file defined for them. Since group node group is smaller and more specific, all common nodes will receive its files. |
Explanation: None.
User Response: None.
2651-559 | Files with the destination name file have different owners or groups. They will not be distributed. |
Explanation: None.
User Response: None.
2651-560 | This file file is not owned by the executing user. It will not be distributed. |
Explanation: None.
User Response: None.