2 Replies Latest reply on Sep 16, 2009 9:54 AM by j_ri

    Agent of 2.3.0 crashes



      this morning I upgraded from JOPR 2.2.1 to 2.3.0 (actually I didn't update, I did a new installation).

      unfortunately my agent is not running stable. Between 1 to 3 minutes after starting the agent (actually the jvm) crashes:

      # An unexpected error has been detected by HotSpot Virtual Machine:
      # SIGSEGV (0xb) at pc=0xe3ad8c37, pid=9418, tid=3823160208
      # Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)
      # Problematic frame:
      # C [libsigar-x86-linux.so+0x9c37] Java_org_hyperic_sigar_Cpu_gather+0x6b

      --------------- T H R E A D ---------------

      Current thread (0xe3197be0): JavaThread "ResourceContainer.invoker.daemon-1" daemon [_thread_in_native, id=9496]

      siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x30203048

      EAX=0x00000000, EBX=0xe3afd10c, ECX=0xe3e0b11c, EDX=0x00000000
      ESP=0xe3e0b104, EBP=0xe3e0b100, ESI=0xe3e0b1a4, EDI=0x30203020


      --------------- S Y S T E M ---------------

      OS:openSUSE 10.3 (X86-64)
      VERSION = 10.3

      uname:Linux #1 SMP 2008-06-09 13:53:20 +0200 x86_64
      libc:glibc 2.6.1 NPTL 2.6.1
      rlimit: STACK 8192k, CORE 0k, NPROC 16384, NOFILE 8192, AS 2884240k
      load average:0.60 0.55 0.54

      CPU:total 2 (cores per cpu 1, threads per core 1) family 15 model 6 stepping 8, cmov, cx8, fxsr, mmx, sse, sse2, sse3

      Memory: 4k page, physical 2063036k(15596k free), swap 1542200k(1542200k free)

      vm_info: Java HotSpot(TM) Server VM (1.5.0_11-b03) for linux-x86, built on Dec 15 2006 01:12:32 by java_re with gcc 3.2.1-7a (J2SE release)

      Any ideas where the problem is?


        • 1. Re: Agent of 2.3.0 crashes

          The crash is occurring in JNI code from SIGAR, the native library the Agent uses for process scans, system metrics, etc. I notice you are running an x86 JVM, but your system is x86_64. I would try with an x86_64 JVM instead. That will cause the x86_64 SIGAR shared library to be used, rather than the x86 one. I'd also recommend using a 1.6, rather than 1.5, JVM if possible. We'll probably be dropping support for 1.5 sometime in the not too distant future.

          • 2. Re: Agent of 2.3.0 crashes

            o.k., with a 64-bit JVM it seems to work.

            Thank you!