[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] strange graph behavior - random machines & graphs
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] strange graph behavior - random machines & graphs
- From: "Gary Baluha" <gumby3203 (at) gmail.com>
- Date: Wed, 5 Dec 2007 11:53:26 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=sJB9IPk02asOMWnGwLeKl8U+m9v7NJPqHh57ydrkows=; b=jEmyO8W6uFoX8Nd9HnsgzpckbYEhcskjMLU4w/YTXp0yhXjYvEQe+WrCwDSQhJ9pvJ1jeQWozRQAkuGgClma89NftcMGT68D0qoCdQDIsA1zXwhC/usJkASBfXgclWyM/nU5YtFm92vwyNgSRwWRCOzQMcov5GSMyI1+JEVBOK4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=igbcHL8dAx5PKCa4ZXocijyTUEtBOSKyrO1d3v598qtwmYkMxtaqQRMDgOTRdVPoO7vxrTkBlhsRE1jRNe+4fUWN4iv8p8KFIy5eWfgZaabR+jB11psI9djJ8ttpYRz9YYvGvCE1/gUOaUMLEGXnugUs2CS6r6AWG4TRZrFBzEM=
- References: <29f517690711280656x5c9fa38cta0e80f0d5761c1f7 (at) mail.gmail.com> <58EF0861D3A1A04182720B3A5231C7C201E022DB (at) usplm205.amer.corp.eds.com> <29f517690711300814q7a1ef9bew600c2d02d2d4de29 (at) mail.gmail.com> <58EF0861D3A1A04182720B3A5231C7C201E38CA9 (at) usplm205.amer.corp.eds.com> <29f517690711301031r110fa494mbf1a5c084971bd42 (at) mail.gmail.com> <58EF0861D3A1A04182720B3A5231C7C201E38D5D (at) usplm205.amer.corp.eds.com> <29f517690711301114g47a9ee50h423a64693d56c289 (at) mail.gmail.com> <29f517690711301207u10f9d59dh70a39c33962cf3d8 (at) mail.gmail.com> <29f517690712031055n6c22d430wb684610a727172dc (at) mail.gmail.com> <961092e10712031106k43c777abrf106e8d285ea0cd8 (at) mail.gmail.com>
I am now completely convinced that the strange behavior of the graphs is due
to some bad data getting inserted into the .rrd database files. The bad
data is always the same value: 5.1776682516e+170. That's what the value
looks like when you do an rrddump on the .rrd database file.
I still have no idea where this value is coming from, but I have at least
determined how to fix these graphs. I'm working on a script to do this, but
for now, I manually do an rrddump of the file, change all bogus values to
NaN (basically, searching for "e+1", since none of the values I trend
generally get that large, so I know these entries are just averaged values
of correct data and the 5.17... number), and then do an rrdrestore from the
modified xml file.
It would be nice to determine where this problem is coming from, though.