similar to: Time moved backwards errors

Scenario: server PC abruptly switched off due to power cable problems (an UPS cannot solve this issue), so during shutdown Linux was not able to resinchronize the system clock. After a few hours the server come back on, Linux booted and the services (ntpd, dovecot and many others) started But the system clock was 45 minutes ahead, so: Jan 19 11:13:39 gw ntpd[2112]: synchronized to LOCAL(0),

OK.. So I synced the clock.... and got .... dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the

i've dovecot --version 1.2.5 hg log | grep changeset | head -n 1 changeset: 9407:a3e16df805e3 in my logs, i'm seeing ... Oct 05 16:51:40 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:07:22 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now

Hallo, I am running dovecot on a PC (a workstation) to have a mail client independent storage for my mails. Now I would like to have the system clock set correctly by using ntpd or ntpdate (using debian/sid). The problem is, that the PC is not online at boot time, but is set online on demand manually using "pon" to start the pppd later. So ntpd cannot sync the time on boot time

Hi all, I am running dovecot version 1.1.1 (dovecot --version) and keeps to have time moved backwards problem. I first found dovecot dead without obvious error message, but see the following when restart dovecot service by # service dovecot restart >Stopping Dovecot Imap: [FAILED] >Starting Dovecot Imap: Warning: Last died with error (see error log for more information): Time

<nervous_darting_eyes> Hi Everyone. </nervous_darting_eyes> Ooops I just broke my dovecot install. I've looked through the mailing list archives and not found anything relevant. When I try to connect to my mail server I get this message. "Could not connect to mail server chen.home.org; connection was refused" The last message in /var/log/mail.err is:- Aug 13

Hello, I would like to suggest a change in handling of 'Time moved backwards' problem. Right now dovecot just dies. So, the scenario: 1) Colocation server is shut down for some reason. The internal time drifts. 2) Server is started again. 3) Dovecot starts successfully. 4) In about a minute, NTP daemon feels confident about adjusting the system time. 5) Dovecot sees the changed time and

Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections

Hi, after setting up a KVM based virtual guest on one of our virtualization servers, we see dovecot die on that virtual guest regularly because of an alleged time shift. The virtual guest is Centos 5.4 based with dovecot 1.2.8 (at first we also tried with the original 1.0.7 (?) dovecot shipped with Centos). I wrote "alleged time shift" because there is no timeshift whatsoever, or

This wins the 2007 award for strangest (or most amusing) log message: dovecot: Time just moved backwards by 13 seconds. This might cause a lot of problems, so I'll just kill myself now. It does, unfortunately, leave dovecot dead, which was pretty mysterious to me. Maybe it could re-exec instead?

Hello *, strange happening yesterday. See this logfile lines: Sep 10 20:45:52 seymour ntpd[9104]: synchronized to 192.53.103.108, stratum 1 Sep 10 20:58:07 seymour ntpd[9104]: synchronized to 134.34.3.18, stratum 1 Sep 10 21:21:02 seymour dovecot: dovecot: Fatal: Time just moved backwards by 434 seconds. [ ... ] Sep 10 21:26:36 seymour ntpd[9104]: no servers reachable Sep 10 21:42:56 seymour

Hi All I have been trying to get this website running for months now. I get this emails from cpanel and don't know how to fix it. If anyone can help me please contact me at pipefab at mweb.co.za. Kind regards Hendrik imap failed @ Fri Oct 12 05:51:18 2012. A restart was attempted automagically. Service Check Method: [check command] Number of Restart Attempts: 1 Cmd Service

A shell script is deployed to synchronize time, the script is invoked hourly by crontab, and its content is as follows: #!/bin/bash service ntpd stop ntpdate 192.168.0.191 #it's a valid ntpd server in LAN service ntpd start chkconfig ntpd on Inspected the Linux log(Centos6.4 /var/log/messages), found the following fragment: Jan 7 14:00:01 host1 ntpd[32101]: ntpd exiting on signal 15 Jan 7

OK, So what you people say is : 1. Run "ntpdate" during startup only once 2. After that, keep time with ntpd Right ? Regards, spyros ---- "I merely function as a channel that filters music through the chaos of noise" - Vangelis

Hello, all. I would like to use ntpd for time sync not rdate or ntpdate. but after installation the ntpd, I found that listened at all interfaces like below. udp 0 0 192.168.111.2:123 0.0.0.0:* 11528/ntpd udp 0 0 xxx.xxx.62.20:123 0.0.0.0:* 11528/ntpd udp 0 0

Hi, To get my system on time, I usually issue these two commands: # ntpdate de.pool.ntp.org # hwclock -w And when I want this to be done on startup, I put the two lines in rc.local. I wonder if this is an orthodox way to do things. Or is there something more appropriate? Niki Kovacs

Hi, I had the following problem today. Because of a misconfigured network switch one system suddenly didn't have any network. After a reboot (with the network still unavailable) NTPD refused to start. Most likely because the initial ntpdate failed to work. I find this troubling, because when the network was restored, NTPD could have resumed working (like I'd expect from a true

Hi there, I got a daily cron (rdate to local time server) job wich adjusts time and which constantly gives me headache. Every day my dovecot suicides with: "dovecot: Time just moved backwards by 11 seconds. This might cause a lot of problems, so I'll just kill myself now." Of course my onboard clock is constantly off by more than 5 secs. I don't want to abandon time

The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in

Hi List I have ntp running as a service on a PC, with the expectation that it would keep time in synch to my ntp server. However, while I can manually update the time using "ntpdate -u ...", I find that if I manually force the wrong time, the ntpd service does not automatically re-synch the system time with the ntp server: - Current time: [admin at lol ~]# date Wed Jan 27 10:54:21