Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

vPostgres service fails to start on vCenter Server Appliance Error : FATAL: lock file "/var/run/vpostgres/.s.PGSQL.5432.lock" is empty (76374)

Last Updated: 1/10/2021Categories: TroubleshootingTotal Views: 33708Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

vCenter services will fail to start as vPostgres service is in a stopped state

When try to start the service manually we get the following error trace :

Operation not cancellable. Please wait for it to finish...
Performing start operation on service vmware-vpostgres...
Error executing start on service vmware-vpostgres. Details {
"detail": [
{
"args": [
"vmware-vpostgres"
],
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'",
"localized": "An error occurred while starting service 'vmware-vpostgres'"
}
],
"componentKey": null,
"resolution": null,
"problemId": null
}
Service-control failed. Error: {
"detail": [
{
"args": [
"vmware-vpostgres"
],
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'",
"localized": "An error occurred while starting service 'vmware-vpostgres'"
}
],
"componentKey": null,
"resolution": null,
"problemId": null
}

Cause

Checking the serverlog.stderr log we find the following:

Starting service process with pid: 17384.
LOG:  skipping missing configuration file "/storage/db/vpostgres/postgresql.conf.repl"
LOG:  skipping missing configuration file "/storage/db/vpostgres/postgresql.conf.repl"
2019-11-21 14:52:54.932 UTC 5dd6a4c6.43e8 0   FATAL:  lock file "/var/run/vpostgres/.s.PGSQL.5432.lock" is empty
2019-11-21 14:52:54.932 UTC 5dd6a4c6.43e8 0   HINT:  Either another server is starting, or the lock file is the remnant of a previous server startup crash.
2019-11-21 14:52:54.932 UTC 5dd6a4c6.43e8 0   LOG:  database system is shut down

The vPostgres Service is failing to start because the contents of ".s.PGSQL.5432.lock" database lock file are missing.

Impact / Risks

vCenter services including the vpxd won't start until and unless vPostgres service is running.

Resolution

Follow the below steps to solve this issue:

1. Take a Snapshot of the vCenter Server Appliance virtual machine.
2. Login to the Appliance shell via SSH.
3. Got to this location : /var/run/vpostgres
4. Locate the file named as .s.PGSQL.5432.lock
5. Open the file in editor : vi .s.PGSQL.5432.lock
6. Enter the following in the file:

21810
/storage/db/vpostgres
1574278293
5432
/var/run/vpostgres
.s.PGSQL.5432.lock (END)

7. Save the file and restart all the vCenter Services.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant