--- Ben Hartshorne <[EMAIL PROTECTED]> wrote:
>
> Jan 24 17:24:18 localhost /usr/sbin/gmetad[30443]: RRD_update
> (/var/lib/ganglia/rrds/production/raiden-8-db1/users.rrd): conversion
> of
> 'min,' to float not complete: tail 'min,'
>
> This seems to relate to a recent change I made that I had forgotten
> about. :) I added the following line to my crontab:
>
> */2 * * * * /usr/bin/gmetric --name="users" --value=`w | head -1 |
> awk '{print $6}'` --type=int16
>
OK, as I discovered before, your command can put funny things like
"min," into the metrics stream. Unfortunatelly, gmetric or gmond are
stupid enough to handle that.
I can now kind of reproduce your problem by inserting the following
into the stream:
gmetric --name="users" --type=int16 --value="min,"
This appears then in both the gmond and gmetad XML. As a result, the
"report" graphs on my cluster view show the gaps. As soon as I insert a
number into the stream, the graphs work fine.
But - I only see the gaps in the cluster overview. The node displays
are not affected (both in the cluster overview and on the node pages).
Seems we need to make gmetric or gmond more robust against junk. Or we
need to see what the problem in the web interface is. Or both :-)
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
