This article helps to get the vPostgres service up if the service is failing to start with FATAL error “bogus data in lock file postmaster.pid”
# service-control –start vmware-vpostgres
Perform start operation. vmon_profile=None, svc_names=[‘vmware-vpostgres’], include_coreossvcs=False, include_leafossvcs=False
2019-11-06T21:38:14.283Z Service vmware-vpostgres state STOPPED
Error executing start on service vmware-vpostgres. Details {
“resolution”: null,
“detail”: [
{
“args”: [
“vmware-vpostgres”
],
“id”: “install.ciscommon.service.failstart”,
“localized”: “An error occurred while starting service ‘vmware-vpostgres’“,
“translatable”: “An error occurred while starting service ‘%(0)s'”
}
],
“componentKey”: null,
/var/log/vmware/vpostgres/serverlog.stderr log content :-
~
~
Starting service process with pid: 61183.
LOG: skipping missing configuration file “/storage/db/vpostgres/postgresql.conf.repl”
LOG: skipping missing configuration file “/storage/db/vpostgres/postgresql.conf.repl”
2019-11-06 21:38:14.700 UTC 5dc33d46.eeff 0 FATAL: bogus data in lock file “postmaster.pid”: “”
Location of the postmaster.pid file :-
root [ /var/log/vmware/vpostgres ]# ls -l /storage/db/vpostgres/postmaster.pid
-rw——- 1 vpostgres users 45 Oct 30 17:20 /storage/db/vpostgres/postmaster.pid
If you try to read the postmaster.pid file with cat or less command, you will see junk characters.
To fix the issue, rename or move the file with mv command :
# mv /storage/db/vpostgres/postmaster.pid /storage/db/vpostgres/postmaster.pid_bkp
You would be able to start the vPostgres service now :service-control –start vmware-vpostgres