similar to: ntpdate odd behavior

Hello everybody, I just tried to run 'yum update' and got this error: Error: Package: ntp-4.2.6p5-19.el7.centos.x86_64 (@updates) Requires: ntpdate = 4.2.6p5-19.el7.centos Removing: ntpdate-4.2.6p5-19.el7.centos.x86_64 (@updates) ntpdate = 4.2.6p5-19.el7.centos Updated By: ntpdate-4.2.6p5-19.el7.centos.1.x86_64 (updates) ntpdate =

I'm building a new Ubuntu 16.04 machine, including Dovecot. When I select the dovecot-core package in Synaptic, it also wants to install ntpdate. Problem: ntpdate has been replaced in Ubuntu with timedatectl. In fact, if ntpdate exists on the machine, ntpd will not work properly. See: https://help.ubuntu.com/lts/serverguide/NTP.html See:

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

Hi, I''m trying to run ntpdate from domain zero and getting weird results. This used to work (prior to using xen). Is this related to xen at all or an entirely unrelated issue? Queries seem to work: # ntpdate -q time-b.nist.gov Looking for host time-b.nist.gov and service ntp host found : time-b.nist.gov server 129.6.15.29, stratum 1, offset 41.820087, delay 0.17027 17

Hi CentOS 5.3 with latest updates. I have a problem with the time zone on dedicated server. I had to setup the timezone using system-config-date to "Europe/London" and "System clock uses UTC" == checked # date; date -u; hwclock --show; hwclock --show --utc; zdump /etc/localtime Thu May 7 21:29:47 GMT 2009 Thu May 7 21:29:47 UTC 2009 Thu 07 May 2009 09:29:48 PM GMT

https://bugzilla.samba.org/show_bug.cgi?id=4168 Summary: Random file has vanished when syncing clock with ntpdate/hwclock ? Product: rsync Version: 2.6.4 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi all, I''m experiencing problems with time: after I sync time both into dom0 and dom1 with public ntp servers, times are not the same. Do you have the same problem? Thanks Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Yes, it is a "known" issue, I'm sure it's going to get fixed ASAP. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Kai Bojens" <kb at kbojens.de> > To: "CentOS mailing list" <centos at centos.org> > Sent: Wednesday, 24 June, 2015 10:48:22 > Subject: [CentOS] Problem with

On 08/17/2017 09:57 PM, Michael Fox wrote: > I'm building a new Ubuntu 16.04 machine, including Dovecot. > > When I select the dovecot-core package in Synaptic, it also wants to install > ntpdate. Install packages at the command line using apt-get. It lets you better see and understand what's going on. dovecot-core /recommends/ ntpdate. This means you can install with apt-get

On 8/17/2017, 9:57:32 AM, Michael Fox <news at mefox.org> wrote: > When I select the dovecot-core package in Synaptic, it also wants to install > ntpdate. > > Problem: ntpdate has been replaced in Ubuntu with timedatectl. In fact, if > ntpdate exists on the machine, ntpd will not work properly. So, this is obviously an Ubuntu packaging problem, so should be reported there.

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

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

Thanks Louis. Results below. > Hai, > > I've reading this thread more closely. > > I suggest you try the followoing. > > Check the servers hardware clock in the bios first. > Set these within 5 min, if they are not about the same. > There no RTC in the pi; the other DC is running in a VM with RTC set to UTC. I have disabled the guest from getting the time

Hi, I would like to sync my CentOS 6.3 hardware clock time to my NTP server's time. Can I do that without reboot the hosts? If yes, it would be great if anyone of you can provide me steps to do that. I am newbie in CentOS. Thanks, Anand Singh

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

Hello ! Just a quick question about time synchronization between xen dom0 and domUs... We''re running Xen 3.1 64-bit, with 32 and 64 bits linux guests. It''s up since 89 days and the domU''s time is around 5 minutes behind the dom0, which is updated via ntpdate... Any idea why it doesn''t sync the guests even that /proc/sys/xen/independent_wallclock is 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

I have multiple VM's on the same KVM host. One of the VM's is running NTP. All VM's can reach eachother, no firewall in between. But the problem is, the VM's cannot communicate over port 123/udp to the NTP VM. Network: 172.24.100.0/22 KVM: 172.24.101.50 VM ntp: 172.24.102.10 VM foo: 172.24.102.20 1. On the NTP server, listen for any incoming packets from VM foo

I have a Dovecot installation on a Fedora 4. With the last update from Dovecot RC10 to Dovecot RC27, the daemon kills itself every night with this error: Mar 17 05:23:11 mail dovecot: Time just moved backwards by 6 seconds. This might cause a lot of problems, so I'll just kill m yself now. The error appears just after the night maintenance script executes a ntpdate syncronization ntpdate

On 05/02/17 16:15, Richard wrote: > >> Date: Sunday, February 05, 2017 10:26:05 -0500 >> From: Robert Moskowitz <rgm at htt-consult.com> >> >> I have read: >> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >> ween-ntpd-and-chronyd/ >> >> My server is up all the time and will serve time to internal >> systems (via