7.1

Read and write permission is required and the owner and group for the le must be vcac.
3 If the output you see is dierent, change the permissions or ownership of the le as needed.
What to do next
Log in to the Tenant page to verify that you can log in without error.
Identity Manager Fails to Start After Horizon-Workspace Restart
In a vRealize Automation high availability environment, the Identity Manager can fail to start after the
horizon-workspace service is restarted.
Problem
The horizon-workspace service cannot start due an error similar to the following:
Error creating bean with name 'liquibase' dened in class path resource [spring/datastore-wireup.xml]:
Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire
change log lock. Currently locked by fe80:0:0:0:250:56:fea8:7d0c%eth0 (fe80:0:0:0:250:56:fea8:7d0c%eth0)
since 10/29/15
Cause
The Identity Manager may fail to start in a high availability environment due to issues with the liquibase
data management utility used by vRealize Automation.
Solution
1 Log in to the vRealize Automation appliance as root using ssh.
2 Run the service horizon-workspace command to stop the horizon-workspace service.
3 Run the su postgres command to become a postgres user.
4 Run the command psql vcac.
5 Run the following SQL query: "update "databasechangeloglock" set locked=FALSE,
lockgranted=NULL, lockedby=NULL where id=1;"
6 Run the SQL query select * from databasechangeloglock.
The output should show a value of "f" for locked.
7 Start the horizon-workspace service using the command service horizon-workspace start.
Incorrect Appliance Role Assignments After Failover
After a failover occurs, master and replica vRealize Automation appliance nodes might not have the correct
role assignment, which aects all services that require database write access.
Problem
In a high availability cluster of vRealize Automation appliances, you shut down or make the master
database node inaccessible. You use the management console on another node to promote that node as the
new master, which restores vRealize Automation database write access.
Later, you bring the old master node back online, but the Database tab in its management console still lists
the node as the master node even though it is not. Aempts to use any node management console to clear
the problem by ocially promoting the old node back to master fail.
Chapter 6 Troubleshooting a vRealize Automation Installation
VMware, Inc. 129