headers
Ed Ravin | 19 Aug 2010 17:29
Picon
Favicon

graph displays daily but not weekly/monthly/yearly stats

This is strange - starting last week, one of my Cricket graphs stopped
displaying data for the weekly/monthly/yearly graph.

The daily graph continues to show current data collected today.

But all the other graphs show a dropoff to zero at the day the problem
started.

I don't see any error messages in the Cricket logs, other than one
of the datasets being collected returns "U", but that's normal
for this setup, where the data is collected by a bunch of EXEC
scripts and some of the values aren't always available.

I dumped the RRD file out to XML and restored it, and just for laughs
I deleted the Cricket image cache, but nothing helped.  I do see
when looking at the RRD XML that all of the RRAs have recent values.

Any idea how to debug this further?

Thanks,

	-- Ed

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
(Continue reading)

Permalink | Reply | 5 comments |
headers
Kiss Gabor (Bitman | 19 Aug 2010 18:53
Picon

Re: graph displays daily but not weekly/monthly/yearly stats

> Any idea how to debug this further?

grapher.cgi, line 62:
$log = 'debug';

Then look for rrdtool command line in http server's error log.

Gabor

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
Permalink | Reply | 3 comments |
headers
Ed Ravin | 19 Aug 2010 20:03
Picon
Favicon

Re: graph displays daily but not weekly/monthly/yearly stats

On Thu, Aug 19, 2010 at 06:53:01PM +0200, Kiss Gabor (Bitman) wrote:
> > Any idea how to debug this further?
> 
> grapher.cgi, line 62:
> $log = 'debug';
> 
> Then look for rrdtool command line in http server's error log.

Here they are.  I don't see anything amiss with this.

[19-Aug-2010 13:44:41 ] RRDs::graph /tmp/cricket-cache/cricket-28a95e55.png -a PNG --base 1000
--start -151200 --vertical-label Delay --width 500 --height 200
DEF:ds0=/cricket/maillogs.rrd:ds2:AVERAGE DEF:ds1=/cricket/maillogs.rrd:ds3:AVERAGE
AREA:ds0#00cc00:average delay per message sent by Postfix LINE1:ds1#ff0000:standard deviation of
delay per message sent by Postfix VRULE:1282190400#ff0000: VRULE:1282104000#ff0000:
[19-Aug-2010 13:44:41 ] RRDs::graph /tmp/cricket-cache/cricket-387ac561.png -a PNG --base 1000
--start -41472000 --vertical-label Delay --width 500 --height 200
DEF:ds0=/cricket/maillogs.rrd:ds2:AVERAGE DEF:ds1=/cricket/maillogs.rrd:ds3:AVERAGE
AREA:ds0#00cc00:average delay per message sent by Postfix LINE1:ds1#ff0000:standard deviation of
delay per message sent by Postfix VRULE:1262318400#ff0000:
[19-Aug-2010 13:44:42 ] RRDs::graph /tmp/cricket-cache/cricket-80bb26e1.png -a PNG --base 1000
--start -3628800 --vertical-label Delay --width 500 --height 200
DEF:ds0=/cricket/maillogs.rrd:ds2:AVERAGE DEF:ds1=/cricket/maillogs.rrd:ds3:AVERAGE
AREA:ds0#00cc00:average delay per message sent by Postfix LINE1:ds1#ff0000:standard deviation of
delay per message sent by Postfix VRULE:1280635200#ff0000:
[19-Aug-2010 13:44:42 ] RRDs::graph /tmp/cricket-cache/cricket-ef141937.png -a PNG --base 1000
--start -864000 --vertical-label Delay --width 500 --height 200
DEF:ds0=/cricket/maillogs.rrd:ds2:AVERAGE DEF:ds1=/cricket/maillogs.rrd:ds3:AVERAGE
AREA:ds0#00cc00:average delay per message sent by Postfix LINE1:ds1#ff0000:standard deviation of
delay per message sent by Postfix VRULE:1281931200#ff0000:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kiss Gabor (Bitman | 19 Aug 2010 20:58
Picon

Re: graph displays daily but not weekly/monthly/yearly stats

> > Then look for rrdtool command line in http server's error log.
> 
> Here they are.  I don't see anything amiss with this.

Now you can issue the same rrdtool graph command by hand.
(Don't forget to quote args containing spaces.)
(The best to create a small shell script.)

Then "morph" the command line from the hourly graph to the daily one
with small modifications and look what happens. What small change
will result constant zero graph?

Gabor

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
Permalink | Reply | 0 comments |
headers
Franz Skale | 19 Aug 2010 21:21
Picon
Favicon

Re: graph displays daily but not weekly/monthly/yearly stats


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Be sure to check the cache file.
Check you cache files.
You defined /tmp/cricket-cache.
So, if deleting it, you must see new graphs generated due to rrdgraph.

Franz

Am 19.08.10 20:03, schrieb Ed Ravin:
> On Thu, Aug 19, 2010 at 06:53:01PM +0200, Kiss Gabor (Bitman)
> wrote:
>>> Any idea how to debug this further?
>>
>> grapher.cgi, line 62: $log = 'debug';
>>
>> Then look for rrdtool command line in http server's error log.
>
> Here they are.  I don't see anything amiss with this.
>
> [19-Aug-2010 13:44:41 ] RRDs::graph
> /tmp/cricket-cache/cricket-28a95e55.png -a PNG --base 1000 --start
> -151200 --vertical-label Delay --width 500 --height 200
> DEF:ds0=/cricket/maillogs.rrd:ds2:AVERAGE
> DEF:ds1=/cricket/maillogs.rrd:ds3:AVERAGE AREA:ds0#00cc00:average
> delay per message sent by Postfix LINE1:ds1#ff0000:standard
> deviation of delay per message sent by Postfix
> VRULE:1282190400#ff0000: VRULE:1282104000#ff0000: [19-Aug-2010
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ed Ravin | 24 Aug 2010 15:11
Picon
Favicon

Re: graph displays daily but not weekly/monthly/yearly stats

On Thu, Aug 19, 2010 at 11:29:00AM -0400, Ed Ravin wrote:
> This is strange - starting last week, one of my Cricket graphs stopped
> displaying data for the weekly/monthly/yearly graph.
> 
> The daily graph continues to show current data collected today.
> 
> But all the other graphs show a dropoff to zero at the day the problem
> started.
> 
> I don't see any error messages in the Cricket logs, other than one
> of the datasets being collected returns "U", but that's normal
> for this setup, where the data is collected by a bunch of EXEC
> scripts and some of the values aren't always available.
> 
> I dumped the RRD file out to XML and restored it, and just for laughs
> I deleted the Cricket image cache, but nothing helped.

Starting a day or so after I rebuilt the RRD file from XML, the weekly
graph now displays properly.  The monthly and yearly graphs still stop
at the same spot, now 12 days ago.

Perhaps they will catch up after a corresponding amount of time has passed?

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anders Synstad | 26 Aug 2010 16:17
Picon

Re: Cricket compile segfault

I finaly found the root cause for this segfault, and thought I'd share 
it with whomever wants.

The 'compile' script uses ConfigTree::Node, which again uses 
Text::ParseWords. In the parse_line sub, there is a regexp that is run 
on the value from the cricket config (my very long  mtargets (45000+ 
chars)).

On my system, this causes perl itself to segfault on variables larger 
than about 20680 chars. I'm sure this number may vary from machine to 
machine. It seems like at least this version of perl simply can't handle 
running regexps on such large variables.

On my machine I'm running and old perl 5.8.8 (I know, can't blame anyone 
when running an old perl), however, upgrading is not that simple in my case.

I did use a small proof-of-concept test script to verify and test the 
problem:

	#!/local/bin/perl

	$| = 1;

	use strict;
	use warnings;
	use Text::ParseWords;

	my $start	= 20000;
	my $step	= 100;
	my $max		= 100000;
(Continue reading)

Permalink | Reply | 0 comments |

Gmane