Eli,
OK, the messages coming from RRDTOOL, just telling that you tried to
update the same metric with exactely the same timestamp.
Do you see any messages prefixed "RRD_create" in your logfiles?
The problem is that if one of the rrd_updates fails, gmetad stops
working on anything.
Do you have a chance to rebuild gmetad with the following patch? It is
against current CVS, but should apply against 3.0.2. If it helps, all
hosts (metrics) except the one causing problems should be OK. It might
not be the real solution, but may help us to track it down.
[gmetad]$ diff -udp rrd_helpers.c rrd_helpers.c-new
--- rrd_helpers.c 2005-03-15 19:11:33.000000000 +0100
+++ rrd_helpers.c-new 2006-03-30 11:28:26.000000000 +0200
@@ -54,7 +54,7 @@ RRD_update( char *rrd, const char *sum,
{
err_msg("RRD_update (%s): %s", rrd, rrd_get_error());
pthread_mutex_unlock( &rrd_mutex );
- return 1;
+ return 0;
}
/* debug_msg("Updated rrd %s with value %s", rrd, val); */
pthread_mutex_unlock( &rrd_mutex );
In addition, do you see any messages prefixed "RRD_create" in your
logfiles? You should, as some of the RRD files seem to be missing.
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
