VRA services fail to register after Disaster Recovery

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:
After Disaster Recovery, the vRealize Automation services are not coming up, due to problems with Messaging, Database and SSO components.

Environment

VMware vRealize Automation 7.4.x

Resolution

This is a known issue.

Currently, there is no resolution.

Workaround:
To workaround this issue,

1. To reset and set rabbitmq node & cluster follow,

• For vRealize 7.2.x - Resetting RabbitMQ cluster in vRealize Automation 7.x

 

2. Restart the database services on all vRA nodes.
   1. SSH login to each appliance node and execute:
      • service vpostgres stop
      • service vpostgres start
      • service vpostgres status
   2. Check the database status in VAMI.
3. Follow the instruction on Restart vRealize Automation in VMware Docs
4. Powered on all vRA VMs.

Additional Information

Details of the issue:

The vRA services, Messaging, Database and SSO report bad states after Disaster Recovery of Cloud Management platform.

vRA VAMI--> Services page shows blank page

The vRA VAMI Messaging page shows:

Connection Status NOT Connected: Connection refused (Connection refused)
RabbitMQ Process [Error]: Can't determine the internal rabbitmq server status.

The vRA VAMI Database page shows:

"Error initializing the database service: Could not open JDBC Connection for transaction; nested exception is org.postgresql.util.PSQLException: FATAL: too many connections for role \"vcac\""

The vRA VAMI SSO page shows:

SSO Info :404