Login fails with an 'Internal Server Error' when using SiteMinder SSO to log into RSA Identity Governance & Lifecycle
Originally Published: 2017-05-01
Article Number
Applies To
RSA Product/Service Type: Appliance
RSA Version/Condition: All
Platform: Red Hat
Issue
Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.3 (Red Hat) Server at <hostname> port 80
Analysis:
- RSA Identity Governance & Lifecycle is accessible by directly logging into the server with:
https://<hostname>/aveksa/main
- There are no errors in the server.log or the aveksaServer.log.
- /etc/sysconfig/iptables has the correct settings.
- SiteMinder is used for SSO login.
- The SiteMinder log file located in /var/log/httpd/error_log is full of these errors:
[30/Apr/2017:04:02:27] [Error] [CA WebAgent IPC] [3505] [CSmSem::SemWait]
Error performing decrement operation on semaphore 19267598 - Invalid argument (22)
[30/Apr/2017:04:02:27] [Info] [CA WebAgent IPC] [3505] [CSmSem::getSem]
Attempted to attach to non-existent semaphore with key 0x6690874a
[30/Apr/2017:04:02:27] [Error] [CA WebAgent IPC] [3505] [CSmNamedMutex::Lock]
Error reinitializing mutex with key base 0x66
[30/Apr/2017:04:02:27] [Error] [CA WebAgent IPC] [3505] [CSmSem::SemWait]
Error performing decrement operation on semaphore 19070984 - Invalid argument (22)
[30/Apr/2017:04:02:27] [Info] [CA WebAgent IPC] [3505] [CSmSem::getSem]
Attempted to attach to non-existent semaphore with key 0x6b90874a
[30/Apr/2017:04:02:27] [Error] [CA WebAgent IPC] [3505] [CSmNamedMutex::Lock]
Error reinitializing mutex with key base 0x6b
[30/Apr/2017:04:02:27] [Error] SiteMinder Agent
PID Cache error.
Failed to read PID Cache
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.
Cause
Resolution
For further root cause analysis and/or to determine other ways to rectify this issue, please contact your SiteMinder vendor as this is a third party product that we neither license nor deploy.
Workaround
Related Articles
Unable to log into Microsoft apps on Android devices when Microsoft Office 365 is configured with the RSA SecurID Access A… 51Number of Views Authentication Dashboard 91Number of Views RSA SecurID Hardware Token Data Sheet 47Number of Views RSA Governance & Lifecycle LDAP Novell eDirectory Connector Datasheet 19Number of Views Unable to log in to the RSA Community after twelve months or more of inactivity 99Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?