On Tue, Aug 05, 2008 at 05:37:20PM -0700, Bernard Li wrote:
> 
> Is this a bug?

not sure how else can we call a gmetad segfaulting.

in this case the code that is breaking is part of libganglia's
hash_lookup (hash.c) function while doing :

  READ_LOCK(hash, i);

when hash is a NULL pointer because "EXTRA_ELEMENT" wasn't handled correctly
as shown by :

#0  0x00007ffec0f82520 in hash_lookup (key=0x43e3d820, hash=0x0) at hash.c:304
#1  0x0000000000405860 in startElement_EXTRA_ELEMENT (data=0x43e3dbf0, 
    el=<value optimized out>, attr=0x61ed10) at process_xml.c:731
#2  0x0000000000405e4c in start (data=0x43e3dbf0, el=0x61cd6c "EXTRA_ELEMENT", 
    attr=0x61ed10) at process_xml.c:1010

a quick workaround that just drops the extra elements at summarization
Committed revision 1631 for trunk, so that a hierarchical 3.1.0 setup can
be done (which I presume no one tested during the year long testing cycle)
otherwise this basically means 3.1.0 is useless in a hierarchical setup (with
more than 1 gmetad)

Carlo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to