When trying to connect to a CA PAM appliance the error below is encountered:
"CA PAM Server is starting up. Please try again later."
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:
Before proceeding to the steps listed below you may find that rebooting the node from the VM console (VMware, AWS, or Azure) or from the LCD panel for physical hardware may allow the appliance to start normally after waiting some time. Since the steps below may take some time it is beneficial to at least try restarting once after waiting about an hour.
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.
Tips to prevent this situation from happening again:
Default credentials for the Config User: