Author Topic: MSL -- Has anyone seen the following in the Messages file (/var/log)?  (Read 1197 times)

Offline bgodde

  • New Member
  • *
  • Posts: 1
  • Country: ca
  • Karma: +0/-0
    • View Profile
Sep 18 12:25:02 micollab2 crond mrtg: 2018-09-18 12:25:02, Rateup ERROR: /usr/bin/rateup found that eth0's log file time of 1537327202 was greater than now (1537287902)
Sep 18 12:25:02 micollab2 crond mrtg: ERROR: Let's not do the time warp, again. Logfile unchanged.
Sep 18 12:25:02 micollab2 crond mrtg: 2018-09-18 12:25:02, Rateup ERROR: /usr/bin/rateup found that memory's log file time of 1537327202 was greater than now (1537287902)
Sep 18 12:25:02 micollab2 crond mrtg: ERROR: Let's not do the time warp, again. Logfile unchanged.
Sep 18 12:25:02 micollab2 crond mrtg: 2018-09-18 12:25:02, Rateup ERROR: /usr/bin/rateup found that loadavg's log file time of 1537327202 was greater than now (1537287902)
Sep 18 12:25:02 micollab2 crond mrtg: ERROR: Let's not do the time warp, again. Logfile unchanged.


Offline Navarre

  • Jr. Member
  • **
  • Posts: 75
  • Karma: +0/-1
    • View Profile
Re: MSL -- Has anyone seen the following in the Messages file (/var/log)?
« Reply #1 on: September 18, 2018, 03:48:36 PM »
Yes. Your system clock went backwards.

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: MSL -- Has anyone seen the following in the Messages file (/var/log)?
« Reply #2 on: September 18, 2018, 06:39:44 PM »
Make sure that you have an NTP reference configured, and that the system is in sync. It should be a reasonably high stratum, preferably 4 or greater.


 

Sitemap 1 2 3 4 5 6 7 8 9 10