PostgreSQL Service fails to start after rebooting Fleet Management appliance post VCF Operations 9.0.1 upgrade

Products

• VCF Operations

Issue/Introduction

After applying the 9.0.1 patch to the VCF Operations fleet management appliance, you may experience the following symptoms only if you reboot the Fleet Management appliance:

• The PostgreSQL service fails to start after rebooting the appliance.
• The system journal contains "Permission denied" errors related to the PostgreSQL process ID (PID) file, which is located at /var/vmware/vpostgres/current/pgdata/postmaster.pid.
• Certificate of VCF Operations fleet management is regenerated

You will see log entries similar to the following:

Sep 18 15:33:07 <hostname> postgres[12859]: pg_ctl: could not open PID file "/var/vmware/vpostgres/current/pgdata/postmaster.pid": Permission denied
Sep 18 15:33:07 <hostname> systemd[1]: vpostgres.service: Control process exited, code=exited, status=1/FAILURE

Environment

VCF Operations Fleet Management Appliance 9.0.1

Resolution

Procedure

1. Apply the correct permissions to the pgdata folder by executing the following command:

   chmod 700 /var/vmware/vpostgres/current/pgdata/

2. Navigate to the /opt/vmware/vlcm/cert directory. The key and certificate files requiring change will have a timestamp in their names (e.g., server.crt.250930102056).
   
   Run the following commands to move the timestamped files into place, replacing the filenames with the ones in your directory:

   mv server.key.250930102056 server.key
   mv server.crt.250930102056 server.crt
   
   

3. Disable the "cap_init" service executing the below command:

   systemctl disable cap_init
systemctl daemon-reload

4. Restart the Nginx service:

   systemctl restart nginx

5. Restart the Lifecycle Manager service:

   systemctl restart vrlcm-server.service

6. Wait a couple of minutes for the service to initialize. You can check its status with the command below:

   systemctl status vrlcm-server.service

7. Monitor the service startup log to confirm it is fully operational. This process may take several minutes.

   tail -f /var/log/vrlcm/vmware_vrlcm.log