[vRSCLM] Loop Loading Issue Caused by Expired Postgres Account

During a fresh vRSCLM 8.18 deployment UI may remain stuck in a continuous loading loop. The deployment task fails, and the appliance never becomes fully operational.

In this case, the root cause was an expired postgres system account.

The issue is clearly visible through the VM Remote Console, which reports that user 1001 is in a fault state.

Reviewing the vpostgres.service logs shows errors indicating that pg_ctl is unable to open the PID file in the vpostgres directory.

Further investigation of the user@1001.service logs reveals multiple “Operation not permitted” errors, which are consistent with an expired password.

To resolve the issue, update the password expiration date for the postgres user using the “chage” command.