Red Hat Bugzilla – Bug 870186
Agent loads Sigar with nonative flag activated
Last modified: 2015-02-01 18:28:28 EST
+++ This bug was initially created as a clone of Bug #869730 +++
Description of problem:
Agent loads the Sigar library with nonative flag activated. This leads to errors agent startup failure in cases where the Sigar library is not compatible with the operating system.
Steps to Reproduce:
1. Use a system that is not compatible with Sigar (eg. SUSE 10.1)
2. Run the agent with --nonative flag
3. Notice error
Failure to start with the following error:
# A fatal error has been detected by the Java Runtime Environment:
# SIGFPE (0x8) at pc=0x00002b592b3d668f, pid=13696, tid=1074792768
# JRE version: 7.0_07-b10
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.3-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [ld-linux-x86-64.so.2+0x868f] do_lookup_x+0xcf
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
The agent starts without Sigar loaded
This issue has been observed on Suse 10.x 64bit. This version of Suse is running an older glibc library (2.4.x) that should be compatible with Sigar but it is throwing SIGPFE excetion at startup.
The main problem is that --nonative flag is not working properly as it should have prevented the loading of Sigar jars completely.
This is fixed in master, pushing to MODIFIED
As this is MODIFIED or ON_QA, setting milestone to ER1.
Created attachment 817037 [details]
checked under Suse 11 (latest) and rhel 4 - no exceptions in agent.log, agent discovered and active in server gui.