Performance Management installations fail during /tmp usage

Products

• CA Infrastructure Management
• CA Performance Management - Usage and Administration
• DX NetOps

Issue/Introduction

Performance Management Performance Center Console, Data Aggregator, Data Collector and Data Repository installations can be observed failing with errors due to problems accessing or writing to the /tmp directory.

Examples of the problems seen:

• Permission denied errors trying to run a program from, or write to /tmp
• For example we see these errors in Data Aggregator and Data Collector installations:

Command.run(): Cannot run program "/tmp/792691.tmp/executeScriptTmp0": error=13, Permission denied

• Performance Center Console installations may show:

Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory file

• Data Repository installDR.bin extraction may show the following error:

Unpacking the JRE... 
Extracting the installation resources from the installer archive... 
Configuring the installer for this system's environment... 
Launching installer... 
JRE libraries are missing or not compatible.... 
Exiting....

Cause

There are three common causes for these issues with the /tmp directory.

1. Wrong user being used.
2. Low available disk space in /tmp where the installation defaults to for writing and running code necessary to the installation.
3. The /tmp location is configured with 'noexec' permissions.

Environment

All supported CA Performance Management product releases and their CA Performance Center, CA Data Aggregator, CA Data Collector components. NetOps 20.2

Resolution

The solutions for these problems are:

1. Ensure the correct user, normally root or a specially configured sudo root user, is running the installation commands.
2. Add more space to /tmp. Ensure a minimum of 4 GB of free disk space is available for the installation to utilize.
3. Remount /tmp without the /noexec permission or specify an alternate directory for the installation to utilize. To do this we run the install command after specifying an alternative location with the IATEMPDIR variable.

The sample command is:

• • • IATEMPDIR=<NewPath> ./<installCommand>

For instance it might look like this for the installDR.bin or installDA.bin commands redirected to /opt/tmp.

• • • IATEMPDIR=/opt/tmp ./installDA.bin -i console 
    • IATEMPDIR=/opt/tmp ./installDR.bin