Hi Mike,

you have setup an rrd file covering the next 5000 years ...
this may be triggering all sorts of interseting overflows ...

it me be that this particular problem is fixed in a later 1.2.x
release, but in general you can not relie on sensible behaviour
from rrdtool for times outside the 32bit unix time range ...

in 1.4.x I will address this problem together with the update of
the database format ...

cheers
tobi

Saturday Mike Schilli wrote:

> I'm getting a core dump with rrdtool 1.2.19 when graphing data with
> large step sizes (1 year). Here's the commands to reproduce it:
>
>     rrdtool create myrrdfile.rrd --step 31536000 \
>      DS:money:GAUGE:63072000:U:U \
>      RRA:MAX:0.5:1:5000
>
>     rrdtool update myrrdfile.rrd 1311653013:100000
>
>     rrdtool graph mygraph.png --end 1369419413 --start 1211653003 \
>     DEF:draw1=myrrdfile.rrd:money:MAX "AREA:draw1#0000FF:Example"
>
> Stacktrace:
>
> ======= Backtrace: =========
> /lib/tls/i686/cmov/libc.so.6[0xb7d70d65]
> /lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb7d74800]
> /usr/lib/librrd.so.2(rrd_free+0x24)[0xb7ed5aa4]
> /usr/lib/librrd.so.2(rrd_fetch_fn+0x607)[0xb7eb86c7]
> /usr/lib/librrd.so.2(data_fetch+0x21b)[0xb7ebed8b]
> /usr/lib/librrd.so.2(graph_paint+0x44)[0xb7ebffa4]
> /usr/lib/librrd.so.2(rrd_graph+0x121)[0xb7ec2051]
> /usr/lib/librrd.so.2(HandleInputLine+0x10db)[0xb7ed140b]
> /usr/lib/librrd.so.2(main+0x92)[0xb7ed15e2]
> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7d1d050]
> /usr/bin/rrdtool(main+0x3d)[0x8048401]
>
> Is this something that has been fixed in later versions?
>
> -- Mike
>
> Mike Schilli
> [EMAIL PROTECTED]
>
> _______________________________________________
> rrd-users mailing list
> [email protected]
> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
>
>

-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch [EMAIL PROTECTED] ++41 62 213 9902

_______________________________________________
rrd-users mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users

Reply via email to