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