Hi Jason,
Note that the timestamps are the same.
when this error occurs on the summary graphs, but not host graphs, check
whether 2 clusters have the
same cluster name. Note that the cluster names are not defined by that
string on the data_source, it comes
from the gmond.conf of the host mentioned for the data_source ni
gmetad.conf.
If you also get this error on host rrd files too, then you may be
including the same cluster twice in gmetad.conf.
If you get errors just on a single host, there may be an error in
reverse dns entries (gmond does a reverse lookup
to see where a ganglia packet comes from).
In all cases, do a "nc ganglia-server-host 8651". Check whether whether
cluster names or host names occur
more than once. If they do, you have something to fi.
kind regards,
Richard Grevis
Production Architecture
Barclays Capital, Canary Wharf, London, E14 4BB
*DDI : +44 (0) 20 7773 4915
* richard.grevis
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jason Faulkner
Sent: 04 January 2007 04:16
To: [EMAIL PROTECTED]; [email protected]
Subject: Re: [Ganglia-general] "Compatibility mode" for gmetad?
Martin Knoblauch wrote:
--- Jason Faulkner <[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED]> wrote:
I'm curious about how "possible" or difficult it
would be to make
gmetad
backwards compatible -- i.e. where I could leave
my 2.5.x gmond
installations alone, and install 3.x gmetad on
my main server (and be
able to collect stats despite having a
heterogeneous 2.5.x and 3.x
environment). This would allow me to (hopefully)
live-migrate my
ganglia
install up to the new version.
--
Jason Faulkner
Systems Manager
Broadwick Corporation
(919) 459-2509
Hi Jason,
although we bumped the major number in the 2.5.x -> 3.0
transition, we
took care to not introduce incompatible changes to the
core metrics
framework. In short, I see no reason why a 3.0.4 gmetad
should not be
able to query 2.5.x gmond data.
It should even be possible to have a 3.0.4 gmond listen
to older
gmonds. Of course, you are limited to multicast until
you have replaced
all gmonds.
Jan 3 23:12:07 intranet1 ./gmetad[25006]: RRD_update
(/var/lib/ganglia/rrds/Dev Login
Servers/__SummaryInfo__/part_max_used.rrd): illegal attempt to update
using time 1167883927 when last update time is 1167883927 (minimum one
second step)
I've been receiving repeated errors like this attempting to use
a 3.0.x gmetad with a 2.5.7 gmond. The times are synced perfectly to a
local NTP server, so I'm sure that's not the issue.
--
Jason Faulkner
Systems Manager
Broadwick Corporation
(919) 459-2509
[EMAIL PROTECTED]
------------------------------------------------------------------------
For more information about Barclays Capital, please visit our web site at
http://www.barcap.com.
Internet communications are not secure and therefore the Barclays Group does
not accept legal responsibility for the contents of this message. Although the
Barclays Group operates anti-virus programmes, it does not accept
responsibility for any damage whatsoever that is caused by viruses being
passed. Any views or opinions presented are solely those of the author and do
not necessarily represent those of the Barclays Group. Replies to this email
may be monitored by the Barclays Group for operational or business reasons.
------------------------------------------------------------------------
