When attempting to install the Introscope Workstation on CentOS 7, the installation exits with the error
"JRE libraries are missing or not compatible....
CentOS 7 64-bit, APM 10.1 Workstation
There are a number of required 32-bit libraries missing that need to be installed to complete the installation and to allow the Workstation to run
To allow the installer to run, you need the ld-linux.so.2 module. This is supplied by glibc 32-bit package.
So you need to run this command to install the relevant package:
yum install glibc.i686
To allow the Workstation to run, you will need to install the following packages also:
yum install libXext.i686
yum install libXrender.i686
yum install libXtst.i686
yum install libgcc.i686
- To troubleshoot initially, you may run the installer like this
sh -x ./IntroscopeWorkstation10.1.0.15linux.bin
which gives this error:
+ jre_success='./IntroscopeWorkstation10.0.0.12linux.bin: /tmp/install.dir.54166/Linux/resource/jre/bin/java: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
running the command:
yum provides ld-linux.so.2
points us to glibc.i686, so we need to install that package.
- For other libraries required for the Workstation to run, edit the Introscope_Workstation.lax to output information to a log file:
In the lax.log file search for UnsatisifedLinkError, for example
Caused by: java.lang.UnsatisfiedLinkError: /user/IntroscopeWorkstation10.1.0.15/jre/lib/i386/libfontmanager.so: libgcc_s.so.1: cannot open shared object file: No such file or directory
Again using yum provides, so in this case
yum provides libgcc_s.so.1
points us to the requirement for libgcc.i686
- One final point, when installing the 32-bit packages you may see this error:
Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just
pointing out that there is a problem.
The likely cause of this is that the 64-bit version of the package is at an older release than the 32-bit package you are installing. So, you may need to update any 64-bit package that gives this error (yum update <package name) and then try to install the 32-bit package again.