similar to: Time just moved backwards error even with ntpd

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

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

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 guys, Thanks for your reply. I originally used the following command to synchronize time: ntpdate 192.168.0.191 but got the error: ntpdate[16715]: the NTP socket is in use, exiting So i used the way of stopping ntpd service. Now I have known that using command "ntpdate -u 192.168.0.191" can solve the above error, and also know using ntpdate command is an improper way, i.e. should use

This is really stupid question. But referring to: http://lists.centos.org/pipermail/centos/2009-October/083791.html I don't see any line related to ntpd in my /var/log/messages . Do I need to turn-on ntpd for timekeeping on VMs? Some people say not to use ntpd on VMs for timekeeping or is it ntpdate cron job? Can someone please elaborate on this? Thanks, Jonathan. -------------- next part

Hello, in system-config-date i have checkbox synchronize date before service startup. Which config switch,file does it affect? I want to turn it on on my CentOS machine without xauth , just editing config files , i was hoping it could be in /etc/sysconfig/ntpd but no. Thanks in advance! D. -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 {

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

I've seen situations where people have put ntpdate in a cronjob to get around issues with big time jumps at boot or dodgy clocks under virtualization. There are much better solutions to this problem, so let us know if this is the case for you. K

Hi there, I've been a happy djbdns+tinydns user for many, many years. I want to keep using it, so answers of the form "bletch! Use ISC BIND the way BSD intended" will be ignored :-) Having said that, one annoying consequence of my transition some time ago to using ntpd, rather than just setting the clock once-off with ntpdate as I used to, is that the /etc/rc.d mechanism starts

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

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

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

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 have got problems with the ntp daemon. It is enabled in systemd but is not started on boot. # systemctl status ntpd ? ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled) Active: inactive (dead) Starting manually works # systemctl start ntpd # systemctl status ntpd ? ntpd.service - Network Time Service

We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [root at devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [root at devserver21 ~]# rdate -s 192.168.1.67 [root at devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap

Hi All, Currently CentOS site contains the below version of ntpd. ntp-4.2.6p5-3.el6.centos.x86_64.rpm<http://mirror.centos.org/centos/6.6/updates/x86_64/Packages/ntp-4.2.6p5-3.el6.centos.x86_64.rpm> :- 16 mar 2015. Does anybody have any information about when the new version of ntpd is expected to release containing new vulnerabilities fixes? Thanks Vijendra.

I am running a server inside of VMWare, and the clock gains ~30 seconds every 1000 seconds or 1.03X. I need to keep the drift under the magic 1000 limit that ntpd kills its self, but despite setting maxpoll really low I get: Dec 11 23:58:14 host ntpd[4909]: kernel time discipline status change 41 Dec 11 23:59:17 host ntpd[4909]: kernel time discipline status change 1 Dec 11 23:59:17 host

Hi, I'm in the middle of migrating our oracle servers to RHEL and C6; while testing ntpd I'm seeing time resets. I see in sysconfig/ntpd the option g is set which means huge offset is one time ignored. But my understanding of ntpd is, it slows or accelerated kernel clock but does not make huge jumps... Is this really expected behaviour? The file step-tickers is empty, ntp.conf is

CentOS 6.4, x86_64. ntpd on one of my systems has started consuming 66% of one core, although it appears to be functioning correctly otherwise. No pertinent logs. Of course, nothing was changed :) I've seen this before many times, but usually the CPU consumption falls back to normal within a day or so, but this has been going on for several weeks now. Stopping and restarting ntpd makes