Few weeks ago, I upgraded esxi hosts from 6.0 to 6.7 and everything went well. However, I observed this alarm on vcenter server few days ago.
From checks online, I saw that this was a common error with esxi 6.7, where the disk size of a particular SEAT partition is almost exhausted and will be fixed in newer releases. Trying to log into Vcenter server again yesterday, I got the error below
This meant I could not log into Vcenter or access all servers and hosts. However, I could log in individually into the hosts. So, I decided to fix this.
There are two ways to fix this temporarily. However, the permanent fix will be in newer releases/patches from VMware. The first way to fix this is to increase the disk size of the partition, however, this will also fill up in no time. The second method is what I will be showing today.
Log in to the Virtual Center appliance as root
– Stop all services but postgres
service-control --stop –all
service-control --start vmware-vpostgres
Truncate DB (to run with the script file below
/opt/vmware/vpostgres/current/bin/psql -U postgres -v TaskMaxAgeInDays=0 -v EventMaxAgeInDays=0 -v StatMaxAgeInDays=0 -d VCDB -t -q -f /download-path/2110031_Postgres_task_event_stat.sql
(The script file will be downloaded on the VMware portal and imported to a directory on the server)
/opt/vmware/vpostgres/current/bin/vacuumdb -U postgres -d VCDB –verbose
Then start all services
service-control --start –all
This should clear the SEAT partition and allow you back into the vCenter. You will then need to ensure that your vCenter is patched to the latest version, 6.7 U3C to permanently resolve this.