|
To fix the 'current = zero' problem, get the latest version of routers2. There is a potential race condition between the update and the display that sometimes can cause the last read value to be 'unknown' as it falls into a different time slot. ALternatively, enable the 'uselastupdate' option in the routers2.conf.
Im not sure about your main problem, sounds like a conflict between either your .cfg file, your .rrd file, and your gathering process. Do you use a periodic scheduled job to collect the data, or do you use mrtg in daemon mode? If the former, make sure you are running it every minute! If the latter, make sure you are not mixing 1min and 5min interval targets in a master.cfg file. Have a separate instance of mrtg for different interval targets.
_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11
|
Login
Register
FAQ
Members
