• Verify that the vpxd service has stopped in the vCenter Server Appliance by running this command:

      service vmware-vpxd status 

• Verify that the vPostgres service has stopped by running this command:

      service vmware-vpostgres status 

• Verify that the vPostgres database is full by running this command:

      df -h
 

• In the vpxd log files, check whether you can see message similar to:

      No Space left on device 

• In the /storage/db/vpostgres/pg_log/postgresql.log file, you see entries similar to:
  
  PANIC: could not write to file ... No space left on device
  ERROR: could not extend file ... No space left on device
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 　

For more information about log files, see Location of vCenter Server log files (1021804).

1. Extend the disk size for the vPostgres database.
   For more information, see Increasing the disk space in vCenter Server Appliance 5.x (2056764).
2. To prevent full database partition, monitor the vCenter Server Appliance database disk usage and change the vCenter Server data retention settings.
   
   For more information, see Monitor vCenter Server Appliance database disk usage (2058187).
3. Delete all obsolete log files from /storage/db/vpostgres/pg_log/

Additional Information

• 日本語: vPostgres データベースが組み込まれた vCenter Server Appliance がデータベース パーティションの領域がいっぱいになったためクラッシュする (2102537)
• 简体中文: 带有嵌入式 vPostgres 数据库的 vCenter Server Appliance 因数据库分区已满而崩溃 (2116829)