TRBL problems and errors with vCenter Server and ESXi or clusters can be straightforward. One possible issue could be only that some services are no longer working.

The first action to perform during the troubleshooting of a problem that has occurred in the vCenter Server is to restart the service using the service-control command:

Command> service-control --list
vmware-vpostgres(VMware Postgres)
vmware-imagebuilder(VMware Image Builder Manager)
vmware-cm (VMware Component Manager)
vmware-vpxd (VMware vCenter Server)
...

Command> service-control --stop vmware-vpxd and service-control --start vmware-vpx

When you see a problem in vmkernel.log, you can check the next important component, that is, the vCenter Server database. Typical problems are disk capacity, CPU, and RAM. With vCSA, the only database that can be used is PostgreSQL, but with the Windows version of vCenter Server, both Microsoft SQL Server and Oracle can be used.

For the Windows-based vCenter Server, you may use the available monitoring tools as a part of the database that's used, such as the Management Studio for MS SQL or SQL Developer for Oracle. When you are using the vCSA, life is more much more comfortable, and you can use the new management console, vCenter Server Appliance Management Interface (VAMI), which is accessible through the browser at https://VCFQDN or IP:5480:

To verify the disk usage, you can go to the Monitor and Disks tab of the VAMI and check the reported value.

The next step to solve problems related to the database is to try and restart PostgreSQL using the service-control command. Next, it is usually useful to restart the problematic vSphere Web Client.

You can use any backup feature that's available so that the vCSA can restore the database.