How to correct mrtg going berserk?
Mark
admin at asarian-host.net
Tue Oct 28 14:48:37 PST 2003
Mrtg has gone berserk on me; apparently they have never heard of clocks
being adjusted because of Daylight Savings:
-------------------------------------
Rateup ERROR: /usr/local/bin/rateup found that 192.168.0.1_1's log file time
of 1067382961 was greater than now (1067380560)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Rateup ERROR: /usr/local/bin/rateup found that localhost.cpu's log file time
of 1067382961 was greater than now (1067380560)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Rateup ERROR: /usr/local/bin/rateup found that memory's log file time of
1067382963 was greater than now (1067380562)
ERROR: Let's not do the time warp, again. Logfile unchanged.
Rateup ERROR: /usr/local/bin/rateup found that swap_memory's log file time
of 1067382963 was greater than now (1067380562)
ERROR: Let's not do the time warp, again. Logfile unchanged.
-------------------------------------
Manually changing the log-times back does not help either. Does anyone know
how to correct it?
Thanks,
- Mark
More information about the freebsd-questions
mailing list