[mrtg] Re: amazing error
Paul C. Williamson
pwilliamson at mandtbank.com
Mon Dec 31 14:39:33 MET 2001
It sounds like you've got one of two problems.
Time changed on the MRTG box. Either you changed it
or ntp changed it. But, ntp would die if it tried to update
something that was that far off. Maybe ntpdate ran and
updated your time?
Two copies of MRTG running. Stop
all instances of MRTG, restart one, and make sure it runs for
at least 10 minutes to see if the error comes back. Make
sure that 192.168.150.60_257.log and 192.168.150.60_257.old
are gone *after* you stop MRTG.
>>> "zeeshan ahmed" <zeshann at worldcall.net.pk> 12/31/01 07:24AM >>>
Hello guys, i have been using MRTG for last two months every thing was running smmotly but today soime hting strange thing happened i was getting following error when i start my mrtg for nay cfg file.
ERROR: let's not do the time wrap, again. Logfile unchanged
Rateup error: /usr/local/src/mrtg-2.9.17/bin/rateup found that 192.168.150.60_257 log file time of 1009770968 was greater than now (1007208922)
i did remove all the log and old file but no use.
please tell me whats the problem
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
More information about the mrtg