LEM Agent Install on Linux OS error: Installer User Interface Mode Not Supported

5/29/2019 5:46 PM

5/29/2019 5:46 PM

This article provides work round for an error that occurs when you install a SEM LInux agent on a server running a Linux OS.

1. You logged into any rpm (confirmed on CentOS and RHEL 7) based distribution of Linux and tried to install LEM agent (6.x) by executing the following commands as root:

#chmod +x setup.bin
#./setup.bin

2. You encountered the following message(which may varies slightly with Linux distribution, this message is  noted on RHEL 7.x), and the installer exits without completing the installation.

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...
Launching installer...
HRE libraries are missing or not compatible....
Exiting....

3. Check the version and distribution of JRE/JDK installed

[root@mypc]#yum list installed | grep java

java-1.8.0-openjdk.x86_64 1:1.8.0.171-8.b10.el7_5 @rhel-7-server-rpms
java-1.8.0-openjdk-headless.x86_64 1:1.8.0.171-8.b10.el7_5 @rhel-7-server-rpms
javamail.noarch 1.4.6-8.el7 @rhel-7-server-rpms
javapackages-tools.noarch 3.4.1-11.el7 @rhel-7-server-rpms
python-javapackages.noarch 3.4.1-11.el7 @rhel-7-server-rpms
tzdata-java.noarch 2018e-3.el7 @rhel-7-server-rpms

4. Enabled LAX DEBUG mode to see verboseinstall progress and error. Noted on RHEL 7 and CentOS7 x64-bit.

[root@mypc]# export LAX_DEBUG=true
[root@mypc]# ./setup.bin -i console No of blocks of size 8192 to extract for custom unix file : 1 Extracting locale bundle from ./setup.bin to /home/myuser/custom_padded ...
Extracting done, exit code = 0
Extracting locale bundle from /home/myuser/custom_padded to /home/myuser/custom ...
Extracting done, exit code = 0
Preparing to install
Checking for POSIX df.
Found POSIX df.
========= Analyzing UNIX Environment ================================= Setting UNIX (linux) flavor specifics.
Importing UNIX environment into LAX properties.
Checking for POSIX awk.

========= Analyzing LAX ==============================================
LAX found............................ OK.
LAX properties read.................. OK.

========= Finding VM =================================================
Valid VM types.......................... 1.6+ Absolute LAX_VM path.................... /tmp/install.dir.9880/Linux/resource/jre/bin/java
Expanded Valid VM types................. 1.6+ Found jvmspecs.properties

========= Virtual Machine Options ====================================
LAX properties incorporated............. OK.
classpath............................... "/tmp/install.dir.9880/InstallerData:/tmp/install.dir.9880/InstallerData/installer.zip"
main class.............................. "com.zerog.ia.installer.Main"
.lax file path.......................... "/tmp/install.dir.9880/temp.lax"
user directory.......................... "/tmp/install.dir.9880"
stdout to............................... "console"
sterr to................................ "console"
install directory....................... ""
JIT..................................... none option (verify)......................... off option (verbosity)...................... none option (garbage collection extent)...... none option (garbage collection thread)...... none option (native stack max size).......... none option (java stack max size)............ none option (java heap max size)............. 50331648 option (java heap initial size)......... 16777216 option (lax.nl.java.option.additional).. none

========= Display settings ===========================================
X display............................... not set UI mode................................. console

Launching installer...

========= VM Command Line ============================================
options: -Xmx50331648 -Xms16777216
CLASSPATH:/tmp/install.dir.9880/InstallerData:/tmp/install.dir.9880/InstallerData/installer.zip:

========= Forking JAVA =============================================
LAX Version = 18.0
____________________________________________________________________

InstallAnywhere 2017
Version: 18.0
____________________________________________________________________

 

XMLScriptReader: unable to parse the provided script file. File may have been invalid...
java.lang.NullPointerException
at Flexeraan9.am(Unknown Source)
at Flexeraan9.ak(Unknown Source)
at Flexeraan9$1.aa(Unknown Source)
at Flexeraais.ad(Unknown Source)
at Flexeraan9.ac(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.b1(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.a8(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.au(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.consoleInstallMain(Unknown Source)
at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source)
at com.zerog.ia.installer.Main.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source) Unable to load the script.

=======================================================

Installer User Interface Mode Not Supported

Unable to load and to prepare the installer in console or silent mode.

=======================================================

SHUTDOWN REQUESTED
(X) commiting registry
(X) shutting down service manager
(X) cleaning up temporary directories
System's temporary directory = /tmp
Exiting with exit code: 2000
cleanUp()
calling cleanUpUNIX()

5. Tried #unset DISPLAY, but the installer displayed the message above and exited without installing the SEM agent.

Security Event Manager

A bug in open JDK 1.8+ patches in 1.8.1.131 switched the font to STIX, which doesn't work well with the headless Java in OpenJDK.

Resolution/Workaround:

To resolve the issue, install JDK/JRE 1.8+ from Oracle software distribution (not the Open JDK ver), as this is the only JRE the SEM agent was tested against as of SEM 6.6

Starting with SEM 6.7 agents are supported with openJDK / JRE environments as well

If you have no choice or capacity to install/deploy Oracle JDK across all your Linux infrastructure and want to use OpenJDK for other reasons, see the work around for the Java font bug in 1.8 (© 2018 Micro Focus, available at https://community.softwaregrp.com, obtained on October 18, 2018).

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.