Two things to check before concluding it's the code (though I think
your points are valid):
If you have a data source that's misconfigured, with a cluster name
that matches a different data source, you'll get this problem, but
only on __SummaryInfo__ files.
If you have a 3.0 system, and the
+1; we patched like that, too, and monitor the same way.
-- ReC
On Sep 11, 2009, at 6:43 AM, Spike Spiegel wrote:
> Hi,
>
> recently we added better monitoring for our ganglia infrastructure and
> one of the checks for gmetad contacts it on port 8651, looks for some
> XML string and exits (receiv
Hi,
recently we added better monitoring for our ganglia infrastructure and
one of the checks for gmetad contacts it on port 8651, looks for some
XML string and exits (receiving 20+ MBs of xml every time we run the
check isn't an option). The 'exists' part means sending a RST before
gmetad has sent
Hi,
our gmetad boxes (2 of them) with 12 data sources, 6 of which are
gmetad and 6 gmonds, are spamming syslog like mad with the following
message:
Sep 6 06:33:32 localhost.localdomain /usr/sbin/gmetad[2526]:
RRD_update (/var/lib/ganglia/rrds/...metric.rrd): illegal attempt to
update using time
If anyone is interested in testing the Ganglia build on the OpenCSW
build farm, it is now possible. This provides access to a range of
Solaris machines including version 8.
libconfuse is now packaged and pre-installed on the OpenCSW machines, so
all the dependencies for building Ganglia are t