| 2545-001 | Command command name was unsuccessful. rc=return code. |
Explanation: The invoked command was unsuccessful with the return code specified.
User Response: Execute the command from the prompt to diagnose the problem. Correct the problem and enter the command again.
| 2545-002 | The -g option supported only from CWS. |
Explanation: The command has been invoked with the -g option from a node. However, the -g option can be used only when the host is the control workstation.
User Response: Use the command with the -g option from the control workstation.
| 2545-003 | Usage: program name [-h] |
Explanation: There is a syntax error in the command line options used.
User Response: See the usage message and the man page for the command to find the correct syntax of the command line options.
| 2545-004 | Opening file file name for writing was unsuccessful. |
Explanation: Opening the specified file for writing was unsuccessful.
User Response: If the file exists, verify that you have write permission for the file. If the file does not exist, check the write permission of the directory in which the file is to be created. Correct the problem and enter the command again.
| 2545-005 | Opening file file name for reading was unsuccessful. |
Explanation: Opening the specified file for reading was unsuccessful.
User Response: Verify that the file exists and that you have read permission. Correct the problem and enter the command again.
| 2545-006 | Could not obtain DCE hostname(s) from SDR for nodes. Local /.k5login file will not be updated. |
Explanation: A problem has been found in retrieving the dcehostname attribute from the SDR Node object.
User Response: The create_dcehostnames command may not have run successfully. The dcehostnames for each node must exist in the SDR. Ensure the create_dcehostnames command has run and was successful. Use the SDRGetObjects command to retrieve and display the dcehostname attribute of Node object for all nodes. Correct SDR problems and enter this command again.
| 2545-007 | Executing the updauthfiles command on remote nodes (through dsh) was unsuccessful on one or more remote nodes as indicated below: |
Explanation: The control workstation has run the command on the nodes using the dsh command. The updauthfiles command was unsuccessful on at least one remote node. The list of nodes on which the command was unsuccessful is printed after this problem message.
User Response: Use the logfile /var/adm/SPlogs/auth_install/log file on each remote node to diagnose the problem on that node.
| 2545-008 | Could not obtain valid CWS DCE hostname from SDR. Local /.k5login file will not be updated. |
Explanation: A problem has been found in retrieving DCE hostname of the control workstation from the SDR.
User Response: Check to see if the control workstation dcehostname attribute of the SP object in the SDR exists and is not empty. Correct the problem and enter the command again.
| 2545-009 | Executing dsh was unsuccessful because a remote command to one or more remote nodes was unsuccessful. The dsh output indicating remote command problems follows: |
Explanation: The dsh execution was unsuccessful since a remote command to one or more nodes was unsuccessful. Those nodes may be down or there may not be any common authentication mechanism turned on for remote commands to use. The list of nodes on which the remote command was unsuccessful appears after this problem message. The updauthfiles command is not run locally on those nodes.
User Response: Identify the nodes for which the remote command was unsuccessful and check to see if they are down. There is no problem if a node is down, since the updauthfiles command will be run locally on the node on its next reboot. If the node is up and running and the remote command was unsuccessful, turn on any common authentication mechanism between the control workstation and the node.
| 2545-010 | Unexpected errors: dsh to update authorization files in remote nodes is suspended beyond timeout value of timeout value seconds. |
Explanation: The updauthfiles command is run in all the nodes through the dsh command. The remote command to at least one node hangs, causing the dsh command to hang.
User Response: See the process status to check the hanging dsh and remote commands. The hanging remote command, as seen by the ps command, indicates the set of nodes on which the remote command is hung. This may occur when the nodes are hanging, but not when they are down.
The nodes that are hung may have to be rebooted. If the nodes are not really hung, enter the updauthfiles command with a higher timeout value. Note that the default timeout value is assumed if the timeout value is not specified.
| 2545-011 | Was unable to copy .klogin from directory to directory |
Explanation: Program was unable to copy the .klogin file from the stated directory to another directory.
User Response: Ensure proper permissions for the 'to directory', ensure enough space available in the 'to directory' file system. Rerun the command after you have corrected the problem.
| 2545-012 | An error occurred in trying to remote copy file file_name was unsuccessful with rc=return_code |
Explanation: Remote copy was unsuccessful. Either you do not have proper authority to issue the remote copy, or the file does not exist
User Response: Ensure you have proper authority to do the remote copy and ensure that the file exists. Then, enter the command again.
| 2545-020 | DCE dce level (2.2) or greater must be installed on the control workstation prior to running this command. |
Explanation: The specified level of DCE is required for this level of PSSP software.
User Response: Ensure that the proper level of DCE is installed, configured, and running on the control workstation prior to running this command.
| 2545-021 | Command syntax error. Incorrect or missing arguments. |
Explanation: A required option was missing, or an incorrect argument was supplied.
User Response: Refer to the command syntax displayed and enter the command with the correct syntax.
| 2545-022 | Error with SDR read operation for SDR object object. |
Explanation: An error occurred while trying to issue the SDRGetObjects command for the specified object.
User Response: Ensure that the object and its attributes exist. The problem may be due to not running previous steps to create or update the objects in the SDR.
| 2545-023 | Could not change attribute, attribute, in the SDR. SDR returned rc = SDR return code. |
Explanation: The program was not able to update the value of the specified attribute. This could occur because the SDR daemon is not running, the object is not in the SDR, or the SDR is corrupted.
User Response: Review any previous error messages pertaining to the SDR, ensure that the SDR is running, and enter this command again.
| 2545-024 | DCE was selected as an authentication method and is required to be installed, configured, and running for htis program to continue. |
Explanation: This program requires that the DCE be functional to obtain information from the DCE databases to configure the SP to use DCE.
User Response: Review the messages to determine the state of DCE. Correct as appropriate and enter the command again.
| 2545-025 | This command must be run on the Control Workstation only. |
Explanation: This command configures the DCE database with node information. The control workstation has all the required information available and must already be configured for DCE. DCE must be running.
User Response: Run the command on the control workstation.
| 2545-026 | The -u option requires UNIX root authority. |
Explanation: The command has been invoked with the -u option, by a user other than root.
User Response: Login as root, and enter the command again.
| 2545-027 | Could not create a temporary response file in /tmp for use with config.dce command. |
Explanation: The program was unsuccessful trying to create a temporary file in /tmp directory.
User Response: Check if /tmp file system has enough space. Fix the problem and enter the command again.
| 2545-028 | Problems encountered trying to do an \"admin\" \ client configure of the nodes. Refer to DCE configure log \"/opt/dcelocal/etc/cfgdce.log\" for more information. |
Explanation: Running config.dce for admin configuring all the nodes was unsuccessful. There may be problems in creating principals.
User Response: Check if DCE registry is not corrupted. Fix the problem and enter the command again. Refer to any msgs found in /opt/dcelocal/etc/cfgdce.log for more information.
| 2545-029 | Command syntax error. The flag flag requires a hostname. |
Explanation: A hostname was expected following the specified flag.
User Response: Enter the command again with a hostname for the stated flag.
| 2545-030 | DCE is not installed on this machine. |
Explanation: DCE must be installed, configured, and running for this program.
User Response: None
| 2545-031 | DCE is not configured on this machine. |
Explanation: DCE must be installed, configured, and running for this program.
User Response: None
| 2545-032 | Could not open file \"/etc/dce/cfg.dat\". This file is used to determine if DCE is configured at the right levels. |
Explanation: Program attempted to open file and was unsuccessful.
User Response: File is required to determine the state of DCE on this machine. This file is created by DCE and should have the appropriate read bits set. Check the file to ensure you have read permission and enter the command again.
| 2545-033 | DCE is not running on this machine. The command dcecp -c keytab catalog was used to determine if DCE is running. The command output is: |
Explanation: Program attempted to open file and was unsuccessful communicating with DCE. There may be some networking problems which may cause DCE to not allow client to server communication.
User Response: Review any additional messages produced by the command. Using the DCE help text, determine the cause of the problem, correct as appropriate, and enter this program again.
| 2545-034 | DCE is installed but not at the minimum level required. The minimum level required is Minimum version of DCE. |
Explanation: This level of PSSP requires the stated level of DCE.
User Response: If this is a node, refer to the DCE documentation for upgrading DCE. Since DCE was selected as an authentication method for the node, and DCE could not be correctly installed, 'dce' will be removed from the node's authentication settings and use. This may leave the node without any authentication methods, and therefore leave the node without remote command or trusted services functions.
| 2545-040 | No authentication or authorization methods were specified on the command line. |
Explanation: The authentication or authorization methods must be specified on the command line. For example: k4, std.
User Response: Refer to the syntax of the command and enter the command with the proper syntax and options.
| 2545-041 | Error with SDRChangeAttrValues. SDR returned rc = SDR return code. |
Explanation: An error occurred while updating the SDR.
User Response: Check to ensure that the SDR is running and enter the command again.
| 2545-042 | Syntax error. Either -i and -d flags were specified together or neither flag on the command line. |
Explanation: The -i and -d flag are mutually exclusive and one must be specified.
User Response: Enter the correct syntax for the command.
| 2545-043 | updauthfiles command was unsuccessful with return code updauthfiles return code. |
Explanation: The updauthfiles command was unsuccessful. It may or may not be fatal. Possible reasons for the problem include: the SDR is not running, or the node itself is not running or the node is not configured to allow remote authorization.
User Response: The node must be up and running for the updauthfiles command to run. Some authorization must be available on the node to allow for remote execution of the command. In the case of a node being down, when it is rebooting, the node will correct or update its own authorization files. After rebooting the node, you must run the updauthfiles command on the control workstation to update all the other nodes.
| 2545-044 | This command must be run from the control workstation only. |
Explanation: The updauthfiles command should not be run from nodes.
User Response: Run the command from the control workstation only.
| 2545-045 | Missing authentication method is an additional required setting for this command due to other authentication attributes. These other attributes were set by spsetauth -d, or chauthpar, or chauthpts. |
Explanation: The complete set of authentication capabilities for this partition is required to be the union of all other partition sensitive authentication methods. These methods are for authorization of root user of AIX Remote Commands set using the spsetauth -d command, Enablement of Authentication methods for AIX Remote Commands set using chauthpar, and SP Trusted Services Authentication methods set using chauthpts.
User Response: Run the command with the required set of methods.
| 2545-046 | The set authorization methods to be set is not valid. There must be at least one common method between Authorization methods and Authentication methods for AIX Remote Commands. |
Explanation: There needs to be at least one common authentication method between Authorization for AIX Remote Commands and the Enabling of Authentication methods for AIX Remote Commands. Otherwise, AIX remote commands will not function properly.
User Response: Run the command with a proper set.
| 2545-047 | The set auth methods to be set is not valid; Either k4 or compat must be included since there is at least one node in the partition running a PSSP code level prior to 3.2.0.0. |
Explanation: There is at least one node running a PSSP code level less than 3.2.0.0. These earlier code levels require that Kerberos Version 4 authentication be set.
User Response: Enter the command again adding either k4 or compat.
| 2545-048 | After processing, there are no authentication methods to set. Review previous error messages to determine the cause of the problem. |
Explanation: The program verifies all settings, and those settings which are not valid are removed from the list to be set. If all are removed, there is nothing to set. Previous messages will state which methods were removed.
User Response: Enter the command again with a proper set of methods.
| 2545-049 | Authorization method to be set is not valid for this command because it is not in the list of Authentication Capabilities, which is set by spsetauth -i command. |
Explanation: In order to set an authorization method, the method must be set as a method to used on the node. There must be a one-to-one correlation to Authentication Capabilities and Authorization methods.
User Response: Either add this method to the set for Authentication Capabilities using the spsetauth -i command, or enter this command without this method.
| 2545-050 | Syntax error. Missing -p flag and its parameter. |
Explanation: The -p flag is required.
User Response: Enter the correct syntax for the command.
| 2545-051 | Kerberos V4 is required to be installed on this machine to select k4 as an authentication method. |
Explanation: The program determined that Kerberos Version 4 was not installed on the local machine. Kerberos Version 4 is required to be installed when selecting k4 as an authentication method.
User Response: Run setup_authent to install Kerberos Version 4 on this machine and then issue spsetauth.
| 2545-052 | Syntax error. Duplicate parameters specified. |
Explanation: Multiple occurrences of the same authentication method was specified.
User Response: Enter the correct syntax for the command.
| 2545-053 | The method "none" cannot be set unless "Remote command method" in the site environment is set to "secrshell". |
Explanation: Setting "none" as a remote command authorization method requires "Remote Command Method" program in the site environment to be set to "secrshell".
User Response: Use either the smit enter_data or spsitenv commands to modify the "Remote Command Method" (rcmd_pgm) to be "secrshell" and run spsetauth command.
| 2545-054 | The method "none" cannot be set unless all nodes in the partition are equal to or greater than PSSP 3.4 software level. |
Explanation: Setting "none" as a remote command authorization method requires all nodes in the partition to be at level PSSP 3.4 or higher.
User Response: Update all nodes in the partition to the proper level and run this command.
| 2545-060 | Incorrect flag or argument specified on the command line. |
Explanation: An incorrect flag or argument to a flag was specified.
User Response: Refer to the command syntax and enter the command again.
| 2545-061 | This command is to be executed on a node. |
Explanation: This command will run only on a node. It does not run on the control workstation.
User Response: Run this command on a node.
| 2545-062 | An error occurred while configuring DCE on the node. The error output from the config.dce command: |
Explanation: There was a problem while configuring DCE on this node. The invoked config.dce command was unsuccessful. The output from config.dce is printed following this message.
User Response: Examine the output from the config.dce command to determine the cause of the problem.
| 2545-063 | The Node objects lppsource_name attribute was not set in SDR. |
Explanation: This attribute does not have any value, which is required to find the DCE file sets for installing on the node.
User Response: Run the spsitenv command to set the name of the install image directory. Run this command again.
| 2545-064 | Could not mount the LPPSOURCE directory LPPSOURCE directory name. This directory needs to be exported from the control workstation as read-only. |
Explanation: The updauthfiles command could not mount the lppsource directory.
User Response: Ensure that the directory is exported as read-only to all the nodes and enter this command again.
| 2545-065 | An error occurred while installing the file sets: DCE file sets. |
Explanation: One or more of the DCE file sets was unsuccessful to install.
User Response: Refer to previous messages about the installation. Correct the problems and enter this command again.
| 2545-066 | An error occurred when attempting to set the authentication methods for the node. |
Explanation: An error occurred while running the chauthent command.
User Response: Refer to any messages pertaining to the chauthent command. Correct the problem and enter the command again.
| 2545-067 | An error occurred while trying to read data from the SDR. |
Explanation: An SDR read error occurred.
User Response: Determine the cause of the SDR read error, and enter this command again.
| 2545-068 | An error occurred while starting DCE on the node. The error output from the start.dce command: |
Explanation: An error occurred while the start.dce command was running. The output from the start.dce command is printed following this message.
User Response: Examine the output from the start.dce command to determine the cause of the problem.
| 2545-069 | Could not enable k5 authentication method since SDR auth_install attribute does not contain DCE. |
Explanation: The auth_methods attribute in the Syspar SDR object includes k5, but the auth_install attribute does not contain DCE. No attempt has been made to enable Kerberos on the node due to this inconsistency.
User Response: Update the auth_install SDR attribute to include DCE, as desired. Or update the auth_methods SDR attribute to remove k5, as desired.
| 2545-070 | Command command name had messages returned from the command. Check the messages to determine if the command executed successfully. rc=return code. |
Explanation: The invoked command has returned messages from the command.
User Response: See the logfile of the command for more details, if it exists.
| 2545-071 | An error occurred when attempting to set the trusted services authentication methods for the node. |
Explanation: An error occurred while running the chauthts command.
User Response: Refer to any messages pertaining to chauthts, correct any problems, and run this command.
| 2545-072 | Missing or incomplete DCE filesets in lppsource directory: lppsource directory. |
Explanation: This program tests to ensure that the fileset dce.cds.ret is present in the lppsource directory. If present, DCE can be installed.
User Response: Ensure all DCE filesets are available in the lppsource directory, then enter this command again.
| 2545-073 | "mkitab" returned with rc=return code. Entry may not be in /etc/inittab correctly. |
Explanation: An error occurred when creating the itab entry. The most common cause is insufficient authority or a file system problem.
User Response: Review the error. If it is an authority issue, ensure you have proper authority to update /etc/inittab. If it is a file system problem, most likely a file system full error, correct the problem and enter this command again.
| 2545-074 | Command command name was unsuccessful. Output from command: |
Explanation: The specified command was unsuccessful. The output from that command is displayed.
User Response: Review the output from the command to determine the problem and, if possible, correct and enter the program again.
| 2545-080 | DCE is not running. DCE is required in order to create DCE hostnames. |
Explanation: DCE is not running on this host. DCE is required for the updauthfiles command.
User Response: Ensure that DCE is installed, configured, and running on the control workstation; then enter the updauthfilescommand.
| 2545-081 | Error reading SDR data. Unable to access SDR to obtain information. |
Explanation: An SDR read error occurred.
User Response: Determine the cause of the SDR read error, and enter this command.
| 2545-082 | Error obtaining DCE host principals. Problem using dcecp, or DCE access error. |
Explanation: A dcecp operation on the host catalog entries was unsuccessful. The dcecp -c host catalog command is required to host entries from the DCE database.
User Response: Ensure that dcecp is installed in: /opt/dcelocal/bin. Ensure that DCE is configured properly. Enter the updauthfiles command again.
| 2545-083 | Problems with updating SDR attributes. Review logfile for additional messages. |
Explanation: A call to the SDRChangeAttrValues command was unsuccessful. See the log file for details.
User Response: Review the log file to determine which SDR command had a problem. Ensure that the SDR is operational and enter the command.
| 2545-084 | Invalid flag or argument specified on the command line. |
Explanation: An incorrect flag or argument to a flag was specified.
User Response: Refer to the command syntax and enter the command again.
| 2545-085 | This command runs only on the control workstation. |
Explanation: This command should not be run from nodes.
User Response: Run the command from the control workstation only.
| 2545-090 | Unable to create directory directory name. No logging will occur. |
Explanation: The command could not create the file.
User Response: Ensure enough space is available in the file system for the file to be created and enough space for data to be logged in this file. Enter this command again.
| 2545-091 | Unable to open file logfile namefor writing. Logging of error messages will not occur. |
Explanation: The command could not open the named file for write.
User Response: Ensure the directory and file have write permission. Enter the command after you have corrected the problem.
| 2545-100 | Could not open file /var/adm/SPlogs/kfserver/regserver.log. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error. A possibility is a full file system.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-101 | Could not create socket. error text. |
Explanation: A socket() system call was not successful. The reason is explained by the error text.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-102 | Could not set socket options. error text. |
Explanation: A setsockopt() system call was not successful. The reason is explained by the error text.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-103 | Could not bind to port port number. error text. Trying the next port. |
Explanation: The program could not bind its socket to the indicated port. The program will continue, increasing the port number until an available port is found.
User Response: None.
| 2545-104 | Could not open file /etc/inetd.conf. error text. |
Explanation: The command needs to update the /etc/inetd.conf file, but could not open it. The reason is explained by the error text.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-105 | kfcli service is already defined in /etc/inetd.conf. |
Explanation: There is already an entry for a service named kfcli.
User Response: Remove the existing entry or rename it, then re-issue the command.
| 2545-106 | Could not add kfcli service to /etc/inetd.conf. |
Explanation: The program could not append a line to the file to define the kfcli service. There may be a file system problem.
User Response: Follow standard problem resolution procedures.
| 2545-107 | Could not add kfcli service to /etc/services. |
Explanation: The program could not append a line to the file to define the kfcli service. There may be a file system problem.
User Response: Follow standard problem resolution procedures.
| 2545-108 | Could not refresh inetd. |
Explanation: The program could not refresh the inetd daemon after registering the kfcli service.
User Response: Follow standard problem resolution procedures.
| 2545-109 | Could not create SP_ports object for kfserver daemon. SDRCreateObjects return code: return code. |
Explanation: The command could not save the port information in SDR. The SDR command returned the error code indicated.
User Response: Follow standard problem resolution procedures.
| 2545-110 | Required fileset fileset is not installed. |
Explanation: setup_CWS requires specific file sets to be installed. During program processing, the stated file set was not found.
User Response: File sets required may be bos.net.uucp, which is needed for systems using kerberos V4, because it contains the uuencode and uudecode code for encoding of srvtab files that are sent over the s1term line.
| 2545-111 | Was unable to copy file to file/directory. |
Explanation: The AIX cp command failed.
User Response: Refer to the message given by the cp command and correct the problem. A possible problem is that the receiving directory does not exist. Create the directory and run this command again.
| 2545-113 | KF_PORT was not set - trying port 32801. |
Explanation: This command expects the KF_PORT environment variable to be set to the port used by the kfserver daemon on the control workstation. The default port number is used instead.
User Response: Check to make sure that the port number for the kfserver daemon is saved in an SP_ports object in the SDR. If not, run the setup_CWS command to save it. If the problem persists, follow normal problem reporting procedures.
| 2545-114 | The KF_PORT value is not numeric. |
Explanation: This command expects the KF_PORT environment variable to be set to the port used by the kfserver daemon on the control workstation. It was set to a non-numeric value.
User Response: Check to make sure that the port number for the kfserver daemon is saved in an SP_ports object in the SDR. If not, run the setup_CWS command to save it. If the problem persists, follow normal problem reporting procedures.
| 2545-115 | Could not determine IP address of kfserver host hostname. |
Explanation: The command could not obtain the IP address of the kfserver host using the inet_aton subroutine.
User Response: Check for a networking problem accessing the control workstation from the node. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-116 | Could not create socket. error text. |
Explanation: A socket() system call was not successful. The reason is explained by the error text.
User Response: Take corrective action based on the error text and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-117 | Could not connect to kfserver. error text. |
Explanation: The command could not establish a socket connection with the kfserver daemon on the control workstation.
User Response: Check that the kfcli service is defined in the /etc/inetd.conf and /etc/services files on the control workstation, and that inetd was refreshed successfully. You may find information in the log file /var/adm/SPlogs/kfserver/regserver.log on the control workstation. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-118 | Could not open keyfile for writing. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error. A possible cause is a full file system.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-119 | Could not open /dev/tty0. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error. A possible cause is a full file system.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-120 | Could not close socket. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-130 | Could not open file /var/adm/SPlogs/kfserver/kfserver.log.PID. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error. A possible cause is a full file system.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-131 | getpeername STDIN was unsuccessful. error text. |
Explanation: The perl function getpeername did not return the socket information for STDIN. The error text gives more information about the error.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-132 | unpack_sockaddr_in was unsuccessful. error text. |
Explanation: The perl function unpack_sockaddr_in could not process the socket information. The error text gives more information about the error.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-133 | Could not obtain information for node node number. SDRGetObjects return code: error code. |
Explanation: Check the SDR return code to determine the reason for the failure. The Node object associated with the client Adapter object could not be obtained.
User Response: Follow normal problem reporting procedures.
| 2545-134 | The uuencode command was unsuccessful. |
Explanation: The uuencode command could not process the specified key file. Refer to the error message explaining the failure.
User Response: Take corrective action based on error information reported by the uuencode command. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-135 | The s1term command was unsuccessful. |
Explanation: The s1term command did not complete normally. Refer to other error messages explaining the failure.
User Response: Take corrective action based on error information reported by the s1term command. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-136 | Could not remove temporary file file path. |
Explanation: The command could not remove the uuencoded key file. If there are no other error messages in the kfserver.log.PID file, then the keyfile was successfully transmitted to the node.
User Response: Check for system or file system problems. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-137 | inet_ntoa was unsuccessful. error text. |
Explanation: The perl function inet_ntoa could not process the client IP address information. The error text gives more information about the error.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-138 | Client address IP address was not found. SDRGetObjects return code: error code. |
Explanation: Check the SDR return code to determine the reason for the failure. The get_keyfiles command may have been invoked from a host that is not a node on this SP system.
User Response: If the specified node does not exist, re-issue the get_keyfiles command, specifying a correct node number. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-140 | Could not open file /var/adm/SPlogs/get_keyfiles/get_keyfiles.log. error text. |
Explanation: Refer to the error text for an explanation of the cause of the error. A possible cause is a full file system.
User Response: Take corrective action based on the error text, and re-issue the command after you have corrected the problem. If you cannot correct it, follow standard problem reporting procedures.
| 2545-141 | Incorrect number of operands. |
Explanation: This command requires two operands: the name of the file to obtain from the kfserver, and the hostname on which the kfserver runs.
User Response: Re-issue the command, specifying the required operands.
| 2545-142 | The keyfile name operand is not valid. |
Explanation: The name of the keyfile to be obtained from the kfserver has an format that is not valid.
User Response: Re-issue the command, specifying the name of a keyfile.
| 2545-143 | The server name operand is not valid. |
Explanation: The hostname of the kfserver has an format that is not valid.
User Response: Re-issue the command, specifying a valid hostname.
| 2545-144 | Could not remove the cons (getty) entry from inittab. |
Explanation: The command could not temporarily remove the /dev/tty0 entry named cons from the inittab. This is necessary to allow the get_keyfiles command to receive the keyfile over that interface.
User Response: Check for system and file system problems. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-145 | Could not stop the cons (getty) process. |
Explanation: The command could terminate the getty process using /dev/tty0. This is necessary to allow the get_keyfiles command to receive the keyfile over that interface.
User Response: Check for system problems. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-146 | Could not obtain node number. |
Explanation: The node_number command did not complete successfully, so this command cannot identify itself to the kfserver.
User Response: Follow normal problem reporting procedures.
| 2545-147 | This command is valid only on SP nodes. |
Explanation: get_keyfiles is designed to retrieve an SP node's keyfiles from the kfserver daemon on the control workstation. It is not valid when issued on the control workstation itself, or on other RS/6000 hosts that are not SP nodes.
User Response: None.
| 2545-149 | The uudecode command was unsuccessful. |
Explanation: The uudecode command could not process the specified key file. Refer to the error message explaining the failure.
User Response: Take corrective action based on error information reported by the uudecode command. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-150 | Could not remove temporary file file path. |
Explanation: The command could not remove the uuencoded key file. If there are no other error messages in the get_keyfiles.log file, then the keyfile was successfully received on the node.
User Response: Check for system or file system problems. If you cannot resolve the problem, follow normal problem reporting procedures.
| 2545-151 | Could not add the cons (getty) entry to inittab. |
Explanation: The command could not replace the inittab entry that it temporarily removed.
User Response: Use the s1term command on the control workstation to login to the
node and manually replace the inittab entry.