ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
PAM Cluster will not restart
Article ID: 145394
CA Privileged Access Manager (PAM)
CA PAM v3.2.6
Following a incident of 100% CPU utilization on the primary site the cluster became out of sync. After restart, the CPU utilization went back to normal but the cluster still would not sync again, even after several attempts to restart the cluster.
Release : 3.2.6
Component : PRIVILEGED ACCESS MANAGEM
The Primary node was rebooted from the Config --> Power page. After doing this, the system was not accessible, either from the GUI or ssh. The VM was hard rebooted in VMware. After doing this the cluster started properly.
The 100% CPU utilization appears related to DE423942, which is listed as resolved in 3.3.1: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-privileged-access-management/privileged-access-manager/3-3-1/release-information/resolved-issues-in-3-3_1.html