6.2

Table Of Contents
RabbitMQ Configuration Fails in a High-Availability
Environment
When RabbitMQ is restarted in a high-availability environment, vRealize Automation appliances must be
shut down and restarted in a specified order.
Problem
Restart of RabbitMQ for vRealize Automation in a high-availability environment fails.
Cause
vRealize Automation appliances must be shut down and restarted in a specified order.
Solution
The last vRealize Automation appliance that is shut down or stopped should be the first to be started (or
within 30 seconds of starting the second. The rabbitmq service on the other vRealize Automation
appliance waits 30 seconds for the rabbitmq service on the last stopped appliance to start before it fails. If
last stopped vRealize Automation appliance cannot be started, then reset rabbitmq on the other
vRealize Automation appliance by running
ssh script:vcac-vami rabbitmq-cluster-config reset_rabbitmq_node.
Encryption.key File has Incorrect Permissions
A system error can result when incorrect permissions are assigned to the Encryption.key file for a virtual
appliance.
Problem
You log in to vRealize Appliance and the Tenants page is displayed. After the page has begun loading,
you see the message System Error.
Cause
The Encryption.key file has incorrect permissions or the group or owner user level is incorrectly assigned.
Solution
Prerequisites
Log in to the virtual appliance that displays the error.
Note If your virtual appliances are running under a load balancer, you must check each virtual
appliance.
Procedure
1 View the log file /var/log/vcac/catalina.out and search for the message Cannot write
to /etc/vcac/Encryption.key.
Installation and Configuration
VMware, Inc. 177