similar to: Time moved backwards

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, 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 All, I am using vms on gogrid and rackspace completely. I am decent but still learning puppet. The biggest problem with vms, especially where I cant control the Host is ntp time and date sync to be good. Here is my config to sync ntp. Please dont tailor my code just help me fix the problem. This code works 99% of the servers its on except for 2 centos 5 machines. class base { class {

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),

Hello, I am experiencing a number of 'Time moved backwards errors' such as: Mar 27 11:38:20 host-78-129-239-60 dovecot: imap-login: Time just moved backwards by 729 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards Mar 27 15:20:10 host-78-129-239-60 dovecot: Time just moved backwards by 4214 seconds. This might cause

Hi, I've noticed that one of my new servers (new mobo) if drifting slowly backwards in time (in aprox. 24 hours, system time drifts back 5 minutes). I have an ntpd process which is supposed to sync with a lan time server but it's not quite working. So I'm launching a manual ntpdate or ntp-client once an hour and that seems to work. However, suppose I update system time at every hour

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

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

Hi All, I am currently running a setup with a main DC ad1, that has ntpd installed and is currently configured to retrieve the time from the UK NTP time pool. I also have a second backup AD DC, ad2, on which I have not installed ntpd but I have installed ntpdate. My current understanding is that the setup I have just described is in-line with the recommended best practices outlined in the

Hello I get this warning in dovecot.log the machine is running ntpd so this is a bit strange ...

Stan, Thanks for the reply. In our case we have actually already done most of the work you suggested to no avail. We had rebuilt two new ntp servers that sync against two stratum 1 sources, and all our nfs clients, regardless of using dovecot, sync to those two machines. You bring up the difference between bare metal and hypervisor, and we are running these machines on vmware 4.0. All the

Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by

Hi, I have the following manifest that basically syncs the time for nodes really out of sync and ntpd can''t drift the time back fast enough. The problem is that when puppet executes the catalog, and puppet changes the time, puppet never finishes because it can''t calculate the "run time" since puppet changed the time during the puppet run. Is this a bug? Should I do

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

Is there a package to do this? Normally the hardware clock is set during shutdown if one is running ntpd. But if a long-running server shuts down unexpectedly, this isn't done, and the hardware clock might be off by a lot when it comes back up. So setting it periodically from a cron job could be useful. What do others do? Adding a one liner to /etc/cron.daily that invokes

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

I am running CntOS 5 with Gnome. Every now and then I have noticed that the computer will somehow get the time wrong by several hours. Is there a simple way to adjust the time? So far the only way I have found is to boot into windows (it is a dual boot system), make the change there, and then get back into CentOS. Older versions of Red Hat and Fedora let you do it by right-clicking on

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

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 all, my first post. After years with an old server, a couple of months ago I've installed a new one. We use IMAP. After research, I chosed dovecot. It has been running for several weeks but from one week ago or so, it suddently dies about once per day. The only change done in the server one week ago has been to install ntpdate, running once per day in cron-daily. In the cron