I have a server that has a time drift of around a minute every hour. Overnight, that is pretty extreme and as this is a PVR, it causes problems.
I have NTP enabled but am still getting this drift and NTP is not correcting or putting much in the logs ( no exit messages )
I am looking for a time or NTP expert to assist.
Here are some outputs
ntp.conf
ntpq ( peers output )
ntpd.log output
it is currently about 10 minutes out after a sync to
tick.usno.navy.mil yesterday at 5PM and then turning on ntpd
--------------------------
ntp.conf
Password:
[root@mythfront ~]# cat /etc/ntp.conf
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
logfile /var/log/ntpd.log
restrict default nomodify notrap noquery
# Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of
# the administrative functions.
restrict 127.0.0.1
# -- CLIENT NETWORK -------
# Permit systems on this network to synchronize with this
# time service. Do not permit those systems to modify the
# configuration of this service. Also, do not use those
# systems as peers for synchronization.
# restrict 192.168.1.0
mask 255.255.255.0 nomodify notrap
# --- OUR TIMESERVERS -----
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
# --- NTP MULTICASTCLIENT ---
#multicastclient # listen on default 224.0.1.1
# restrict
224.0.1.1 mask 255.255.255.255 nomodify notrap
# restrict 192.168.1.0 mask 255.255.255.0
nomodify notrap
# --- GENERAL CONFIGURATION ---
#
# Undisciplined Local Clock. This is a fake driver intended for backup
# and when no outside source of synchronized time is available. The
# default stratum is usually 3, but in this case we elect to use stratum
# 0. Since the server line does not have the prefer keyword, this driver
# is never used for synchronization, unless no other other
# synchronization source is available. In case the local host is
# controlled by some external source, such as an external oscillator or
# another protocol, the prefer keyword would cause the local host to
# disregard all other synchronization sources, unless the kernel
# modifications are in use and declare an unsynchronized condition.
#
server 127.127.1.0
fudge 127.127.1.0 stratum 10
#
# Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file
# by creating a temporary in the same directory and then rename()'ing
# it to the file.
#
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
#
# Keys file. If you want to diddle your server at run time, make a
# keys file (mode 600 for sure) and define the key number to be
# used for making requests.
#
# PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
# systems might be able to reset your clock at will. Note also that
# ntpd is started with a -A flag, disabling authentication, that
# will have to be removed as well.
#
keys /etc/ntp/keys
restrict 0.pool.ntp.org mask
255.255.255.255 nomodify notrap noquery
restrict 1.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
restrict
2.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
------------------------------------
ntpd.log
31 May 17:30:47 ntpd[28707]: frequency initialized 0.000
PPM from /var/lib/ntp/drift
31 May 17:31:26 ntpd[28707]: ntpd exiting on signal 15
31 May 17:31:39 ntpd[28827]: frequency initialized 0.000 PPM from /var/lib/ntp/drift
31 May 17:33:41 ntpd[28827]: ntpd exiting on signal 15
31 May 17:33:56 ntpd[28920]: frequency initialized 0.000 PPM from /var/lib/ntp/drift
31 May 17:34:30 ntpd[28920]: ntpd exiting on signal 15
31 May 17:34:50 ntpd[28973]: frequency initialized 0.000 PPM from /var/lib/ntp/drift
31 May 17:38:08 ntpd[28973]: synchronized to LOCAL(0), stratum 10
31 May 17:38:08 ntpd[28973]: kernel time sync enabled 0001
---------------------------
ntpq peers output
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
leela.isw.stude 195.13.1.153 3 u 11 1024 377 145.912 1066136 24034.0
ns4.your.org 128.4.40.12 3 u 3 1024 377 145.563 1066158 23934.9
agw-01.ham.aman 209.97.231.218 3 u 11 1024 377 149.521 1042189
24036.0
*LOCAL(0) .LOCL. 10 l 46 64 377 0.000 0.000 0.001
Anyone have any thoughts on what could be up with this?
Other things I can try. I am not sure why my clock is off this much. All brand new hardware as well.
