[ntp:questions] LOCL clock reachability not 377?

mike cook michael.cook at sfr.fr
Wed Jul 30 06:50:45 UTC 2014


Paradoxically , the LCL clock is fine when there are no refclocks. That is, when you don't need or want it.

     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*127.127.1.1     .LOCL.           5 l    8   64  377    0.000    0.000   0.008
+192.168.1.4     .PPS1.           1 u    5   16  377    0.900   -0.022   0.030
+192.168.1.23    .GPS.            1 u   23   64  377    0.804   -0.134   0.017



Le 30 juil. 2014 à 06:46, Brian Inglis a écrit :

> On 2014-07-29 21:32, Paul wrote:
>> On Tue, Jul 29, 2014 at 10:15 PM, Brian Inglis
>> <Brian.Inglis at systematicsw.ab.ca> wrote:
>>> As I discovered recently under similar circumstances, offline servers are
>>> considered falsetickers, and if you have insufficient other candidates, or
>>> fewer than 3, nothing gets selected.
> 
>> I don't think I'm seeing what you're seeing but I could be confused.
>> I believe I mentioned the same thing last time around on this topic.
> 
> Default for minsane is 3, if that is where you are confused.
> Not seen this topic mentioned in the last year or more.
> 
>> ntpd --version;ntpq -pn
>> ntpd 4.2.7p440 at 1.2483-o Tue Apr 22 11:51:47 UTC 2014 (6)
>>      remote           refid      st t when poll reach   delay   offset  jitter
>> ==============================================================================
>> o127.127.22.0    .GPPS.           0 l    2    8  377    0.000   -0.002   0.004
>> *127.127.1.0     .LOCL.          12 l   65    8    0    0.000    0.000   0.004
>>  192.168.0.210   .GPS.            1 u   22   32  377    1.304   -0.080   0.028
>> 
>> or just using LOCL ...
>> 
>>      remote           refid      st t when poll reach   delay   offset  jitter
>> ==============================================================================
>> o127.127.22.0    .GPPS.           0 l    5    8  377    0.000   -0.005   0.008
>> *127.127.1.0     .LOCL.          12 l   60    8  200    0.000    0.000   0.008
>> 
>> naturally you need to let NTP discipline your clock and a cold start
>> requires something to set it.
> 
> These statuses show the same issue with local clock reach, implying if reach stays
> at zero, sync will be lost and PPS become a falseticker without anything to number
> seconds for too long.
> 
> Read the thread about the OP's config and problems.
> 
> -- 
> Take care. Thanks, Brian Inglis
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions


More information about the questions mailing list