RSA Product/Service Type: Authentication Agent for Web for Apache
RSA Version/Condition: 7.1
Platform: Red Hat
O/S Version: 5
The following errors appear in the /etc/httpd/logs/error_log:
Thu Jan 24 15:51:11 2013] [notice] caught SIGTERM, shutting down
rpc_server 18165 started by 18154
AceShutdown try to kill process 18165
acestatus: error while loading shared libraries: libaceclnt.so: cannot open shared object file: No such file or directory
rpc_server 20358 started by 20348
RSALogoffCookieService: error while loading shared libraries: libaceclnt.so: cannot open shared object file: No such file or directory
[Thu Jan 24 15:51:20 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
start child 20359
As documented by RSA:
Apache versions refer to distributions available on www.apache.org. Prepackaged Apache modules available from other sources or vendors can result in incorrect behavior or missing functionality in the RSA agent.
In this particular use case, the $APACHEHOME is /etc/httpd; therefore when installing the agent, the agent will install to /etc/httpd/rsawebagent.
The Authentication Agent for Web for Apache expects to find the lib and bin directories (and their contents) a subordinate to $APACHEHOME; i. e., /etc/httpd/lib and /etc/httpd/bin respectively. In the use case of the precompiled rpm from Red Hat, it is not. The httpd executable for the rpm version from Red Hat is /usr/sbin, not /usr/local/apache (if --prefix=/usr/local/apache was used when apache was compiled from source), and when looking at an ldd /usr/sbin/httpd, it will search /lib64 and /usr/lib64, thusly be unable to locate or execute calls to libaceclnt.so.
To insure 100% compatibility, regardless of Authentication Agent for Web for Apache version, Apache needs be compiled from source for 100% compatibility., The agent should then be applied to the compiled from source instance of Apache. The agent was not qualified on Apache 2.2.3, and there are known issues by using the prepackaged version (for example, New PIN Mode may not work, throwing a 103 error when the prepackaged version is used as compared to working correctly when compiling from source.
In instances where you must use the Apache rpm that is bundled with Red Hat, the following workaround may be used, noting that there may be other issues as the agent was not qualified with the 2.2.3 rpm version from Red Hat after the agent is installed:
As root, create a symbolic link to the libaceclnt.so in the /lib64 directory:
cd /lib64 ln -s /etc/httpd/rsawebagent/libaceclnt.so libaceclnt.so
To view the link:
ls -al libaceclnt.so lrwxrwxrwx 1 root root 36 Jan 24 15:52 libaceclnt.so - /etc/httpd/rsawebagent/libaceclnt.so
Related Articles
Authentication Manager cannot send telemetry data warning on RSA Authentication Manager 8.5 and up 242Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' 3.62KNumber of Views Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … 365Number of Views AFX Server Fails to Start with 'Could Not Build a Validated Path' and 'Timed Out Waiting for AFX Applications to Start' in… 1.19KNumber of Views Error 413--Request Entity Too Large, now system cannot be restarted when updating RSA Authentication Manager 8.3.0.… 605Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process