search cancel

Upgrading to 6.7 result in error version `GLIBC_2.14' not found


Article ID: 201039


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


Upgrading to RA version 6.7 results in below error

-bash-4.1$ ./
Unpacking JRE ...
Starting Installer ...
Oct 08, 2020 11:38:35 AM java.util.prefs.FileSystemPreferences$2 run
INFO: Created system preferences directory in java.home.
java.lang.UnsatisfiedLinkError: /var/opt/data/CA/ReleaseAutomationServer/ /lib64/ version `GLIBC_2.14' not found (required by /var/opt/data/CA/ReleaseAutomationServer/
        at java.lang.ClassLoader$NativeLibrary.load(Native Method)
        at java.lang.ClassLoader.loadLibrary0(
        at com.install4j.runtime.launcher.Launcher.main(Unknown Source)
Could not display the GUI. This application needs access to an X Server.
You can also run this application in console mode without
access to an X server by passing the argument -c


Release : 6.7



The reason for above error is due to the fact that some of the system requirements for RA version 6.7 are not met. The details of same are provided below.

1: System Requirements: Platform Support

For example a user running RHEL 6.10 which is not supported by RA 6.7 GA and RHEL 7.6 or higher is must, due to the limitation of bundled JRE( by AdoptJDK) with product.

Please find more details below.

From Product Perspective

Linux Servers

    • In general, any other Linux distributions that have a minimum glibc version 2.12 on x86 or version glibc version 2.17 on other architectures are expected to function without problems.

RHEL Specific

    • "We certified RHEL 8.1 in cumulative of 6.7.1(release notes) .We do not have plans to certify older versions of RHEL like 7.6 on 6.7." as they are near to be end of support from RHEL (RHEL Life cycle phase


  • Note: Linux version and glibc version on Linux based system can be validate with below command
#Linux version details
cat /proc/version
# GLIBC details
ldd --version


From Support Perspective

We are using AdoptOpenJDK from 6.7 onward, which list support RHEL 6.9 X64 Architecture, RHEL 7.4, RHEL 8 and any other Linux distributions that have a minimum glibc version 2.12 on x86, 2.23 on aarch32 and 2.17 on other architectures are expected to function without problems.

More details about supported platform by AdoptOpenJDK can be referred at AdoptOpenJDK supported platforms

  • Limitation: In some case if there is an issue identified in JRE and on specific platform not supported by Adopt, we will not be feasible and viable to take responsibility of full JRE and have to wait for Adopt to provide fix for JRE, if viable for them".  So we still go with our Linux Compatibility as below.

Linux Compatibility Statement

Release Automation has tested its products on the Red Hat versions of Linux. Release Automation will assist running its products on other Linux distributions in the following manner: 

    • Release Automation will provide support for issues that are known to occur on Linux Validated Environments or that can be shown to occur on one of the Linux Validated Environment.
    • If the issue is a known Release Automation issue we will recommend the appropriate solution (configuration, patch, etc.).
    • If the issue is reproduced on a Linux Validated Environment Release Automation Customer Service will provide support and open a corrective update request with Release Automation Development if required.
    • If the issue cannot be reproduced on Linux Validated Environment the customer will need to get further assistance from the Linux distribution provider.
    • Release Automation will validate solutions to issues on Linux Validated Environment only. This will in most cases work on the non-validated Linux distributions that exhibit the same issue but that outcome is not guaranteed.
    • Linux validated Environment means Red Hat Enterprise Linux (RHEL)


In case if OS is unsupported please try to upgrade OS to supported platform(as it should be bundled with correct GLIBC version). An alternative can be to patch/upgrade the GLIBC on the current OS (please take care upgrading GLIBC may cause error for applications dependent on specific version(old) of GLIBC)