Login page of CA PAM server is not loading

Document ID : KB000094730
Last Modified Date : 04/05/2018
Show Technical Document Details

 While trying to login to the CA PAM server, the login page does not appear, but the following message appears in the Web browser

This page can’t be displayed Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://<CA PAM SERVER> again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator.

CA PAM Version 2.8.x
This can be either standalone setup or a cluster setup.
One of the possible cause for this is that CA PAM is not able to respond to the incoming request from the client (Web Browser)
The most likely cause for this is that CA PAM does not have space for the log files to capture the incoming request as it might be out of disk space.

- With help of CA Support connect to CA PAM server
- Check the disk space utilization using "df -h" command
- In case the disk space is at 100%, then use the following command to find the filesystem that is consuming the highest disk space
- Command to check highest used disk space "du -hs *"
- Review the output and go to the filesystem which is consuming the highest disk space
- Run "du -hs *" again from the filesystem that is consuming the highest disk space
- This would list the directory which is having highest disk space usage
- Dig further into the directory to list the files that are consuming the high disk space
- In case the disk space utilization is being due to debug logs, then either transfer these logs to a different host using a file transfer utility (based of the log retention policy of the client), else delete the backup copies of the debug logs / backup copy of the log files to create disk space
- Once disk space is created, then either start the CSPM services manually by following the steps below
-- cd /opt/cloakware/cspmserver/bin/

/cspmserver stop

/cspmserver start

- The other option is to reboot the CA PAM host using the "reboot" command
- Once the CA PAM host is up, the login would be possible.
Additional Information:
- The above resolution would be effective only if the "Debug SSH" patch has been applied as well as "Remote Debugging" being enabled ahead of time.
- The CA PAM host should be reachable, ping response should be received.
- In case the files consuming large disk space are not the debug logs or regular logs, please look at cleaning up the "Tomcat logs", logs from "MySQL"