[Dovecot] dovecot: Fatal: Time just moved backwards by 3603 seconds.

[Scott Silva]

on 8-18-2008 1:54 PM Charles Marcus spake the following:
> On 8/18/2008, Ville Walveranta (walveranta at gmail.com) wrote:
>> ntp client as a service (daemon) is the way to go... I had the same
>> problem; I wasn't aware of the fact that dovecot would be sensitive to
>> time going backwards. I was running ntpdate via cron, and the first
>> time the time-check resulted in backwards correction, dovecot bombed.
> 
> This is nothing new... time has *always* been considered extremely
> critical on servers - and ntpdate has *always* been seen as the WRONG
> way to keep a server in time - it moves time in much too large increments.
> 
> An ntp client has always been the way to go...
> 
> But you should also make sure your hardware clock is not totally crapped
> out, as that can make a [successful] cold start problematic...
> 
During a cold start is probably the ONLY time ntpdate would be appropriate. 
Call ntpdate right after the network starts, but before the other services get 
started and your time should be very close. Then a ntp client can keep it that 
way.

-- 
MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://dovecot.org/pipermail/dovecot/attachments/20080819/083ae59a/attachment-0001.bin