[mythtv-users] OT: ntp won't synchronize

[Michael T. Dean]

matthew.garman at gmail.com wrote:

>I tried recording with MythTV for the first time last night.
>Everything work as expected---except for the time!  My computer was
>running 15 minutes fast, so my recorded TV was off.
>
>Now I'm struggling with NTP.  Actually, I've been struggling with
>ntp for some time now.  I've followed the gentoo wiki HOWTO for ntp:
>
>    http://gentoo-wiki.com/HOWTO_Setup_MythTV#NTP
>
>As well as many other sources over the months.  Basically, ntpq
>shows that I am not synchronized to any peers:
>
># ntpq -p
>     remote           refid      st t when poll reach   delay   offset  jitter
>==============================================================================
> Time4.Stupi.SE  .PPS.            1 u   37   64  377  124.516  -11202. 1225.91
> thesimonet.org  .TRUE.           1 u   38   64  377  109.329  -11213. 1232.51
> fin.rshell.net  192.114.62.249   3 u   32   64  377  205.910  -9569.1 1521.31
> titan.cais.rnp. 32.233.177.224   2 u   44   64  377  165.240  -11991. 1915.26
>
>That first space in the peers list is a tally mark that, according to
>the ntpq documentation at:
>
>    http://www.eecis.udel.edu/~mills/ntp/html/ntpq.html
>
>Means that those peers are all rejected: "The peer is discarded as
>unreachable, synchronized to this server (synch loop) or outrageous
>synchronization distance."
>  
>
"outrageous synchronization distance" -- did you ever set your clock to 
be closer to the real time than 15 minutes off?  NTP will refuse to 
synch if the delta is large.

Stop NTP then:

ntpdate -b <time server name>

Then start NTP (and give it a while--at least 10 or 15 minutes--before 
trusting a rejection message).  Note, also, that a backwards clock step 
of 15 minutes may give "unusual" results during the 15 minutes of 
"repeated time" (i.e. wait until the repeat is over before compiling 
anything or doing other stuff that's affected by the current time).

Mike