|
When using LDAP with SSL to access the Netscape Directory Server, the Netscape
Directory Server will be unable to make a secure connection if the certificate is signed
using CAServlet. The Netscape Directory Server will give the following errors:
- ldapu_get_cert_subject_dn(01136924) -301 Could not extract the issuer
DN from the certificate.
- ldapu_get_cert_issuer_dn(01136924) -301 Could not extract the issuer
DN from the certificate.
To view the Administration Server logs, go to Getting Started > View Admin Logs. You can view the
Access log and the Error log.
- Message: mod_ibm_ssl: Failure obtaining Cert data for label <certificate label>
- Reason: Didn’t supply a valid certificate/key label
- Solution: Rename certificate label to default or valid certificate/key
- Notes: None
- Message: mod_ibm_ssl: keyfile does not exist: <keyfile>
- Reason: Specified a keyfile for keyfile directive that did not exist
- Solution: Create a keyfile
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake failed, The GSK library unloaded
- Reason: GSK library unloaded
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake failed, internal error
- Reason: The communication between client and the server failed
- Solution: Retry connection from the client
- Notes: None
- Message: mod_ibm_ssl: Failure obtaining Cert data for label <certificate label>
- Reason: Didn’t supply a valid certificate/key label
- Solution: Rename certificate label to default or valid certificate/key
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, GSK handle is in an invalid state for operation
- Reason: Incorrect state for GSK handle
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, key-file label not found
- Reason: Could not find the certificate/keyfile label
- Solution: Specify a certificate/keyfile label
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Certificate is not available
- Reason: Could not find the certificate
- Solution: Specify a certificate
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Unsupported certificate type.
- Reason: Does not support certificate type
- Solution: Use certificate type that is supported
- Notes: None
- Message: mod_ibm_ssl: Failure attempting to load GSK library.
- Reason: The GSK toolkit is not installed, permissions problem, or the file does not exist.
- Solution: Install the GSK toolkit, check permissions on the library.
- Notes: None.
- Message: mod_ibm_ssl: GSK function address undefined.
- Reason: Incorrect version of the GSK installed.
- Solution: Install the correct version of the GSK.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid SSLV2 Cipher Spec.
- Reason: The SSL Version 2 cipher specs passed into the handshake were invalid.
- Solution: Change the specified Version 2 cipher specs.
- Message: mod_ibm_ssl: SSL handshake Failed, Invalid SSLV3 Cipher Spec.
- Reason: The SSL Version 3 cipher specs passed into the Handshake were invalid.
- Solution: Change the specified Version 3 cipher specs.
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid security type.
- Reason: The SSL security type field passed into the handshake is not valid.
- Solution: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid security type combination.
- Reason: The SSL security type field that is passed into the handshake is not valid.
- Solution: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, No read function specified.
- Reason: The read funtion was not passed into the handshake properly.
- Solution: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, No write function specified.
- Reason: The write funtion was not passed into the handshake properly.
- Solution: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, No ciphers specified.
- Reason: The client did not specify any cipher specifications during the handshake.
- Solution: Client problem.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, No certificate.
- Reason: The client did not specify a certificate.
- Solution: Client problem
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid certificate.
- Reason: The client did not specify a valid certificate.
- Solution: Client problem.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Unsupported certificate type.
- Reason: The client did not specify a certificate that is supported by the GSK toolkit.
- Solution: The client needs to specify a different certificate.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, I/O error.
- Reason: The communication between the client and the server failed.
- Solution: Retry the connection from the client.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid MAC.
- Reason: The communication between the client and the server failed.
- Solution: Retry the connection from the client.
- Notes: None.
- Message: mod_ibm_ssl: SSL Handshake Failed, Unsupported.
- Reason: The communication between the client and the server failed.
- Solution: Retry the connection from the client.
- Notes: None.
- Message: Missing ldap.client.rte.2.1.1.0 # Base Level Fileset
- Reason: LDAP client toolkit not installed.
- Solution: Install the LDAP client toolkit.
- Notes: None.
- Message: mod_ibm_ssl: Failure obtaining Cert data for label <certificate label>
- Reason: Did not supply a valid certificate/key label
- Solution: Rename certificate label to default or valid certificate/key
- Notes: None
- Message: mod_ibm_ssl: keyfile does not exist: <keyfile>
- Reason: Specified a keyfile for keyfile directive that did not exist
- Solution: Create a keyfile
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake failed, The GSK library unloaded
-
- Reason: GSK library unloaded
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake failed, GSK internal error
- Reason: The communication between client and the server failed
- Solution: Retry connection from the client
- Notes: None
- Message: mod_ibm_ssl: Failure obtaining Cert data for label <certificate label>
- Reason: Didn't supply a valid certificate/key label
- Solution: Rename certificate label to default or valid certificate/key
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, GSK handle is in an invalid state for operation
- Reason: Incorrect state for GSK handle
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, keyfile label not found
- Reason: Could not find the certificate/keyfile label
- Solution: Specify a certificate/keyfile label
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Certificate is not available
- Reason: Could not find the certificate
- Solution: Specify a certificate
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Certificate is not available
- Reason: Could not find the certificate
- Solution: Specify a certificate
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Certificate validation error.
- Reason: Certificate was not validated
- Solution: Create another ceritifcate or retry connection
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Error processing cryptography
- Reason: Invalid crytography
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Error validating ASN fields in certificate.
- Reason: Invalid ASN fields in certificate
- Solution: Create valid ASN fields in certificate
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Error connecting to LDAP server.
- Reason: The communication between LDAP server and web server failed
- Solution: retry connection between LDAP server and web server
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal unknown error.
- Reason: Unknown
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Error connecting to LDAP server.
- Reason: The communication between LDAP server and web server failed
- Solution: Retry connection between LDAP server and web server
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Open failed due to cipher error.
- Reason: Invalid Cipher
- Solution: Make sure specified correct cipher
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, I/O error reading keyfile.
- Reason: Could not read keyfile
- Solution: Create valid keyfile
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Keyfile has an invalid internal format. Recreate keyfile.
- Reason: Keyfile has an invalid format
- Solution: Recreate keyfile
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Keyfile has two entries with the same key.
Use iKeyman to remove the duplicate key.
- Reason: Placed two identical keys in keyfile
- Solution: Use iKeyman to remove duplicate key
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Keyfile has two entries with the same label.
- Use IKEYMAN to remove the duplicate label.
- Reason: Placed two identical key labels in keyfile
- Solution: Use iKeyman to remove duplicate label
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The default key in the keyfile has an expired certificate.
- Use IKEYMAN to remove certificates that are expired.
- Reason: An expired certificate is in the keyfile
- Solution: Use IKEYMAN to remove certificates that are expired
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The keyfile password is used as an integrity check.
- Either the keyfile has become corrupted or the password is incorrect.
- Reason: Corrupted or incorrect password for keyfile
- Solution: Generate new password for keyfile
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, There was an error loading one of the GSKdynamic
link libraries. Be sure GSK was installed correctly.
- Reason: Could not load one of the GSKdynamic link libraries
- Solution: Make sure the Gskit got installed correctly
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid date.
- Reason: The system date was set to an invalid date
- Solution: Change the system date toa valid date
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, I/O error during handshake.
- Reason: An I/O error occurred on a data read or write
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid key length for export.
- Reason: In a restricted cryptography environment, the key size is too long to be supported.
- Solution: Make key size smaller
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - read failed.
- Reason: The read failed
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - write failed.
- Reason: The write failed.
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Socket has been closed.
- Reason: The client closed the socket before the protocol completed.
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - SSL Handle creation failure.
- Reason: The handle could not be created
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - GSK initialization has failed.
- Reason: Initialization failed
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, LDAP server not available.
- Reason: Unable to access the specified LDAP directory when validating a certificate
- Solution: Make sure LDAP server is available
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The specified key did not contain a private key.
- Reason: Key did not contain a private key
- Solution: Create key with private key
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The PKCS#11 driver failed to find the token label
specified by the caller.
- Reason: Specified invalid PKCS#11 token label
- Solution: Specify a valid PKCS#11 token label
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, A failed attempt was made to load the
specified PKCS#11 shared library.
- Reason: Specified invalid PKCS#11 shared library/module
- Solution: Specify a valid PKCS#11 shared library/module
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, A PKCS#11 token is not present for the slot.
- Reason: PKCS#11 token not present
- Solution: Specify valid slot for PKCS#11 token
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The password/pin to access the PKCS#11 token is
either not present or invalid.
- Reason: Specified user password/pin for PKCS#11 token is not present or invalid
- Solution: Specify a valid user password/pin for PKCS#11 token
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The SSL header received was not a
properly SSLV2 formated header.
- Reason: Incorrectly formatted SSLV2 header.
- Solution: Retry connection between client and server with valid SSLV2 cipher
- Notes: None
- Message: mod_ibm_ssl: SSL Internal error - SSLV3 is required for reset_cipher,
and the connection uses SSLV2.
- Reason: SSLV3 is required for reset_cipher, and the connection uses SSLV2
- Solution: None
- Message: mod_ibm_ssl: SSL Internal error - An invalid ID was specified for
the gsk_secure_soc_misc function call.
- Reason: Specified an invalid ID for the gsk_secure_soc_misc function call
- Solution: None
- Message: mod_ibm_ssl: SSL Internal error - An invalid ID was specified for the
gsk_secure_soc_misc function call.
- Reason: Specified an invalid ID for the gsk_secure_soc_misc function call
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - The attribute has
a negative length in: <argument>.
- Reason: Attribute has a negative length
- Solution: Make sure attribute does not have a negative length
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The enumeration value is invalid
for the specified enumeration type in: <argument>.
- Reason: Invalid enumeration value for attribute
- Solution: Specify valid enumeration value for argument
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The attribute has an
invalid numeric value: <argument>.
- Reason: Invalid numeric value for attribute.
- Solution: Specify valid numeric value
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid or improperly formatted certificate
- Reason: Client certificate is invalid
- Solution: Client problem
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The function call, <argument>, has an invalid ID
- Reason: Function call has invalid ID
- Solution: None
- Message: mod_ibm_ssl: Initialization error, GSK internal error
- Reason: The communication between client and the server failed
- Solution: Retry connection from the client
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The GSK library unloaded
- Reason: GSK library unloaded
- Solution: None
- Message: mod_ibm_ssl: Initialization error, keyfile label not found
- Reason: Could not find the certificate/keyfile label
- Solution: Specify a certificate/keyfile label
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Certificate is not available
- Reason: Could not find the certificate
- Solution: Specify a certificate
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Certificate validation error.
- Reason: Certificate was not validated
- Solution: Create another ceritifcate or retry connection
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Error processing cryptography
- Reason: Invalid crytography
- Solution: none
- Message: mod_ibm_ssl: Initialization error, Error validating ASN fields in certificate.
- Reason: Invalid ASN fields in certificate
- Solution: Create valid ASN fields in certificate
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Error connecting to LDAP server.
- Reason: The communication between LDAP server and web server failed
- Solution: retry connection between LDAP server and web server
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Internal unknown error.
- Reason: Unknown
- Solution: none
- Message: mod_ibm_ssl: Initialization error, Open failed due to cipher error.
- Reason: Invalid Cipher
- Solution: Make sure specified correct cipher
- Notes: None
- Message: mod_ibm_ssl: Initialization error, I/O error reading keyfile.
- Reason: Could not read keyfile
- Solution: Create valid keyfile
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Keyfile has an invalid internal format. Recreate keyfile.
- Reason: Keyfile has invalid format
- Solution: Recreate keyfile
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Keyfile has two entries with the same key.
Use IKEYMAN to remove the duplicate key.
- Reason: Placed two identical keys in keyfile
- Solution: Use iKeyman to remove duplicate key
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Keyfile has two entries with the same label.
Use IKEYMAN to remove the duplicate label.
- Reason: Placed two identical key labels in keyfile
- Solution: Use iKeyman to remove duplicate label
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The keyfile password is used as an integrity check.
Either the keyfile has become corrupted or the password is incorrect.
- Reason: Corrupted or incorrect password for keyfile
- Solution: Generate new password for keyfile
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The default key in the keyfile has an expired
certificate. Use iKeyman to remove certificates that are expired.
- Reason: An expired certificate is in the keyfile
- Solution: Use iKeyman to remove certificates that are expired
- Notes: None
- Message: mod_ibm_ssl: Initialization error, There was an error loading one of the GSKdynamic
link libraries. Be sure GSK was installed correctly.
- Reason: Could not load one of the GSKdynamic link libraries
- Solution: Make sure the Gskit got installed correctly
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Unsupported certificate type.
- Reason: The client did not specify a certificate that is supported by the GSK toolkit.
- Solution: The client needs to specify a different certificate
- Notes: None
- Message: mod_ibm_ssl: Initialization error, I/O error during handshake.
- Reason: An I/O error occurred on a data read or write
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid key length for export.
- Reason: In a restricted cryptography environment, the key size is too long to be supported.
- Solution: Make key size smaller
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Internal error - read failed.
- Reason: The read failed
- Solution: none
- Message: mod_ibm_ssl: Initialization error, Internal error - write failed.
- Reason: The write failed.
- Solution: none
- Message: mod_ibm_ssl: Initialization error, Socket has been closed.
- Reason: The client closed the socket before the protocol completed.
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid SSLV2 Cipher Spec.
- Reason: The SSL version 2 cipher specs passed during initialization were invalid.
- Solution: Change the version 2 cipher specs that are specified
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid SSLV3 Cipher Spec.
- Reason: The SSL version 3 cipher specs passed during initialization were invalid.
- Solution: Change the version 3 cipher specs that are specified
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid security type.
- Reason: The SSL security type field that is passed during initialization was not valid
- Solution: Change the version 3 cipher specs that are specified
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid security type combination.
- Reason: The SSL security type field that is passed during initialization was not valid.
- Solution: Change the version 3 cipher specs that are specified
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Internal error - SSL Handle creation failure.
- Reason: The handle could not be created
- Solution: None
- Message: mod_ibm_ssl: Initialization error, Internal error - GSK initialization has failed.
- Reason: Initialization failed
- Solution: None
- Message: mod_ibm_ssl: Initialization error, LDAP server not available.
- Reason: Unable to access the specified LDAP directory when validating a certificate
- Solution: Make sure LDAP server is available
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The specified key did not contain a private key.
- Reason: Key did not contain a private key
- Solution: Create key with private key
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The PKCS#11 driver failed to find the token label
specified by the caller.
- Reason: Specified invalid PKCS#11 token label
- Solution: Specify a valid PKCS#11 token label
- Notes: None
- Message: mod_ibm_ssl: Initialization error, A failed attempt was made to load the specified
PKCS#11 shared library.
- Reason: Specified invalid PKCS#11 shared library/module
- Solution: Specify a valid PKCS#11 shared library/module
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, A PKCS#11 token is not present for the slot.
- Reason: PKCS#11 token not present
- Solution: Specify valid slot for PKCS#11 token
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The password/pin to access the PKCS#11 token
is either not present or invalid.
- Reason: Specified user password/pin for PKCS#11 token is not present or invalid
- Solution: Specify a valid user password/pin for PKCS#11 token
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The SSL header received was not a properly SSLV2
formated header.
- Reason: Incorrectly formatted SSLV2 header.
- Solution: Retry connection between client and server with valid SSLV2 cipher
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The function call, <argument>, has an invalid ID
- Reason: Function call has invalid ID
- Solution: None
- Message: mod_ibm_ssl: Initialization error, Internal error - The attribute has a negative
length in: <argument>.
- Reason: Attribute has a negative length
- Solution: Make sure attribute does not have a negative length
- Notes: None
- Message: Initialization error, The enumeration value is invalid for the specified
enumeration type in: <argument>.
- Reason: Invalid enumeration value for attribute
- Solution: Specify valid enumeration value for argument
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The attribute has an invalid numeric value: <argument>.
- Reason: Invalid numeric value for attribute.
- Solution: Specify valid numeric value
- Notes: None
- Message: mod_ibm_ssl: GSK could not initialize, no keyfile specified
- Reason: Did not supply a keyfile for keyfile directive
- Solution: Specify keyfile for keyfile directive
- Notes: None
- Message: mod_ibm_ssl: If CRL is turned on, you must specify an LDAP hostname for
the SSLCRLHostname directive
- Reason: Did not specify an LDAP TCP/IP name or address for SSLCRLHostname directive when CRL is enabled
- Solution: Specify an LDAP TCP/IP name or address for SSLCRLHostname directive
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - Bad handle
- Reason: Bad handle
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal memory allocation failure
- Reason: Could not allocate internal memory
- Solution: None
- Message: mod_ibm_ssl: GSK could not initialize, no keyfile specified
- Reason: Didn't supply a keyfile for keyfile directive,/li>
- Solution: Specify keyfile for keyfile directive
- Notes: None
- Message: mod_ibm_ssl: If CRL is turned on, you must specify an LDAP hostname for the
SSLCRLHostname directive
- Reason: Didn't specify an LDAP TCP/IP name or address for SSLCRLHostname directive when CRL is enabled
- Solution: Specify an LDAP TCP/IP name or address for SSLCRLHostname directive
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal error - Bad handle
- Reason: Bad handle
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Internal memory allocation failure
- Reason: Could not allocate internal memory
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Specified label could not be found in key file.
- Reason: Specified key label is not present in keyfile
- Solution: Specify a valid key label
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid password for keyfile.
- Reason: The keyfile may be corrupt or the password for keyfile may be incorrect
- Solution: Specify a valid keyfile and password for keyfile
- Notes: None
- Message: mod_ibm_ssl: GSK could not initialize, Neither the password nor the stash-file name
was specified. Could not open keyfile.
- Solution: Specify a valid password and stash-file for keyfile
- Notes: None
- Message: mod_ibm_ssl: GSK could not initialize, Could not open keyfile.
- Reason: Either the path to the keyfile was specified incorrectly or the file permissions did not
allow the file to be opened.
- Solution: Supply valid path to keyfile and make sure permissions are valid
- Notes: None
- Message: mod_ibm_ssl: Internal error - GSK could not initialize, Unable to generate
a temporary key pair.
- Reason: GSK could not generate a temporary key pair
- Solution: None
- Message: mod_ibm_ssl: GSK could not initialize, Invalid password for keyfile.
- Reason: The keyfile may be corrupt or the password for keyfile may be incorrect
- Solution: Specify a valid keyfile and password for keyfile
- Notes: None
- Message: mod_ibm_ssl: GSK could not initialize, Invalid label.
- Reason: Specified key label is not present in keyfile
- Solution: Specify a valid key label
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Internal error - Bad handle
- Reason: Bad handle
- Solution: None
- Message: mod_ibm_ssl: GSK could not initialize, Internal memory allocation failure
- Reason: Could not allocate internal memory
- Solution: None
- Message: mod_ibm_ssl: Initialization error, Invalid date.
- Reason: The system date was set to an invalid date
- Solution: Change the system date to a valid date
- Notes: None
- Message: mod_ibm_ssl: Initialization error, No ciphers specified.
- Reason: The client did not supply any cipher specifications during the handshake
- Solution: Client problem
- Notes: None
- Message: mod_ibm_ssl: Initialization error, No certificate.
- Reason: The client did not supply a certificate
- Solution: Client problem
- Notes: None
- Message: mod_ibm_ssl: Initialization error, The received certificate was formatted incorrectly.
- Reason: Client certificate is invalid
- Solution: Client problem
- Notes: None
The following error messages may appear, but can be ignored:
- mod_ibm_ssl: SSL Handshake Failed, Invalid or improperly formatted certificate.
- mod_ibm_ssl: SSL Handshake Failed, Bad message sent.
- Mod_ibm_ssl: SSL Handshake Failed, I/O error during handshake.
If you encounter an error starting a target server, the error message, line number in the configuration file and the
actual line text that caused the error display. To view the line text error in context:
- Select the text.
- Copy the text.
- Go to View Config > Edit Config and press Ctrl + F for "Find"
- Paste the text
- Click OK.
- Message: mod_ibm_ssl: Setting the LIBPATH for GSK failed.
- Reason: Memory allocation failure.
- Solution: The process is low on memory and should be restarted.
- Notes: None.
- Message: mod_ibm_ssl: mod_ibm_ssl: Setting the LIBPATH for GSK failed, could not append /usr/lib.
- Reason: Memory allocation failure.
- Solution: The process is low on memory and should be restarted.
- Notes: None.
- Message: mod_ibm_ssl: SSL Connection attempted when SSL did not initialize.
- Reason: Should be a previous error message telling why the library did not initialize properly.
- Solution: Fix the library loading problem.
- Notes: None.
- Message: mod_ibm_ssl: Client did not supply a certificate, closing the connection.
- Reason: The client who connected failed to send a client certificate and the server is configured to require a certificate.
- Solution: Nothing on the server side.
- Notes: None.
- Message: mod_ibm_ssl: Setting the LIBPATH for GSK failed, could not append /usr/opt/gskkm/lib.
- Reason: Memory allocation failed
- Solution: The process is low on memory and should be restarted.
- Notes: None
- Message: mod_ibm_ssl: Setting the LD_LIBRARY_PATH for GSK failed.
- Reason: Could not set library path, memory allocation failed
- Solution: The process is low on memory and should be restarted.
- Notes: None
- Message: mod_ibm_ssl: Setting the LD_LIBRARY_PATH for GSK failed, could not append /usr/lib.
- Reason: Memory allocation failed
- Solution: The process is low on memory and should be restarted.
- Notes: None
- Message: mod_ibm_ssl: Setting the LD_LIBRARY for GSK failed.
- Reason: Could not set library path, memory allocation failed
- Solution: The process is low on memory and should be restarted.
- Notes: None
- Message: mod_ibm_ssl: Setting the LD_LIBRARY for GSK failed, could not append /usr/lib.
- Reason: Memory allocation failed
- Solution: The process is low on memory and should be restarted.
- Notes: None
- Message: mod_ibm_ssl: Client did not supply a certificate.
- Reason: Client certificate not supply
- Solution: Create a client certificate
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, An incorrectly formatted SSL message was received.
- Reason: Client sent incorrectly formatted SSL message
- Solution: Client problem
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Could not verify MAC.
- Reason: The message authentication code (MAC) was not successfully verified
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Unsupported SSL protocol or unsupported certificate type
- Reason: Specifed SSL protocol or certificate type was unsupported
- Solution: Specify a supported SSL protocol or certificate type
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid certificate signature.
- Reason: The received certificate contained an incorrect signature
- Solution: Send a certificate with a correct signature
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid certificate sent by client.
- Reason: Incorrectly formatted certificate sent by client
- Solution: Send correct formatted certificate to server from client
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Invalid peer.
- Reason: Invalid SSL protocol received from the client
- Solution: Send valid SSL protocol to server from client
- Notes: None
- Message: mod_ibm_ssl: SSL Handshake Failed, Permission denied.
- Reason: Internal error
- Solution: None
- Message: mod_ibm_ssl: SSL Handshake Failed, The self-signed certificate is not valid.
- Reason: Specified invalid self-signed certificate
- Solution: Create valid self-signed certificate
- Notes: None
- Message: mod_ibm_ssl: Initialization error, GSK handle is in an invalid state for operatio
- Reason: Incorrect state for GSK handle
- Solution: None
- Message: mod_ibm_ssl: Initialization error, An incorrectly formatted SSL message was received.
- Reason: Client sent incorrectly formatted SSL message
- Solution: Client problem
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Could not verify MAC.
- Reason: The message authentication code (MAC) was not successfully verified
- Solution: Retry connection between client and server
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Unsupported SSL protocol or unsupported certificate type
- Reason: Specifed SSL protocol or certificate type was unsupported
- Solution: Specify a supported SSL protocol or certificate type
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid certificate signature.
- Reason: The received certificate contained an incorrect signature
- Solution: Send a certificate with a correct signature
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid certificate sent by client.
- Reason: Incorrectly formatted certificate sent by client
- Solution: Send correct formatted certificate to server from client
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Invalid peer.
- Reason: Invalid SSL protocol received from the client
- Solution: Send valid SSL protocol to server from client
- Notes: None
- Message: mod_ibm_ssl: Initialization error, Permission denied.
- Reason: Internal error
- Solution: None
- Message: mod_ibm_ssl: Initialization error, The self-signed certificate is not valid.
- Reason: Specified invalid self-signed certificate
- Solution: Create valid self-signed certificate
- Notes: None
|