We started the upgrade from our vIDM installation from 3.3.4 to 3.3.5 in vRLCM but it hangs at "Waiting for SaaS to come up on the VMware Identity Manager Host". Looking at the IDM system diagnostic page turns out that the "ACS Health - Application Deployment Status" service was in error state.
The log file for this service is found at /opt/vmware/horizon/workspace/logs/accesscontrol-service.log and there was the error:
ERROR your.idm.appliance.com:accesscontrol (localhost-startStop-5) [;;;] org.springframework.boot.SpringApplication - Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/vmware/vidm/accesscontrol/db/DbDataStoreAutoConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by 0.0.0.0 (0.0.0.0) since 11/11/11 11:11
This brings me to the KB Following an upgrade Workspace fails to start correctly with error: Could not acquire change log loc...
The KB is not very detailed so here are all the steps i did:
- get the PostgreSQL DB password:
cat /usr/local/horizon/conf/db.pwd
- Login to the DB with the above password:
psql -U horizon saas
- View the lock entry:
SELECT * FROM saas.ACS_DATABASECHANGELOGLOCK;
- Remove the lock:
UPDATE saas.ACS_DATABASECHANGELOGLOCK set LOCKED=false, LOCKGRANTED=null, LOCKEDBY=null where ID=1;
- Close the DB connection:
\q
- Reboot the appliance and the vRLCM task finished successfully
Drink coffee.. Do stupid things faster with more energy...
