vRealize Log Insight primary node UI inaccessible after applying Hotfix1
search cancel

vRealize Log Insight primary node UI inaccessible after applying Hotfix1

book

Article ID: 318393

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

The purpose of the article is to inform the reader of the issue, and resolve the inaccessibility of the vRealize Log Insight UI.

Symptoms:
  • vRealize Log Insight UI becomes inaccessible when the hotfix is applied.
  • If it is a multi-node cluster, the primary node is upgraded while the rest of the nodes are stuck in the "Upgrade in progress" state.
  • While trying to access the vRealize Log Insight through the primary node's FQDN/IP, it shows the error "Page not found".
  • The UI is accessible through the worker node's FQDN/IP.
  • However, the vRealize Lifecycle Manager shows the status of a successful upgrade.
  • The following errors are observed in the /storage/core/loginsight/var/runtime.log files:
[2022-09-27 11:07:59.331+0000] ["BucketManager-thread-1"/<IP> ERROR] [com.vmware.loginsight.daemon.notifications.AlertNotifierService] [Failed to find current leader.]
[2022-09-27 11:08:05.645+0000] ["localhost-startStop-1"/<IP> ERROR] [com.vmware.loginsight.config.VIDMAuthenticationConfig] [Failed to decrypt VMware Identity Manager OAuth Client Secret]


Environment

VMware vRealize Log Insight 8.x

Resolution

This issue is resolved in vRealize Log Insight 8.10.2 (build number 21145187).

Workaround:
To work around the issue:
  1. SSH to the affected Log Insight node as root
  2. Change to the Log Insight config directory
cd /storage/core/loginsight/config
  1. Take a backup of the latest config file
cp loginsight-config.xml#x loginsight-config.xml#x.orig

Note: Replace x in the above command with the highest numerical value of the files in the directory, indicating it is the latest version of the file
  1. Using a text editor, open the latest config file, removing the entire <auth-method value="vidm"> section as highlighted beneath
image.png
  1. Save and close the file.
  2. Restart the Log Insight service
service loginsight restart
  1. The UI should load after a short time
  2. Re-configure the vIDM Integration from Administration->Configuration->Authentication->VMware Identity Manager
Note: The above work around will not persist reboots - so it is advised to upgrade to 8.10 after following the steps in this article, and then follow VMware Aria Operations for Logs primary node UI unavailable after upgrading to 8.10 (90257) for a work around which persists reboots.


Powered by Wolken Software