Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

SDDC Manager service(s) may fail to start with "Could not acquire change log lock." if the service or SDDC Manager is abruptly restarted during service initialization (71248)

Last Updated: 9/2/2021Categories: TroubleshootingTotal Views: 9702Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

In the /var/log/vmware/vcf/{service_name}/{service_name}.log, you see errors messages similar to the below:

2019-07-26T00:00:09.007+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:00:19.017+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:00:29.019+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:00:39.021+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:00:49.022+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:00:59.023+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:01:09.025+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:01:19.026+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:01:29.029+0000 INFO [0000000000000000,0000] [liquibase,main] Waiting for changelog lock....
2019-07-26T00:01:39.033+0000 WARN [0000000000000000,0000] [o.s.b.c.e.AnnotationConfigEmbeddedWebApplicationContext,main] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by 10.x.x.x (10.x.x.x) since 7/22/19 8:02 PM
2019-07-26T00:01:39.036+0000 INFO [0000000000000000,0000] [o.a.catalina.core.StandardService,main] Stopping service [Tomcat]

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

The SDDC Manager UI does may not display any domain information

UI displays "Failed to Poll" and "Failed to Fetch" messages

Failed to poll domain info. Could not reach the server., possible reasons could be network connectivity issue or server going down.
Failed too fetch allocation. Could not reach the server., possible reasons could be network connectivity issue or server going down

In the Common Services log, located at /var/log/vmware/vcf/commonsvcs, there are references to 502 Bad Gateway:

2019-07-11 08:56:50.443 ERROR [pool-2-thread-5] [com.vmware.evo.sddc.taskaggregator.services.TaskCollector] collect() failedorg.springframework.web.client.HttpServerErrorException: 502 Bad Gateway

Cause

A service acquires a database change log lock during initialization.

If this service is restarted or the VM rebooted before the lock was released, it will result in race condition. Subsequent service restarts will continue to wait for this lock.

Resolution

This is a known issue, to workaround the problem please follow the steps below.

Workaround

Take a backup/snapshot of the SDDC Manager VM before proceeding

Open an SSH to the SDDC Manager VM, change to root:

su -

Run the following command to drop the databasechangeloglock table for the failing service:

For VMware Cloud Foundation 3.7.x:

psql -h /home/postgresql/ -U postgres -d {service_name} -c 'drop table databasechangeloglock;'

For VMware Cloud Foundation 3.8.x and onward:

psql -h localhost -U postgres -d {service-name} -c 'drop table databasechangeloglock;'

Reboot the SDDC Manager VM to ensure all services come up successfully

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 4.3.x

VMware Cloud Foundation 4.2.x

VMware Cloud Foundation 4.1

VMware Cloud Foundation 4.0.x

VMware Cloud Foundation 3.9.x

VMware Cloud Foundation 3.8.x

VMware Cloud Foundation 3.7.x

VMware Cloud Foundation 3.10.x

VMware Cloud Foundation 3.0.x

view all

Take Our Survey

Support Assistant