[rrd-users] Threshold checking problem
Matchan, Neil W
Neil.W.Matchan at team.telstra.com
Thu Jan 19 05:49:06 MET 2006
I've noticed that there have been other threads about this in the past
but they don't seem to document any solutions except for reverting back
to an earlier version of RRDTool.
I currently have two sites both running mrtg/rrdtool on a Redhat AS3
platform. The second site was built some 18 months after the first as a
Disaster Recover site.
Software Versions: (1st site)
MTRG 2.10.15, RRDTool 1.0.49
Software Versions: (DR site)
MRTG 2.12.2, RRDTool 1.2.11
The problem I'm having relates to 'threshold' processing and seems to be
related to (for what I've read in other threads) changes between the two
versions of RRDTool.
The RRDTool web site states that the format of the .rrd files has
changed and that 1.2.10 or later can read rrd files from earlier
versions but earlier versions of RRDTool can't read the new format rrd
data files. Ok, that makes sense.
The problem I'm having is thousands of the following messages being
logged on the RRDTool 1.2.11 site which do not occur on the older
RRDTool 1.0.49 site.
E.g. 2006-01-16 00:48:54 -- WARNING: can't do threshold checking for
target qcc2evers0101_se0_0_0(o) -- No valid current data
MRTG debug for the monitored device shows:
2006-01-19 10:11:47 -- --log: Called:
RRDs::tune(/var/www/html/rrdtool/edn/qcc2e
vers0101_fa0_0.rrd -a ds0:14375000 -a ds1:14375000 -d ds0:COUNTER -d
ds1:COUNTER
)
2006-01-19 10:11:47 -- --log: Calling:
RRDs::update(/var/www/html/rrdtool/edn/qc
c2evers0101_fa0_0.rrd, '1137625906:315079339893:517354880449')
2006-01-19 10:11:47 -- --log: Called: RRDs::last()
2006-01-19 10:11:47 -- --log: Called:
RRDs::fetch(/var/www/html/rrdtool/edn/qcc2
evers0101_fa0_0.rrd,'AVERAGE','-s',1137625906,'-e',1137625906)
2006-01-19 10:11:47 -- --log: got: NaN/NaN
2006-01-19 10:11:47 -- --log: Called:
RRDs::tune(/var/www/html/rrdtool/edn/qcc2e
vers0101_se0_0_0.rrd -a ds0:294400 -a ds1:294400 -d ds0:COUNTER -d
ds1:COUNTER)
2006-01-19 10:11:47 -- --log: Calling:
RRDs::update(/var/www/html/rrdtool/edn/qc
c2evers0101_se0_0_0.rrd, '1137625907:211241821:2879691546')
2006-01-19 10:11:47 -- --log: Called: RRDs::last()
2006-01-19 10:11:47 -- --log: Called:
RRDs::fetch(/var/www/html/rrdtool/edn/qcc2
evers0101_se0_0_0.rrd,'AVERAGE','-s',1137625907,'-e',1137625907)
2006-01-19 10:11:47 -- --log: got: NaN/NaN
2006-01-19 10:11:47 -- WARNING: can't do threshold checking for target
qcc2evers
0101_se0_0_0(o) -- No valid current data
2006-01-19 10:16:46 -- --log: Called:
RRDs::tune(/var/www/html/rrdtool/edn/qcc2e
vers0101_fa0_0.rrd -a ds0:14375000 -a ds1:14375000 -d ds0:COUNTER -d
ds1:COUNTER
)
2006-01-19 10:16:46 -- --log: Calling:
RRDs::update(/var/www/html/rrdtool/edn/qc
c2evers0101_fa0_0.rrd, '1137626206:315083600328:517384211874')
2006-01-19 10:16:46 -- --log: Called: RRDs::last()
2006-01-19 10:16:46 -- --log: Called:
RRDs::fetch(/var/www/html/rrdtool/edn/qcc2
evers0101_fa0_0.rrd,'AVERAGE','-s',1137626206,'-e',1137626206)
2006-01-19 10:16:46 -- --log: got: NaN/NaN
2006-01-19 10:16:46 -- --log: Called:
RRDs::tune(/var/www/html/rrdtool/edn/qcc2e
vers0101_se0_0_0.rrd -a ds0:294400 -a ds1:294400 -d ds0:COUNTER -d
ds1:COUNTER)
2006-01-19 10:16:46 -- --log: Calling:
RRDs::update(/var/www/html/rrdtool/edn/qc
c2evers0101_se0_0_0.rrd, '1137626206:239693926:2883775484')
2006-01-19 10:16:46 -- --log: Called: RRDs::last()
2006-01-19 10:16:46 -- --log: Called:
RRDs::fetch(/var/www/html/rrdtool/edn/qcc2
evers0101_se0_0_0.rrd,'AVERAGE','-s',1137626206,'-e',1137626206)
2006-01-19 10:16:46 -- --log: got: NaN/NaN
2006-01-19 10:16:46 -- WARNING: can't do threshold checking for target
qcc2evers
0101_se0_0_0(o) -- No valid current data
2006-01-19 10:21:47 -- --log: Called:
RRDs::tune(/var/www/html/rrdtool/edn/qcc2e
vers0101_fa0_0.rrd -a ds0:14375000 -a ds1:14375000 -d ds0:COUNTER -d
ds1:COUNTER
)
As stated in other threads, the RRDs::update and RRDs::fetch methods
both have the same time value but the RRDs::fetch returns no data
(NaN/Nan) which explains the 'No valid current data' error messages but
the next question is why the RRDs::fetch is returning NaN/Nan when an
RRDs::update was just done?
The rrd data files on the RRDTool 1.2.11 site were copied (using rsync)
from the RRDTool 1.0.49 site. Could it be a 'backward' compatibility
issue?
If this is a 'backward' compatibility issue, are there any utilities I
can use against the older RRDTool 1.0.49 rrd data files to migrate them
to the new format?
If not any of the above, any suggestions?
Thanking the group in advance,
Neil M
--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive http://lists.ee.ethz.ch/rrd-users
WebAdmin http://lists.ee.ethz.ch/lsg2.cgi
More information about the rrd-users
mailing list