--- Mike Walker <[EMAIL PROTECTED]> wrote:
> However, if I run gstat -a I do get the data I would expect. But
> when I run anything with gmetric I get nothing (no errors no
> output....). Of course I might be doing gmetric wrong, so here is
> what I tried.
>
> 'gmetric -n mem_free -v mem_free -t uint32'
>
Mike,
this could be a real killer. Up to/including 3.0.2 "gmetad" has a bug
that will stop any host reporting metrics if a integer/floating typed
metric has a value that does not represent a number. Unfortunatelly
"gmetric" is not very picky about the strings that get passed via "-v".
The next release (3.0.3, no planned date) will have a fix that makes
gmetric check whether the "-v" string translates into a number.
In the meanwhile, you could try the following fix to gmetad:
--- rrd_helpers.c-orig 2006-01-25 16:14:16.000000000 +0100
+++ rrd_helpers.c 2006-01-25 16:10:27.000000000 +0100
@@ -54,7 +54,7 @@
{
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 );
If it fixes your problems, please report back.
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
