[rrd-users] Re: Problems with multi-DS RRD that gets asynchronous-DS updates

[Alex van den Bogaerdt]

> 
>  > > From: me
>  > > [...]
>  > > Then at 1999-09-16 12:45:00 CDT, it did snmpgets across
>  > > a second boundary so my script stuffed values into rrd via:
>  > > 
>  > >   rrdtool update MadisonSD.rrd -t input 937503900:496053104
>  > >   rrdtool update MadisonSD.rrd -t output 937503901:108120595
>  > > 
>  > > I expect the value of the DS output at 1999-09-16 12:45:00 CDT to be
>  > > 1.058e+04 = (108120595 - 104956107) / 300.
>  > > 
>  > > But instead I get NaN:
>  > > 
>  > >   <!-- 1999-09-16 12:45:00 CDT --> <row><v> 6.7762683333e+04 </v> \
>  > >     <v> NaN </v></row>
>  > > [...]
>  
>  > From: Alex van den Bogaerdt
>  > This means that your RRD doesn't allow for updates more than 300
>  > seconds apart. Check your heartbeat settings, I bet they are 300.
> 
> I comtemplated that idea... but I have minimal_heartbeat set

Argh, lost that bet :-)

Been thinking about it for a while. What could happen is that
rrd writes an unknown at time=937503900, verify by dumping the database
inbetween 937503900 and 937503901.

You are allowing updates to come once a day, however rrdtool will try
and create a datapoint when it can (and if I'm right this time, it can).

Perhaps updating at 937503899 and 937503900 will do the trick ?

Regards,
Alex

--
* To unsubscribe from the rrd-users mailing list, send a message with the
  subject: unsubscribe to rrd-users-request at list.ee.ethz.ch