similar to: Fwd: Re: Dotlock dovecot-uidlist errors / NFS / High Load

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first

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

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

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 have 30 identical Lenovo desktop systems running CentOS 5.1. On one of those systems the clock is running slow (5+ minutes from yesterday to this morning and another minute since this morning) despite the fact that NTP is running on all of them and they all have the exact same /etc/ntp.conf file (I compared the MD5 sums of that file on all the systems). Here is the output of

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

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

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

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

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, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64

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

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

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

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

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

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

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