Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How to replace a corrupted truststore in vRealize Log Insight 8.x (76168)

Last Updated: 10/10/2023Categories: How toTotal Views: 15264Language:
English

10 like this article

Subscribe to get an email
newsletter with new updates

10 people found this helpful Please provide article feedback:

Symptoms

Unable to successfully test pre-existing vRealize Log Insight integrations (such as vIDM, vSphere, vRealize Operations, and Active Directory).

Intermittent issues logging in with AD/SSO accounts

"Error loading certificates" is thrown accessing the Administration -> Certificates page

Exporting logs from Log Insight fails with message '<HTML><head><title>Servlet Error | vRealize Log Insight </title><style> error-page-container

Exporting logs from Log Insight to an NFS share fails with message "Failed to add new export task"

Navigating between UI tab yields the error "Failed to download fields. The list of fields is incomplete."

This issue can occur after upgrading to vRealize Log Insight 8.x, but is not exclusive to that task, and can occur outside of an upgrade.

The /storage/var/loginsight/runtime.log file contains entries similar to:

[2023-10-03 07:15:15.307+0000] ["SslCertificateManagerScheduler-thread-1"/IP ERROR] [com.vmware.loginsight.database.dao.CACertificateDO] [Unable to get alias of certificate. /usr/java/jre-vmware/lib/security/cacerts (No such file or directory)]

[2023-10-03 07:15:15.308+0000] ["SslCertificateManagerScheduler-thread-1"/IP ERROR] [com.vmware.loginsight.database.dao.CACertificateDO] [Unable to get custom CA certificates. /usr/java/jre-vmware/lib/security/cacerts (No such file or directory)]

[2019-11-01 16:46:40.212+0000] ["pool-10-thread-6"/172.27.16.112 ERROR] [com.vmware.loginsight.commons.security.UrlConnectionManager] [Failed to create socket factory]

java.security.KeyStoreException: problem accessing trust store

The /storage/var/loginsight/ui_runtime.log file contains entries similar to:

[2019-11-01 16:48:23.861+0000] ["https-jsse-nio2-443-exec-8"/172.27.16.112 ERROR] [com.vmware.loginsight.web.actions.APIProxyActionBean] [Error creating SSL socket factory.]
java.security.KeyStoreException: problem accessing trust store

The /storage/var/loginsight/plugins/vsphere/li-vsphere.log file contains entries similar to:

[2019-11-01 16:52:40.214+0000] ["pool-10-thread-2"/172.27.16.112 INFO] [com.vmware.loginsight.vsphere.events.VimEventMonitor] [[XXX] Connecting to vCenter at https://vCenterIPorFQDN/sdk]

[2019-11-01 16:52:40.214+0000] ["pool-10-thread-2"/172.27.16.112 INFO] [com.vmware.loginsight.vsphere.events.VimEventMonitor] [verifySslCertificate is set to true, check for https certificates to be trusted.]

[2019-11-01 16:52:40.215+0000] ["pool-10-thread-2"/172.27.16.112 ERROR] [com.vmware.loginsight.vsphere.events.VimEventMonitor] [[XXX] Failed to Monitor VimEvents]
java.security.KeyStoreException: problem accessing trust store

Listing the contents of the truststore fails with an error

To list the contents of the truststore:

Log in as root to the vRealize Log Insight node in question via SSH

Note: If you do not know your root password, refer to How to reset the root password in vRealize Log Insight (53649)

Run the following command /usr/java/jre-vmware/bin/keytool -list -keystore /usr/java/jre-vmware/lib/security/cacerts -storepass changeit

Note: The above command should return the certificates that exist in the truststore when run on a healthy node.  If an error is received, please proceed to replace the truststore with the procedure outlined in this article

Purpose

This article details how to replace a corrupted truststore in vRealize Log Insight 8.x

Resolution

The preferred method to replace a corrupt truststore is by using a copy from a healthy vRealize Log Insight node from the same cluster that does NOT return an error when listing the contents via the above command.  If this is not available, the secondary method is  to use the default truststore attached to this article (cacerts-nofips.tar.gz or cacerts-fips.tar.gz depending on whether FIPS is enabled in the cluster).

Non-FIPS enabled clusters

Perform one of the two operations:

Using a utility like WinSCP or FileZilla, copy a truststore from a working node in the same cluster, using it to replace the existing one in the following directory:

/usr/java/jre-vmware/lib/security/cacerts

Using a utility like WinSCP or FileZilla, copy the cacerts-nofips.tar.gz truststore attached to this article to the node's /tmp directory, extract it, and replace the existing one:

SSH to the node as root

Extract the file

tar -xvzf /tmp/cacerts-no-fips.tar.gz

Replace the existing cacerts file with the new one and update ownership

mv /tmp/cacerts /usr/java/jre-vmware/lib/security/cacerts; chown root:root /usr/java/jre-vmware/lib/security/cacerts

Repeat steps 1-3 on all nodes which in the cluster that were determined to have corrupt truststores

FIPS enabled clusters

Perform one of the two operations:

Use a truststore from a working node in the same cluster to replace the existing one in the following directory:

/usr/java/jre-vmware/lib/security/cacerts

Using a utility like WinSCP or FileZilla, copy the cacerts-fips.tar.gz truststore attached to this article to the node's /tmp directory, extract it, and replace the existing one:

SSH to the node as root

Extract the file

tar -xvzf /tmp/cacerts-fips.tar.gz

Replace the existing cacerts file with the new one and update ownership

mv /tmp/cacerts /usr/java/jre-vmware/lib/security/cacerts; chown root:root /usr/java/jre-vmware/lib/security/cacerts

Repeat steps 1-3 on all nodes which in the cluster that were determined to have corrupt truststores

Related Information

If you are unsure whether or not your cluster is FIPS enabled, and do not have access to the UI to verify:

Log in as root to any vRealize Log Insight node in your cluster via SSH

Run the following command to determine the status of FIPS

/usr/lib/loginsight/application/sbin/fips.sh --all --status

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

cacerts-no-fips.tar

cacerts-fips.tar

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vRealize Automation 8.0 から VMware Identity Manager ログイン ページにリダイレクトすると「Bad Gateway」が返される (76379)

KB
•
仮想マシンをパワーオンすると「エラー - モジュール「NumVCPUs」のパワーオンに失敗しました (Failed - Module 'NumVCPUs' power on failed)」というエラーが表示される (74899)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
取消注册 Skyline Collector (74677)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vRealize Log Insight

VMware Aria Operations for Logs

Related Versions:

VMware vRealize Log Insight 8.x

VMware Aria Operations for Logs 8.12.x

Take Our Survey

Support Assistant