When installing either CA Spectrum or CA Performance Management (CAPM) components (such as the DA) on Linux, the install fails to proceed and the following error is seen:
Preparing to install
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
JRE libraries are missing or not compatible....
Error when installing data collector
There is no space or incorrect permissions on the /tmp/ directory.
CA Spectrum, CA Spectrum Remote Administration (SRAdmin) Daemon and CAPM component installations require root privileges to evaluate available resources and run custom installation scripts. Installing under the root ensures root privileges for the setuid executable, which lets the SpectroSERVER connect to SNMP ports. Because an initial installation generates residual files with root ownership, subsequent upgrade installations also require root privileges.
It could also be due to system hardening through fapolicyd (Linux 8.x+)
CA Performance Management
OS: RHEL (any supported release)
Space or access to /tmp:
Make sure there is sufficient space in /tmp/ folder and the root user has full permission on /tmp/ folder.
Is it writeable and executable for the root user?
Check the directory permissions as follows:
# ls -ld /tmp
drwxrwxrwt. 12 root root 4096 Jul 19 04:13 /tmp
To check the disk space available in /tmp, run:
You can grant exec permissions to /tmp:
mount -o remount,exec /tmp
If it is not possible to provide required access to /tmp folder or there is insufficient space, you can install CA Spectrum or CAPM using a different folder as tmp folder by redirecting the System /tmp to to another file system with sufficient space. For example:
chown root.root /<AnotherFilesystem>/tmp
chmod 1777 /<AnotherFilesystem>/tmp
Check for the existence of /etc/fapolicyd/fapolicyd.rules
If the file exists, it is likely that fapolicyd is configured. While fapolicyd's use is untested or validated and thus is not supported, it may be possible to add an exception for the software to run like the below example for the Data Repository. Note: this does require restarting fapolicyd:
# Carve out exceptions for Vertica
allow perm=any uid=1003 : dir=/opt
allow perm=any uid=1003 : dir=/opt/vertica
allow perm=any uid=1003 : dir=/data
allow perm=any uid=1003 : dir=/catalog
allow perm=any uid=1003 : dir=/opt/CA
Verify that the 32 bit glibc package is installed. If not, the installer will error;
sudo yum install -y glibc.i686