7.4

Table Of Contents
To see which log files were collected, unzip the support bundle and open the Environment.html file in a
Web browser. Without connectivity, IaaS components might appear in red in the Nodes table. Another
reason that the IaaS logs are missing might be that the vRealize Automation management agent service
has stopped on IaaS Windows servers that appear in red.
General Installation Troubleshooting
The troubleshooting topics for vRealize Automation appliances provide solutions to potential installation-
related problems that you might encounter when using vRealize Automation.
Installation or Upgrade Fails with a Load Balancer Timeout Error
A vRealize Automation installation or upgrade for a distributed deployment with a load balancer fails with
a 503 service unavailable error.
Problem
The installation or upgrade fails because the load balancer timeout setting does not allow enough time for
the task to complete.
Cause
An insufficient load balancer timeout setting might cause failure. You can correct the problem by
increasing the load balancer timeout setting to 100 seconds or greater and rerunning the task.
Solution
1 Increase your load balancer timeout value to at least 100 seconds.
2 Rerun the installation or upgrade.
Server Times Are Not Synchronized
An installation might not succeed when IaaS time servers are not synchronized with the
vRealize Automation appliance.
Problem
You cannot log in after installation, or the installation fails while it is completing.
Cause
Time servers on all servers might not be synchronized.
Solution
Synchronize all vRealize Automation appliances and IaaS Windows servers to the same time source. Do
not mix time sources within a vRealize Automation deployment.
n
Set a vRealize Automation appliance time source:
a Log in to the vRealize Automation appliance management interface as root.
https://vrealize-automation-appliance-FQDN:5480
Installing vRealize Automation
VMware, Inc. 155