Troubleshooting

You can troubleshoot some common issues you encounter with HCL Local License Server (LLS).

The following logs are created that you can use to troubleshoot errors while using LLS.

Error log - The system logs installation errors when there's a fingerprint mismatch, TLS certificate issues, and so on. These errors are captured in the installed_directory/logs/hcl_lls.log file.
Features log - The installed_directory/logs/hcl_lls_features.log file covers the details of the leases, current state of a pool, and so on.

The following tips help you troubleshoot some of the issues that you may encounter:

`OpenSSL is not installed or not found in the system's PATH`

Cause: When running the utility program for TLS certificate generation in any of the following scenarios:

Scenario 1 - When OpenSSL is not installed.
Scenario 2 - When you have installed OpenSSL but have not set the PATH variable.
Scenario 3 - When you have installed OpenSSL and have also set the PATH variable. This issue is with OpenSSL issue when it is not able to read the OpenSSL configuration file.

Resolution: You must ensure that OpenSSL is installed, set the OPENSSL_CONF system environment variable to specify the path of the openssl.cfg file, and start the utility program again.

`Fingerprint mismatch`

Cause: When the fingerprint in the license file does not match with the fingerprint generated.

Resolution: You must generate the fingerprint again, download the license file, and use the license file for installation.

`TLS certificate is expired`

Cause: When you use an expired TLS certificate while installing LLS.

Resolution: Generate a new self-signed TLS certificate using the utility program or use a valid third-party certificate.

`TLS certificate and key loading failed: tls: private key does not match public key`

Cause: When you specify a wrong certificate key file while installing LLS or when updating the third-party certificate in which the chain of certificates is not correct.

Resolution: Ensure that the key file you specify belongs to the specified TLS certificate and that the order of certificates is: server certificate, intermediate certificate, and root certificate.

`Not able to stop Windows service`

Cause: On Windows, you cannot start services manually from the Services window.

Resolution: Stop the service by terminating its process and then start the service again from the Services window.

`Could not resolve host or curl: (51) SSL: no alternative certificate subject name matches target host name`

Cause: When the hostname is not included in the hosts file.

Resolution: You must add the hostname to the hosts file. The host file is available:

On Windows at C:\Windows\System32\drivers\etc location.
On Linux at /etc/hosts location.

`TLS certificate and key loading failed: tls: failed to parse private key`

Cause: When you use a certificate key encrypted with the private key at the time of installing or updating LLS.

Limitation: Currently, LLS does not support certificates with encrypted private keys.