FATAL: configuration file "/storage/db/vpostgres/postgresql.conf" contains errors

[massadinho]

I am having problems with Vcenter. I am getting "503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE: 0x0000562aca3f19b0] _serverNamespace = / action = Allow _pipeName = / var / run / vmware / vpxd-webserver-pipe)" when I connect via https.

I did some troubleshooting and narrowed down the issue to postgresql does not come up.

root @ photon-machine [~] # service-control - status

StartPending:

vmware-vpxd-svcs

Running:

applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-eam vmware-psc-client vmware-rhttpproxy vmware-sca vmware-statsmonitor vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon vsphere- client vsphere-ui

Stopped:

pschealth vmcam vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sps vmware-updatemgr vmware-vcha vmware-vpostgres vmware-vpxd vmware-vsan-health vmware-vsm

root @ photon-machine [~] # more / var / log / vmware / vpostgres / serverlog

LOG: syntax error in file "/storage/db/vpostgres/health_status_worker.conf" line 1, near token ""

LOG: skipping missing configuration file "/storage/db/vpostgres/postgresql.conf.repl"

FATAL: configuration file "/storage/db/vpostgres/postgresql.conf" contains errors

I am using the vcenter to manage NSX and do not want to rebuild the complete environment from scratch.

[vmrale]

Hi,

run df -h in vCenter's shell and show me the results.

Did it run stable earlier? What have changed in your environment and resulted in this error?

[massadinho]

Yes, it was working before. The last thing I did is delete two VMs from ESXi directly.

The disk usage looks good.

root@photon-machine [ ~ ]# df -h

Filesystem                                Size  Used Avail Use% Mounted on

devtmpfs                                  5.9G     0  5.9G   0% /dev

tmpfs                                     5.9G     0  5.9G   0% /dev/shm

tmpfs                                     5.9G  688K  5.9G   1% /run

tmpfs                                     5.9G     0  5.9G   0% /sys/fs/cgroup

/dev/sda3                                  11G  5.0G  5.1G  50% /

tmpfs                                     5.9G  880K  5.9G   1% /tmp

/dev/sda1                                 120M   35M   80M  30% /boot

/dev/mapper/netdump_vg-netdump            985M  1.3M  932M   1% /storage/netdump

/dev/mapper/imagebuilder_vg-imagebuilder  9.8G   23M  9.2G   1% /storage/imagebuilder

/dev/mapper/log_vg-log                    9.8G  759M  8.5G   9% /storage/log

/dev/mapper/updatemgr_vg-updatemgr         99G   65M   94G   1% /storage/updatemgr

/dev/mapper/core_vg-core                   25G   45M   24G   1% /storage/core

/dev/mapper/autodeploy_vg-autodeploy      9.8G   23M  9.2G   1% /storage/autodeploy

/dev/mapper/db_vg-db                      9.8G  101M  9.2G   2% /storage/db

/dev/mapper/seat_vg-seat                  9.8G   99M  9.2G   2% /storage/seat

/dev/mapper/dblog_vg-dblog                 15G  182M   14G   2% /storage/dblog

[vmrale]

Did You try to restart whole vCSA?

[massadinho]

Yes I did but with no success

[vmrale]

Did You replace certificates on vCSA recently? Or changed hostname or IP address?

What is the output of this command run in shell of vCSA?

cat /etc/vmware/deployment.node.type

[vmrale]

Check this if it's relevant for You:

VMware Knowledge Base

Don't focus on version and license, but check time in set vCSA and if it is syncronizing time from the host

[massadinho]

Here is the output of  the command

root@photon-machine [ ~ ]# cat /etc/vmware/deployment.node.type

embedded

[massadinho]

Unfortunately setting the time as per VMware Knowledge Base didn't help.

[bdubisz]

Quite old topic, but just in case if anyone else has similar problem..

LOG: syntax error in file "/storage/db/vpostgres/health_status_worker.conf" line 1, near token ""

Above error message indicates that "/storage/db/vpostgres/health_status_worker.conf" config file may be corrupted.

Open this file using vi and check if there is no corruption inside.

You can replace the content of this file from any other working VC running on the same build.

After that, you should be able to start postgres service.