VA cluster component stuck at reboot

SailPoint Human Fabric (SHF) SHF Discussion and Questions
, ,
1

“detailedMessage”: “pag service has restarted 56 times in the last 30 minutes”,
“restartCount”: 56,
“uuid”: “49861b60-7083-42f2-854a-fd75190941bb”,
“timestamp”: “2026-08-06T13:23:08.570Z”,
“lastNotifiedTimeStamp”: “2026-08-06T13:23:09.020679446Z”,
“severity”: “errors”,
“category”: “container”

PAG cluster component stuck at reboot state.

Already tried readding a new VA.

Have two VA’s one of them updated with the expected cluster components but the other when keep on failing.

Showing critical error on the cluster.

2

Hi Sam, this matches SailPoint’s Service Stability warning, which triggers when a container restarts more than 10 times in 30 minutes.

image
image1416×291 25.9 KB

First, try restarting the cluster from Admin > Connections > Virtual Appliances > Actions > Restart Cluster.

Also verify that both VAs meet the additional PAG resource requirements: 2 processors and 4 GB RAM per VA above the base minimums.

Since you already tried adding a new VA, if the issue continues after the restart and resource check, I would suggest opening a SailPoint Support case.

3

@Sam_Seth

If one VA updated successfully but the second VA is stuck at reboot/critical state, it usually requires SailPoint Support intervention to clear or recover the failed cluster component state. Also verify network/proxy/firewall because similar “update in progress/stuck” issues are often caused by network connectivity problems