The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Whats this?

Discussion in 'General Discussion' started by sexy_guy, May 10, 2003.

  1. sexy_guy

    sexy_guy Well-Known Member

    Joined:
    Mar 19, 2003
    Messages:
    848
    Likes Received:
    0
    Trophy Points:
    16
    Rateup ERROR: /usr/bin/rateup found that mail's log file time of 1052558105 was greater than now (1052558103)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that mailbytes's log file time of 1052558107 was greater than now (1052558105)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that spam's log file time of 1052558108 was greater than now (1052558106)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that loadavg's log file time of 1052558108 was greater than now (1052558106)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that sendmail's log file time of 1052558109 was greater than now (1052558107)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that mailscanner's log file time of 1052558109 was greater than now (1052558107)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that outqueue's log file time of 1052558109 was greater than now (1052558107)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that inqueue's log file time of 1052558109 was greater than now (1052558107)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that memory's log file time of 1052558109 was greater than now (1052558107)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that virus's log file time of 1052558111 was greater than now (1052558109)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that cpu's log file time of 1052558116 was greater than now (1052558114)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that spoolusage's log file time of 1052558116 was greater than now (1052558114)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that rootusage's log file time of 1052558116 was greater than now (1052558114)
    ERROR: Let's not do the time warp, again. Logfile unchanged.
    Rateup ERROR: /usr/bin/rateup found that iptraffic's log file time of 1052558116 was greater than now (1052558114)
    ERROR: Let's not do the time warp, again. Logfile unchanged.

    :confused:
     
  2. jamesbond

    jamesbond Well-Known Member

    Joined:
    Oct 9, 2002
    Messages:
    738
    Likes Received:
    1
    Trophy Points:
    18
    This is a MRTG issue.
    I believe rateup updates the mrtg logs.

    Maybe you could restart MRTG and see if that helps.
    There might be something wrong with the time setting on the server?
     
Loading...

Share This Page