vpostgres.service Shows Failed State via systemctl on VMware Identity Manager

Products

• VCF Operations

Issue/Introduction

• On VMware Identity Manager (vIDM), querying the 'vpostgres.service' via 'systemctl status' persistently reports a "failed" state, despite the cluster remaining fully operational. All other services may report as active.
• The following errowill be presented;
  

  Active: failed (Result: exit-code) since <DATE> Process: <PID> ExecStart=/etc/rc.d/init.d/vpostgres start (code=exited, status=1/FAILURE)

Environment

• VMware Identity Manager 3.3.7

Cause

The 'systemctl' status reporting for the 'vpostgres' service has become desynchronized from the actual functional state of the service due to a known reporting artifact within the core product's OS integration.

Resolution

• Do not perform corrective service restarts (e.g., service vpostgres stop / start) based on systemd output, as modifying the service introduces unnecessary risk to an otherwise functional database cluster.

• Ignore the inaccurate systemctl status output for vIDM services.

• Exclusively utilize the /etc/init.d/<service> status command syntax to accurately monitor service health on vIDM appliances.

• Verify the true operational state of the services by executing the following commands:

  • /etc/init.d/vpostgres status

  • /etc/init.d/pgService status

  • /etc/init.d/opensearch status