[Dovecot] Time jumped forwards
Running Dovecot 2.0.8 on 32bit Centos5.5. The machine is a VMWare ESX VM.
I'm seeing a lot of warning messages in syslog as follows:
2011-01-14T11:45:37.315917+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:00.598006+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:25.364405+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:27.030658+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:49.712202+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:07.600748+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:23.195587+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:37.342804+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:42.671037+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:45.903081+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:49.001119+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:58.935835+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:49:15.046253+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 104 seconds 2011-01-14T11:49:16.842962+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds
I've checked the clock settings in Centos and it all looks OK. NTP is running and not complaining about clock drift. Vmware recommend appending 'divider=10 clocksource=acpi_pm' kernel boot options to prevent timekeeping issues, which I've done.
Has anyone else encountered this message? Is it something to be concerned about?
Thanks, Ian.
On 01/13/2011 09:01 PM, Ian B wrote:
Running Dovecot 2.0.8 on 32bit Centos5.5. The machine is a VMWare ESX VM.
I'm seeing a lot of warning messages in syslog as follows:
2011-01-14T11:45:37.315917+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:00.598006+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:25.364405+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:27.030658+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:49.712202+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:07.600748+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:23.195587+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:37.342804+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:42.671037+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:45.903081+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:49.001119+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:58.935835+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:49:15.046253+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 104 seconds 2011-01-14T11:49:16.842962+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds
I've checked the clock settings in Centos and it all looks OK. NTP is running and not complaining about clock drift. Vmware recommend appending 'divider=10 clocksource=acpi_pm' kernel boot options to prevent timekeeping issues, which I've done.
Has anyone else encountered this message? Is it something to be concerned about?
Thanks, Ian.
In particular, see NTP Recommendations and VMware Tools bits at the bottom.
-- -Eric 'shubes'
participants (2)
-
Eric Shubert
-
Ian B