CA PAM Server is starting up. Please try again later.
Document ID :
Last Modified Date :
Show Technical Document Details
CA Privileged Access Management
PRIVILEGED ACCESS MANAGEMENT:CAPAMX
When trying to connect to a CA PAM appliance the error below is encountered:
"CA PAM Server is starting up. Please try again later."
After allowing 10+ minutes for the CA PAM Server to finish starting up the same error occurs
This can effect any number of appliances
Rebooting the appliance(s) does not solve the problem
This error usually occurs when a PAM Appliance is starting up and thinks that it is already in an active cluster during startup. When this happens, PAM may not be able to re-join the cluster (depending on what type of site the node is a member of) and will instead stop itself from starting the web server fully because it finds that it has been deactivated from the cluster or can't reach it's cluster members.
Common causes of this situation are:
Rebooting PAM Nodes while the Cluster is turned on (Note: PAM will not allow graceful shutdown from the GUI when clustered)
Reverting a VM PAM appliance to a snapshot that was taken while the cluster is running
Network issues or vMotion may cause split-brain situations which can lead to this problem during reboot
To resolve this this issue, follow these steps:
Depending on your current cluster status, it is possible that step 4 can shut down the whole cluster. The cluster will need to be shut down anyway to bring the effected node(s) back in, so it is recommended to shut the rest of the cluster down first if it is currently running.
Navigate to the following link in a Web Browser: https://<PAM_Address>/config/?legacy=1
Login as the config user
Navigate to: Configruation > Clustering
Click the button "Turn Cluster Off".
The cluster will turn off on this node and possibly other nodes if they were still clustered. Ensure clustering is shut down on each effected node before continuing.
Once clustering is shut down on the effected nodes the standard login page becomes active for logins. Login to confirm everything is working.
Either restart the Cluster if clustering will continue to be used (Configuration > Cluster > Turn Cluster On) or if this node is being removed from the cluster Unlock it's Database (Configuration > Cluster > Unlock Me)
Tips to prevent this situation from happening again:
Never pull the power plug or otherwise reboot PAM while the cluster is enabled unless directed to by Support
Ensure the cluster is turned off or the individual node has been safely removed before patching or other major changes
Never take LIVE (running) VM snapshots of PAM Appliances (Snapshots taken while PAM is powered off are acceptable)
Disable vMotion for all PAM Appliances
Default credentials for the Config User:
Was this information helpful?