Re: 30 Minutes (system time/ntpdate/dovecot)

Thread View: gmane.linux.debian.user

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by David Baron Sun, 14 Jun 2009 16:50

#307871

Author: David Baron
Date: Sun, 14 Jun 2009 16:50

29 lines
1101 bytes

>>>Has been happening quite a bit lately:

>>>Problem with ntpdate. If and when it finally works, get a change of 10,800
>seconds ... that is 30 minutes.

>>>The dovecot IMAPd server is unreadable. Restarting it yields a complaint
>>>about 10,800 seconds of time, killing itself now! Restarting it again
>>>works OK.

>>>What's happening? Bug? Fix?

>>Of course, we are missing the point. No, it is not 30 minutes like my eyes
>>fooled me into a cute title. This is three hours and that is a significant
>>number. I live at GMT + 2. Add one for daylight savings time.

>>However, I have never used GMT (universal) time to save my system time.
>>So why is this happening now? Ntpdate has not been upgraded past few days.

>>... and why should dovecot care?

>OK, time to fix this. Since my system comes up with the "correct" time zone
>but three hours later, it must be interpreting the stored (hw) time as GMT
>and adding the three hours (gmt+2 + daylight savings).

>How to fix this?

Even more. I get a bootup error message failing to set date (and time) to ...
the following day + 3 hours!!

Re: 30 Minutes (system time/ntpdate/dovecot)

#307919

Author: "Todd A. Jacobs"
Date: Sun, 14 Jun 2009 19:54

24 lines
889 bytes

On Sun, Jun 14, 2009 at 04:50:23PM +0300, David Baron wrote:

> Even more. I get a bootup error message failing to set date (and time)
> to ... the following day + 3 hours!!

You may have a bad system clock. That does happen on some older
hardware or if a CMOS battery goes bad. I'd do the following:

    - Make sure you're calling "hwlock --systohc --localtime" at some
      point when your time has been correctly set.

    - Make sure /etc/default/ntp contains "NTPD_OPTS='-g'" so that you
      can handle large clock offsets.

If that still doesn't really resolve your problem, then you might want
to try chrony instead, which assumes that your clock has a stable drift
rate that can be compensated for. NTP is certainly better for accuracy,
but chrony is a little more tolerant of clock issues as far as I can
tell.

--
"Oh, look: rocks!"
	-- Doctor Who, "Destiny of the Daleks"

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads