Linux MID Server startup error failed to resolve the version of Java


Description

Linux MID Server fails to start.

Cause

The JRE used by the MID Server is not supported in the current operating system environment.

To check the JRE version:

  1. Navigate to <agent/jre/bin>
  2. Run command: java -version

If an error is returned, the JRE is likely not supported by the OS. Example error:

Glibc_2.14 not found required by libjli.so
As an example from the Quebec MID Server System Requirements docs page:
Upgraded MID Servers might use different Java versions depending on their operating system versions.

MID Servers upgraded from earlier versions use the OpenJDK provided with the MID Server installer. This version of the OpenJDK was tested and certified for use with these MID Servers.

The JRE version is not upgraded when upgrading 32-bit Linux MID Servers or Linux with glibC versions lower than 2.17. The MID Server will continue to use earlier the earlier version of JRE, such as 1.8.0_231.

MID Servers upgraded on any other operating system versions also automatically upgrade the JRE to the version provided with the installation package.

Note: Linux MID Servers require glibC version 2.17. The library must be updated for JRE 11. On 64-bit Linux systems, you must install the 32-bit GNU C library (glibc). The installation command for CentOS is: yum install glibc.i686
From the above, the auto upgrade process tries to keep a JRE which is supported. However, in some cases customer may need to download the new MID server files and include JREs which are not supported with the OS. In such cases, this situation may happen and the MID server may fail to start. If MID servers cannot be auto upgraded, follow the steps in the resolution once the new MID server is installed.

Resolution

  1. First, find your version of the "MID Server System Requirements" documentation page:
  2. Check what JRE version is supported by both the MID server and your operating system
  3. Using the JRE vendor's own instructions, Install the JRE in the normal way but be sure to install it outside of the MID Server's "agent" install folder. MID Server upgrades can replace anything included within the agent folder, and do regularly delete and replace everything in the bundled JRE's agent/jre/ folder.
  4. Edit the agent/conf/wrapper-override.conf file to tell the MID Server to use the newly installed external JRE.
  5. Example JRE configuration:
    ################################################################################
    # External JRE
    ################################################################################
    # Uncomment and edit if an external JRE is preferred. By default,
    # the internal JRE distribution is used.
    #
    # OPTIONAL: The path (relative to agent dir or absolute) to the java bin
    wrapper.java.command=C:\ServiceNow_MID_Servers\OpenJDK\8u251\jre\bin\java

Note: the JRE cacerts will need to have the certificates imported if the MID server connects to the instance via a proxy, or any equipment which does packet deep inspection (basically a device in the middle which decrypts the traffic and re-encrypts it before sending it back to the instance). For more information see following document.

Warnings:

Additional Information