This documentation supports the 9.0 version of BMC Atrium Single Sign-On, which is in "End of Version Support." However, the documentation is available for your convenience. You will not be able to leave comments.

Click here to view the documentation for a supported version of Remedy Single Sign-On.

Resolving installation issues on a Linux operating system

You may face the following issues while installing BMC Atrium Single Sign-On on Red Hat Enterprise Linux computers.

The following topics are provided:

Installation failure due to missing libraries

If you are installing BMC Atrium Single Sign-On on 64-bit version of Red Hat Enterprise Linux (RHEL) 6.x and the installer stops suddenly, then you must install the following 32-bit RPM packages to make 32-bit JRE support and the user interface available to the installer:

  • Glibc.i686
  • libXtst.i686

Installation failure due to insufficient execute permissions


This issue may occur on LINUX and Solaris operating systems.

Due to security issues, the temporary storage directory, $TMP may not have execute permissions. If BMC Atrium SSO installer is running, the script tries to create and run the script from the $TMP directory. But the script fails to execute due to denied permissions for the $TMP directory, which results in installation failure.


The $TMP directory must have execute permissions for running the BMC Atrium SSO installer. You can assign the execute permission by removing the noexec attribute from the /tmp line in the /etc/fstab file. For example,

UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp                    ext4    defaults,noexec        1 2

Remove the noexec attribute from the line and save the file.

UUID=0aef28b9-3d11-4ab4-a0d4-d53d7b4d3aa4 /tmp                    ext4    defaults        1 2

Installation failure due to low level of entropy

In computing, entropy is the randomness collected by an operating system or an application for use in cryptography, or for other uses that require random data. This randomness is often collected from hardware sources: either existing sources such as mouse movements, or specially provided randomness generators. When the entropy level in an application decreases beyond a certain level, the Linux operating systems running the BMC Atrium Single Sign-On (SSO) installation might fail.

During installation, BMC Atrium Single Sign-On (SSO) logs the entropy level for maintenance purposes. For successful installation of BMC Atrium Single Sign-On, the entropy level must be substantially higher than 3000. If an installation or silent installation stops suddenly, finishes very quickly, or takes a long time to complete,  the computer might be experiencing low entropy issues. When the entropy level on the computers running the BMC Atrium Single Sign-On installer is under 3000, the installation fails with the following error message:

There is potential problem with performance on this computer. The level of entropy is 3000 and the random data generation time is 6 milliseconds. You may run the following command as root user: 'rngd -b -r /dev/urandom -o /dev/random' or prefer to restart the computer.


You can verify the level of entropy from the entropy_avail file on the Linux computers by using the following command: cat /proc/sys/kernel/random/entropy_avail.


To restore the optimum entropy level and install BMC Atrium Single Sign-On, use one of the following options:

  • As root user, configure your server to run the following commands during server startup. This option is preferred because it helps to maintain the entropy level after installation.

    yum install rng-tools
    echo 'EXTRAOPTIONS="-i -o /dev/random -r /dev/urandom -t 10 -W 2048"' >>/etc/sysconfig/rngd
    chkconfig rngd on
    service rngd restart
  • Restart your computer. This option is not recommended and will temporarily increase the entropy level. You can use this option to determine whether entropy is the only reason for the installation failure.
Was this page helpful? Yes No Submitting... Thank you