vIDM Error: "An Unexpected Error Has Occurred. Please Try Again Later" while accessing the appliance health
search cancel

vIDM Error: "An Unexpected Error Has Occurred. Please Try Again Later" while accessing the appliance health

book

Article ID: 395725

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

vIDM was reporting errors when accessing the appliance health page. All nodes displayed failures in ACS health and Application Manager services. vIDM nodes was unable to communicate with the master node, impacting overall cluster health.

Environment

VMware Identity Manager 3.3.x

Cause

vIDM nodes was unable to communicate with the master node and upon verifing it was found that /etc/hosts file on one of the node was missing critical entries for the master and delegate IP addresses. As a result, the node could not resolve or communicate with the master node, which prevented OpenSearch and Horizon Workspace services from starting correctly.

Resolution

The /etc/hosts file on the master node was updated to include the missing master and delegate IP information:
 
# Begin /etc/hosts (network card version)
# End /etc/hosts (network card version)
# Do not modify below values manually. Modifying below values would affect postgres clustering
For Example:
192.168.0.1 master
192.168.0.2 delegateIP
# VAMI_EDIT_BEGIN
# Generated by Studio VAMI service. Do not modify manually.
127.0.0.1  <hostname> <shortname> localhost
::1 <hostname> <shortname> localhost ipv6-localhost ipv6-loopback
 
After modifying the hosts file, the horizon service needs to be restarted:

service horizon-workspace restart
 
Cluster health was restored, and communication between nodes was re-established. The pgpool output confirmed all nodes were up with correct roles assigned.