rhq-agent keep crashing
mazz at redhat.com
Thu Jun 24 16:20:43 UTC 2010
Things like this are due to bugs/problems in the third-party native
SIGAR library used by the agent. It is attempting to scan the operating
system's process table to try to discover resources and for some reason,
its crashing with a segfault, taking down the entire VM with it.
Is the operating system something "special" (a special build of some
sort) or is there anything out of the ordinary with the platform? Is
this a virtual OS?
You can turn off the native library usage by passing the command line
argument --nonative to the agent, just to get your agent going again.
You'd lose some capabilities (since SIGAR is used to collect native
metrics for some things and to do auto-discovery of some resources) but
the agent will retain most of its features.
On 06/24/2010 11:05 AM, Henon Guillaume wrote:
> I have installed rhq-server-3.0.0.B05 and server is working fine.
> Now I have also installed an agent but it keeps crashing, before having
> discovered any targets.
> The hs_err file shows the following
> # A fatal error has been detected by the Java Runtime Environment:
> # SIGSEGV (0xb) at pc=0x00c8001c, pid=27794, tid=2800745360
> # JRE version: 6.0_20-b02
> # Java VM: Java HotSpot(TM) Server VM (16.3-b01 mixed mode linux-x86 )
> # Problematic frame:
> # C [libc.so.6+0x6801c]
> --------------- T H R E A D ---------------
> Current thread (0xa632c800): JavaThread "InventoryManager.discovery-1"
> daemon [
> _thread_in_native, id=28634, stack(0xa6eaf000,0xa6f00000)]
> siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR),
> And last entry in agent.log is
> 2010-06-24 16:52:39,501 INFO [InventoryManager.discovery-1]
> ory.AutoDiscoveryExecutor)- Process scan auto-detected new server
> resource: scan
> ], name=[JBoss4]], discovered-process=[process: pid=,
> name=[java], ppid=[
> I'm running agent and server on the same host : linux redhat 5 32b.
> 2.6.18-53.el5xen #1 SMP Wed Oct 10 17:06:12 EDT 2007 i686 i686 i386
> Can somebody help me on that issue ? I had the same problem with
> rhq-users mailing list
> rhq-users at lists.fedorahosted.org
More information about the rhq-users