CA PAM 2.8 A2A service not starting after 64-bit installation on RHEL

Products

• CA Privileged Access Manager - Cloakware Password Authority (PA)
• PAM SAFENET LUNA HSM
• CA Privileged Access Manager (PAM)

Issue/Introduction

After installing the 64-bit version of the A2A client on Red Hat Enterprise Linux, a service startup by running "<CSPM Client Home>/cspmclient/bin/cspmclientd start" will fail with message "Failed to start client daemon".

Cause

The startup script fails to set a variable that would make the client start in 64-bit mode. If the gtk2.i686 compatibility libraries were installed, the service would still startup successfully in 32-bit mode. But without these libraries startup will fail.

Environment

64-bit A2A client installed on RHEL 6 or 7 without gtk2.i686 compatibility libraries installed.

Resolution

To resolve this problem, edit the cspmclientd script and add the following line after line 4, which sets variable CSPM_CLIENT_HOME:

. $CSPM_CLIENT_HOME/cspmclient/bin/.cspmclientrc

Note the space between the leading dot and "$CSPM...". A modified file will look similar to the following:

 

#!/bin/sh

 

CSPM_CLIENT_HOME="/opt/cloakware"

. $CSPM_CLIENT_HOME/cspmclient/bin/.cspmclientrc

 

pid_file="$CSPM_CLIENT_HOME/cspmclient/var/pid_file"

...