Amos Shapira wrote:
2008/7/23 Shachar Shemesh <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
Hi all,
I have a strange problem, and it is happening on several servers.
I set up NTP to synchronize, sometimes with a local NTP source
(say, a Windows Server domain controller) and sometime external
(the usual ntp servers). The NTP process is working, and displays
the time offset properly. However, it does not keep the machine
synchronized with the server.
You can see images from munin monitoring that machine, showing how
the time keeps drifting away. At some point I ran ntpdate, and
that synchronized the clocks ok until the times started drifting
apart again.
Any idea where to look for the source of the problem?
My standard issue is "ntptrace" (on the server's machine).
Also see "ntpq -p", taken from http://www.ntp.org/ntpfaq/NTP-s-trouble.htm
--Amos
Hi,
I never had problem with external ntp server, but it seems that ntp
require the server to be in a low stratum value - so for example the
root server can't use its local BIOS clock as a source.
I saw this problem at customers that were using the AD server as the
root time source, ntpdate was updating fine - but since the stratum of
the AD server was high ( 14 or so) ntpd refused tosync with it.
The solution was to sync the AD server with a reliable data source (
e.g. external NTP server or GPS clock in non internet connected
environment).
Tomer
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
