I had a similar problem on a different server that I fixed last night.
Evidently it had a BIOS level feature that tried to modify the CPU clock
rate, much like cpu-freq does within the kernel, and was doing so by
messing with the system clock impacting the RTC. I was drifting all
over the place u
I'm still having this issue. Here is another update. I noticed that
the drift file for the system with the problem contained "0.000". On
most other systems this contains a positive number (and on two a
negative number). I deleted the drift file, resynch'ed the time with
"ntpdate ", rest
On May 21, 2008, at 0:55, Paul Heinlein wrote:
Yeah, with an offset of 54 seconds, it's a bad system. :-)
Try this (assuming 10.101.32.104 is your preferred local NTP server):
service ntpd stop
echo "10.101.32.104" > /etc/ntp/step-tickers
service ntpd start
Adding a server to the step-t
On Tue, 20 May 2008, Alfred von Campe wrote:
Bad system:
# ntpq -np
remote refid st t when poll reach delay offset jitter
==
10.101.32.104 67.128.71.65 3 u 689 1024 3770.659 54095.7 4
On Tue, May 20, 2008 at 8:53 PM, Alfred von Campe <[EMAIL PROTECTED]> wrote:
> # ntpq -np
> remote refid st t when poll reach delay offset
> jitter
> ==
> 10.101.32.104 67.128.71.65 3 u 689 1
On May 20, 2008, at 20:25, Filipe Brandenburger wrote:
What is the output of "ntpq -np" ? You should have a line with a star
(*), otherwise it is not synchronizing. Start running NTP again, wait
for half an hour and issue that command to see what your output is. It
could be a problem related to
On May 20, 2008, at 16:56, Paul Heinlein wrote:
A slew of 5 min/24 hrs should be in the range of fixable.
If the NTP daemon was doing its job :-).
This is very suspect. Are there any SELinux or other log messages
suggesting that ntpd isn't able to write to its drift file? Your
local clock
On Tue, May 20, 2008 at 3:46 PM, Alfred von Campe <[EMAIL PROTECTED]> wrote:
> 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 tha
On Tue, 20 May 2008, Alfred von Campe wrote:
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 a
9 matches
Mail list logo
