PAM 3.3.1 Cluster was turned off and shutdown.
When the PAM is powered on, "CA PAM is starting up" is displayed and unable to logon.
PAM 3.3.1 (and also 3.3.0) has a known issue with SequenceManager that can fail to initialize.
There can be 2 types of exceptions.
#1. SequenceManager.initialize Exception: Value 'xxxxxxxxx' is outside of valid range for type java.lang.Integer
#2. SequenceManager.initialize Exception: Communications link failure
If it is for #1 exception there is hotfix 184.108.40.206 (220.127.116.11) to address it.
#2 does not have any hotfix as of 2020-08-12.
Restart of cspm did not resolve these issues.
This happens even when the Cluster is switched off correctly.
As long as tomcat fails to initialize all its services, PAM will be displaying the "CA PAM is starting" message.
Release : 3.3
Component : PRIVILEGED ACCESS MANAGEMENT
Upgrade to PAM 3.3.3 resolves both issues.