AWSDEB - SSL messages

This section lists error and warning messages that might be issued when using SSL.

The message component code is DEB and the old message set code is 105 in the "unison" message catalog.

AWSDEB009E

Data transmission is not possible because the connection is broken. The following gives more details of the error: "error_message".

See message.

error_message describes the error and includes the operating system error message.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Use the ping command to check if the two workstations involved can connect to each other.

If not, resolve the network problem and restart the process that was trying to communicate.

If there is no network problem, and this is the first communication between two workstations, check that their SSL settings are compatible, and correct any discrepancy.

AWSDEB010E

An error occurred in gethostbyname: "error_message" (getting the host IP address using the host name).

While trying to look up the host IP address on the Domain Name Server (DNS), an error was received.

error_message describes the error and includes the operating system error message.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Check the information in the error message. If it indicates that the host name does not exist on the DNS, verify that the value of the host name in the connection parameters is correct. The connection parameters might have been supplied as part of a command, in a text file referenced in the command string , or from the default definitions in the useropts or localopts file. If the host has only been recently connected to the network, or has been reconnected after a host name change, you might have to wait for the DNS server to update its database with the new or changed host name.

If a different type of error is reported, attempt to resolve it.

If the error has been resolved, retry the operation.

AWSDEB011E

The socket descriptor is incorrect. The following gives more details of the error: "error_message".

See message.

error_message describes the error and includes the operating system error message.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Verify the connection definitions in the localopts file. For example the netman port must match the TCP port in the computer's workstation definition.

AWSDEB016E

An internal error has occurred. The data structure area (comarea) cannot be initialized (is null).

See message.

The program stops.

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSDEB017E

The internal data structure area (comarea) cannot be initialized (memory error).

See message.

The program stops.

Check the following:

  1. Verify if the workstation has enough memory available. Information about the memory requirements of HCL Workload Automation is provided in the Release Notes. If not, you might need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to the program. Rerun the program.
  2. If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun the program.
  3. If the problem persists, reboot the workstation, and then rerun the program.
  4. If the problem persists, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
The Release Notes for details of memory requirements.

AWSDEB024E

An internal error has occurred. The program could not access the internal data structure (comarea) while opening the socket or accepting a connection in the socket descriptor sockfd (part of comarea). The following gives more details of the error: "error_message".

See message.

error_message describes the error and includes the operating system error message.

The program stops.

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSDEB025E

An internal error has occurred. The program cannot set the linger socket option. The following gives more details of the error: "error_message".

See message.

error_message describes the error and includes the operating system error message.

The program proceeds.

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSDEB026E

An internal error has occurred. Cannot set the reuseaddr socket option. The following gives more details of the error: "error_message".

See message.

error_message describes the error and includes the operating system error message.

The program proceeds.

Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSDEB027E

Error setting close on exec/uninherit flag: !1

AWSDEB028E

Error opening os handle: !1

AWSDEB045E

An error has occurred during the creation of the local SSL context. The following gives more details of the error: "error_message".

This error occurs when one of the HCL Workload Automation network processes (mailman, writer, netman or scribner) is unable to initialize the local SSL context. The problem could be related to either an invalid SSL setting specified within the localopts file or to an initialization error of the SSL.

error_message could be either the error number or a string explaining specifically the error if available.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

To solve this problem check all the values of the options specified within the localopts file of the node where the error is logged (see the appropriate chapter of the Planning and Installation guide for more details). One of the most common errors is related to the creation of the encrypted file that contains the password. If the source password file contains some spurious characters the resulting encrypted file is not useful and the initialization of the local SSL context fails.

The Planning and Installation guide

AWSDEB046E

An error has occurred during the SSL handshaking. The following gives more details of the error: "error_message".

A problem has occurred during the SSL handshaking between a workstation and its domain manager or between a domain manager and its parent domain manager. The most common reasons for this error are as follows:

  • Could not connect to or accept the incoming communication
  • Could not establish a common cipher between the SSL server and client
  • Could not get the certificate from the connecting node
  • The incoming certificate is not trusted or is expired
  • The incoming node cannot be authenticated

The error_message could be either a standard SSL error number or a string explaining the error (if available).

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Use the information in the error message to determine the error and take the appropriate action.

If the message is not clear, do the following:

  • Check that there are no network problems preventing the connection
  • Check the SSL parameters in the local and global options files
  • Check that the certificates in use by both server and client are compatible, trusted, and not expired.

When you have found and resolved the problem, rerun the process that was running when the error occurred.

