FusionReactor Observability & APM

Installation

Downloads

Quick Start for Java

Observability Agent

Ingesting Logs

System Requirements

Configure

On-Premise Quickstart

Cloud Quickstart

Application Naming

Tagging Metrics

Building Dashboards

Setting up Alerts

Troubleshoot

Performance Issues

Stability / Crashes

Low-level Debugging

Blog / Media

Blog

Videos / Webinars

Customers

Video Reviews

Reviews

Success Stories

About Us

Company

Careers

Contact

Contact support

Installation

Downloads

Quick Start for Java

Observability Agent

Ingesting Logs

System Requirements

Configure

On-Premise Quickstart

Cloud Quickstart

Application Naming

Tagging Metrics

Building Dashboards

Setting up Alerts

Troubleshoot

Performance Issues

Stability / Crashes

Debugging

Blog / Media

Blog

Videos / Webinars

Customers

Video Reviews

Reviews

Success Stories

About Us

Company

Careers

Contact

Contact support

[FRS-355] FusionReactor Production Debugger fails to start due to missing GLIBC_2.14

[FRS-355] FusionReactor Production Debugger fails to start due to missing GLIBC_2.14

UPD uses a native library to provide some of its features. UPDs native library requires GLIBC_2.14 to function.

Centos 6.x, Red Hat Enterprise Linux and other linux systems don’t provide this version. When it’s not available you will see error messages like this during startup :

$ sudo bin/catalina.sh run
Using CATALINA_BASE:   /opt/apache-tomcat-8.0.3
Using CATALINA_HOME:   /opt/apache-tomcat-8.0.3
Using CATALINA_TMPDIR: /opt/apache-tomcat-8.0.3/temp
Using JRE_HOME:        /usr
Using CLASSPATH:       /opt/apache-tomcat-8.0.3/bin/bootstrap.jar:/opt/apache-tomcat-8.0.3/bin/tomcat-juli.jar
Error occurred during initialization of VM
Could not find agent library /opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so in absolute path, with 
error: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so)

On CF servers this error information is redirected to /dev/null so its never seen but you could be hitting this error.

Check glibc version

To check the version of glibc on a linux system you can run one of the following:

# red hat / centos
rpm -q glibc

# debian / ubuntu
dpkg -l libc6

# via ldd
ldd --version

Workaround

To work around we have build a libc.so6 version 2.14.1 for uses on Centos (64 bit only) which must be explicitly loaded via the LD_PRELOAD variable

E.g. in tomcat you would set the following lines in the ‘setenv.sh’

export FR_OPTS="-javaagent:/opt/fusionreactor/instance/tomcat8/fusionreactor.jar=name=tomcat8,address=127.0.0.1:8088 -agentpath:/opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so"
export JAVA_OPTS="$JAVA_OPTS $FR_OPTS"

export LD_PRELOAD=/opt/fusionreactor/instance/tomcat8/libc.so.6

Disable the FusionReactor Production Debugger

You can disable the debugger completely by removing the

-agentpath:/opt/fusionreactor/instance/tomcat8/libfrjvmti_x64.so

argument from your application server. For Tomcat this is in setenv.sh and for CF servers its in the jvm.config.

Files

libc.so.6 – md5 checksum fa05af08d2993c478786a1f5b0335e1a


Issue Details

Type Technote
Issue Number FRS-355
Components UPD
Resolution Fixed
Last Updated 2019-11-27T12:19:37.645+0000
Affects Version(s) 6.0.0
Fix Version(s) 6.0.0
Platforms(s) Linux