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

Products

• VCF Operations/Automation (formerly 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. The vIDM nodes were unable to communicate with the master node, impacting overall cluster health.

In a few scenarios, when running the show pool_nodes Command to check the database cluster status, the operation fails with the following error:

psql.bin: FATAL:  failed to create a backend connection
DETAIL:  executing failover on backend

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:

##.##.##.## master

##.##.##.## 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.