vPostgres Service fails to start with error 'Could not write lock file"postmaster.pid": No space left on device

Products

• VMware Cloud Director

Issue/Introduction

Unable to login to VMware vCloud Director UI  as services fail to start , vcd and vpostgres services are not running with error " vPostgres Service fails to start with error 'Could not write lock file"postmaster.pid": No space left on device "

Environment

VMware vCloud Director 10.x

Cause

Since there is no space left on device and customer vpostgres is full, we cannot login to database and services fail to start 

Resolution

If you have insufficient space on the PostgreSQL database disk of your VMware Cloud Director appliance, you can increase the capacity of the embedded PostgreSQL database.

The PostgreSQL database resides on Hard disk 3. It has a default size of 80 GB. The procedure can be done while the appliances are operational.

If your VMware Cloud Director environment has standby nodes, identify the standby nodes and the primary node, and begin the procedure from a standby node.

 

 

1. Log in to the vSphere Client to increase the capacity of Hard Disk 3 to the size that you want.
   The PostgreSQL database disk size on each standby appliance must be as large as the PostgreSQL database disk on the primary appliance.
   1. Select the appliance virtual machine that you want to change.
   2. Select >Actions..
   3. Increase the size of hard disk 3 and click ok
    
2.  Apply the changes to the OS of an appliance node 

    

   Log in directly or by using an SSH client to the VMware Cloud Director appliance console as root.

   1. To apply the hard disk resizing change to the OS, run the following script.
       

      /opt/vmware/appliance/bin/db_diskresize.sh