Re: Make cricket update RRD file with a realtimestampinstead of "N"

Have you actually checked all 75,000 files?  I naturally had not checked
all 45,000 of my files.  But when it was brought to my attention that a
graph was empty I started looking.  I wrote this crude little perl
script to identify files that were empty:

while (<STDIN>) {

        chomp;
        my $rrd_file = $_;
        my $info = RRDs::info("$rrd_file");
        my @array = keys %{$info};
        my $counter = 0;
        while (@array) {
                my $entry = shift @array;
                if ($entry =~ /value/) {
                        if (defined $$info{$entry}) {
                                $counter++;
                        }
                }
        }
        if ( $counter == 0 ) {
                print "$rrd_file\n";
        }

}

There weren't many.

There are no errors in any cricket files.  My recollection from last
week was that a manual rrdtool update of the file using a timestamp
resulted in data in the file.  My experience this morning however tells
me this is not so.

I had updated the cricket code use the timestamp, but it is not making a
difference.

I think I need to move this discussion to the rrd-users mailing list.

Thanks.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Marc
Powell
Sent: Friday, January 05, 2007 11:28 AM
To: [email protected]
Subject: Re: [cricket-users] Make cricket update RRD file with a
realtimestampinstead of "N"



> -----Original Message-----
> From: [email protected]
[mailto:cricket-users-
> [email protected]] On Behalf Of Ruttenberg, Tanya
> Sent: Friday, January 05, 2007 9:41 AM
> To: [email protected]
> Subject: [cricket-users] Make cricket update RRD file with a real 
> timestampinstead of "N"
> 
> I just noticed an issue whereby cricket is retrieving data (SNMP
stats)
> and updating the rrd file only to find that the rrd file is full of
> NaN's.   From what I've read, this problem can sometimes be alleviated
> if the updates are done with an explicit timestamp instead.

I've never seen any timestamp issues updating 75,000+ rrd files every 5
minutes for the past 5 years. It seems more likely to me that you're
going down a wrong path. What makes you think it's a timestamp issue?
Are you updating with the correct number of DS's that the rrd file is
expecting? That's always been the issue for me when I have NANs. Have
you run the collector in debug mode/checked the logs for specific errors
from cricket/rrdtool?

--
Marc

------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
cricket-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cricket-users

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV