FMS crashed and fails to start with message ERROR: database is not accepting commands to avoid wraparound data loss in database (4374844)

FMS (Foglight Management Server) fails to start after a crash.

Management Server log shows an error message like this:

ERROR   [forge-startup] com.quest.nitro.service.topology.provider.wcfsdo.TopologyLoader - An unexpected error occurred which may cause undesired behavior. You may want to contact customer support if you see this error again: Failed to add domain contributor for domain: Forge
com.quest.nitro.service.sl.interfaces.topology.OptimisticLockException: ERROR: database is not accepting commands to avoid wraparound data loss in database "foglight"
  Hint: Stop the postmaster and vacuum that database in single-user mode.
You might also need to commit or roll back old prepared transactions.
    at com.quest.nitro.service.topology.persistence.TopologyPersistence.insertObjectHistory(TopologyPersistence.java:477)
    at com.quest.nitro.service.topology.TopologyService.finalizeUpdate(TopologyService.java:3735)
    at com.quest.nitro.service.topology.TopologyService$ObjectUpdateAction.performAction(TopologyService.java:3592)
    at com.quest.nitro.service.topology.TopologyService$ObjectUpdateAction.performAction(TopologyService.java:3577)
    at com.quest.nitro.service.topology.TopologyService.performTransactionalAction_aroundBody24(TopologyService.java:4833)
    at com.quest.nitro.service.topology.TopologyService$AjcClosure25.run(TopologyService.java:1)
    at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
 

VACUUM can correct this issue but his needs to be run in single-user mode.

These are example steps to start the embedded PostgreSQL repository database in single-user mode in Linux.

cd /opt/quest/Foglight/postgresql/bin/
./postgres --single -D /opt/quest/Foglight/state/postgresql-data foglight
backend> vacuum full;

This operation takes some time to complete.