|
This is a known problem caused by a race condition in MRTG.
If a graph is built from multiple RRD files, which update at different times, you will get a period of between 0s and 5min during which the 'current' value for some of the components will be zero. The 'current' value is not the same as the 'last' value!
EG, if you update at 12:04:59, right at the end of the 5min window, then between 12:00 and 12:04:58, then 'current' value is unknown (the 'last' value is the one you submitted some time between 11:55:00 and 11:59:59).
Routers2 tries to work around this but cannot always do so, particularly when several different RRD files are being combined into a graph.
Another workaround is to have 'uselastupdate = yes' in your Routers2.conf which bases graphs on the last update time, not on the current time.
_________________ Steve Shipway UNIX Systems, ITSS, University of Auckland, NZ Woe unto them that rise up early in the morning... -- Isaiah 5:11
|