Your message dated Thu, 23 Oct 2008 18:55:25 +0600
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
has caused the Debian Bug report #503196,
regarding rrdtool: Plots wrong data with -A -Y options
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
503196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503196
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: rrdtool
Version: 1.3.1-4
Severity: grave
Justification: causes non-serious data loss
First, create a round-robin database that will hold our test data.
rrdtool create testdata.rrd --start 1224453000 --step 1800 \
DS:testdata:GAUGE:28000:0:U RRA:LAST:0.5:1:1800
Then, populate it with numbers:
rrdtool update testdata.rrd 1224453300:1350535
rrdtool update testdata.rrd 1224467700:1350545
rrdtool update testdata.rrd 1224482100:1350554
rrdtool update testdata.rrd 1224496500:1350560
rrdtool update testdata.rrd 1224514800:1350562
rrdtool update testdata.rrd 1224539700:1350562
rrdtool update testdata.rrd 1224557700:1350562
rrdtool update testdata.rrd 1224576000:1350562
rrdtool update testdata.rrd 1224590100:1350562
rrdtool update testdata.rrd 1224604800:1350562
rrdtool update testdata.rrd 1224622500:1350562
rrdtool update testdata.rrd 1224636900:1350562
rrdtool update testdata.rrd 1224651300:1350562
rrdtool update testdata.rrd 1224669300:1350562
rrdtool update testdata.rrd 1224683700:1350562
rrdtool update testdata.rrd 1224698100:1350562
rrdtool update testdata.rrd 1224712500:1350562
rrdtool update testdata.rrd 1224730500:1350562
rrdtool update testdata.rrd 1224744900:1350562
Let's plot it:
rrdtool graph testdata.png -t testdata --start 1224453000 --end 1224757634 \
DEF:testdata=testdata.rrd:testdata:LAST 'LINE2:testdata#ff0000'
Result (correct):
http://lh4.ggpht.com/patrakov/SQBmKaXKPtI/AAAAAAAAAOc/O8iAIBxWbw4/s800/testdata.png
Indeed, there is not much change. But let's suppose that we are really
interested in the small change that happened over the week. Let's use
the alternative autoscaling option that, according to the manual page,
is designed specifically for such cases:
rrdtool graph testdata-bug.png -t testdata --start 1224453000 --end 1224757634 \
-A -Y DEF:testdata=testdata.rrd:testdata:LAST 'LINE2:testdata#ff0000'
Result (wrong):
http://lh4.ggpht.com/patrakov/SQBmKohptyI/AAAAAAAAAOk/29p6b-TuuJw/s800/testdata-bug.png
The buggy image says that testdata is about 35000M, while it is
actually at 1.35M. Misleading plot = data loss.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.CP1251, LC_CTYPE=ru_RU.CP1251 (charmap=CP1251)
Shell: /bin/sh linked to /bin/bash
Versions of packages rrdtool depends on:
ii libc6 2.7-14 GNU C Library: Shared libraries
ii libfontconfig1 2.6.0-1 generic font configuration library
ii libpixman-1-0 0.10.0-2 pixel-manipulation library for X a
ii libpng12-0 1.2.27-2 PNG library - runtime
ii librrd4 1.3.1-4 Time-series data storage and displ
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxcb-render-util0 0.2.1+git1-1 utility libraries for X C Binding
ii libxcb-render0 1.1-1.1 X C Binding, render extension
ii libxcb1 1.1-1.1 X C Binding
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
rrdtool recommends no packages.
Versions of packages rrdtool suggests:
pn librrds-perl <none> (no description available)
-- no debconf information
--
Alexander E. Patrakov
--- End Message ---
--- Begin Message ---
I should have used the -L 10 option. The manual page warns about that,
although it would be really nice if rrdtool marked the chopped-off
strings somehow. Even Excel's "###" is better.
--
Alexander E. Patrakov
--- End Message ---