AWSDEB047E

The program could not access the localopts local options file.

See message.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Verify that the localopts file is present and that the <TWSuser> has the rights to process it.

AWSDEB048E

An internal error has occurred. HCL Workload Automation network processes (mailman, writer, netman or scribner) are unable to use the previously allocated SSL context.

See message.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

An internal error has occurred. Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.

AWSDEB049E

The counterparty workstation did not present an SSL peer certificate, or no connection was established.

See message.

The probable cause is that the TCP/IP connection has broken or the localopts SSL settings of the node that is trying to connect are not correct.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Check that the network connection is good, by using the ping command.

If the network connection is good, check the localopts setting of the node that is trying to connect (see the appropriate chapter of the Planning and Installation guide for more details).

The Planning and Installation guide.

AWSDEB051E

The program cannot authenticate the SSL peer certificate: the requested level is not matched.

See message.

The behavior of HCL Workload Automation during an SSL handshake is based on the value of the SSL auth mode localopts option as follows:

  • caonly: The program checks the validity of the certificate and verifies that the peer certificate has been issued by a trusted Certificate Authority.
  • string: The program checks the validity of the certificate and verifies that the peer certificate has been issued by a trusted Certificate Authority. It also verifies that the common name of the certificate subject matches the string specified in the SSL auth string option.
  • cpu: The program checks the validity of the certificate and verifies that the peer certificate has been issued by a trusted Certificate Authority. It also verifies that the common name of the certificate subject matches the name of the workstation that requested the service.

This message is generated by a library function that is called by more than one program. The calling program decides how to process the error that this message has revealed. Look in the log for other messages following this one to see how HCL Workload Automation reacts.

Check the Authentication mode you have selected for the Workstation and verify that the peer certificate of the Workstation that is trying to connect respects the SSL auth mode you selected.

A useful command to view the contents of a certificate is the following:

openssl x509 -noout -text -in certificate.crt

AWSDEB052E

An error occurred in getaddrinfo: "error_message" (getting the host IP address using the host name).

An error was issued while the program was searching for the host IP address on the Domain Name Server (DNS).

error_message describes the error and includes the operating system error message.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for following messages to find how HCL Workload Automation responds.

Check the information in the error message. If it states that the host name does not exist on the DNS, verify that the value of the host name in the connection parameters is correct. The connection parameters might have been supplied as part of a command, in a text file referenced in the command string, or from the default definitions in the useropts or localopts file. If the host has just been connected to the network, or if it has been reconnected after a host name change, you might have to wait for the DNS server to update its database with the new or changed host name.

AWSDEB053E

FIPS cannot be enabled. The connection is not possible.

HCL Workload Automation cannot enable FIPS mode as requested in the configuration.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

Checks GSkit module

AWSDEB054E

An error occurred during an SSL connection using the OpenSSL Toolkit.

An error was issued while the program was connecting to its peer agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

Check your OpenSSL certificate in the localopts file.

AWSDEB055E

An error occurred during an SSL connection using the GSKit libraries.

An error was issued while the program was connecting to its peer agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

Check your GSKIT certificate in the localopts file.

AWSDEB056E

An error occurred a SSL connection using the OpenSSL Toolkit. The connection can not be accepted.

An error was issued while the program was connecting to its peer agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

.Check your OpenSSL certificate in the localopts file

AWSDEB057E

An error occurred a SSL connection using the GSKit libraries.The connection can not be accepted.

An error was issued while the program was connecting to its peer agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

Check your GSKIT certificate in the localopts file.

AWSDEB058E

An error occurred during the initialization of the ICC module in FIPS mode. Encryption is not possible.

An error was issued while the program was trying to decrypt or crypt a password.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Search the log for the following messages to see how HCL Workload Automation responds.

.Check your GSKIT/ICC libraries

AWSDEB059E

An error occurred during the initialization of the GSKit module in FIPS mode. The configuration is not correct. Check the configuration in the localopts file.

An error was issued while the program was trying to connect an agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Check if the label, key store, or other parameter in the localopts file is not correct.

.Check your GSKIT/ICC configuration

AWSDEB060E

An error occurred during the initialization of the OpenSSL Toolkit. The configuration is not correct. Check the configuration in the localopts file.

An error was issued while the program was trying to connect an agent.

This message is generated by a library function that is called by more than one program. The calling program decides how to handle the error displayed by this message. Check if the label, key store, or other parameter in the localopts file is not correct.

.Check your OpenSSL configuration