similar to: Ubuntu 16.04 dovecot-core requires deprecated ntpdate

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.

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

I noticed this morning that my ntp time was not correct on machines. So I manually ran "ntpdate time.apple.com" on my clients, I got 7 May 08:46:43 ntpdate[10550]: no server suitable for synchronization found then I ran "ntpdate -d time.apple.com" and it worked . filter offset: -163.446 -163.446 -163.446 -163.447 0.000000 0.000000 0.000000 0.000000 delay 0.20570,

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 =

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

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

Hai Gregory,   No problem, now netplan, but i cant tell you much about netplan out of experiance, i've never used it. But what is it exact you want to know?? The how and why i configure like this is already a bit explained.   about this part: > So, I'm curious about the contrast between modifying netplan vs simply disabling systemd.resolved   But I did a bit reading.

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

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

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

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

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

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

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

Hi, the date jumps within 30 seconds to a wrong value. ntp service is stopped at the beginning. Whereas hwclock seems more precise. [root at kerio ~]# service ntpd stop Shutting down ntpd: [ OK ] [root at kerio ~]# ntpdate 0.centos.pool.ntp.org 13 Mar 07:04:48 ntpdate[23003]: step time server 131.234.137.24 offset -3450.678273 sec [root at

> 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 DHCP options). > > Caveat is that my server is an armv7

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