[Dovecot] Time moving backwards error
I'm running dovecot on an OpenBSD 3.7 server and after upgrading to RC25, the daemon started exiting with:
Fatal: Time just moved backwards (1173221579 -> 1173221578)! This might cause a lot of problems, so I'll just kill myself now.
After upgrading to RC26, I've gotten the error:
Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present.
Occasionally, however, it's followed by:
Fatal: Sleep interrupted, byebye.The server is running NTP, but I can't find any reason why it would have to roll the clock back a second so often. Until I get this figured out, I've gone back to RC19.
Any ideas? Thanks.
-- Emmett "Buddy" Pate Chief Technology Officer William E. Wood and Associates, Realtors epate@williamewood.com
On Wed, 7 Mar 2007, Emmett Pate wrote:
****** snipped ******
Hi Emmett,
I had some servers that somehow "loses" time after a while and ntpd always had to resync. The problem went away after I replaced the onboard Lithium battery. Have you tried replacing the battery?
Cheers.
On Wed, 2007-03-07 at 08:22 -0500, Emmett Pate wrote:
Occasionally, however, it's followed by:
Fatal: Sleep interrupted, byebye.
I thought this would never happen, so I didn't bother handling it. But this'll fix it: http://dovecot.org/list/dovecot-cvs/2007-March/007979.html
I guess your clock doesn't stay on time somehow. No idea why.. But I found this from ntpd(8):
-x Ordinarily, if the time is to be adjusted more than 128ms, it is stepped, not gradually slewed. This option forces the time to be slewed in all cases. Note: Since the slew rate is limited to 0.5 ms/s, each second of adjustment requires an amortization interval of 2000 s. Thus an adjustment of many seconds can take hours or days to amortize.
participants (3)
-
Emmett Pate
-
Tan Shao Yi
-
Timo Sirainen