[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ntpd and kernel message set_rtc_mmss: can't update



Rob Brown-Bayliss:
>> [root localhost ~]# ntpq -p
>>     remote           refid      st t when poll reach   delay   offset  jitter
>> ==============================================================================
>> mu-relay1.masse 192.5.41.40      2 u   16   64  177  170.570  -798.72 12760.3
>> ns1.compass.net 128.250.36.3     2 u   14   64  177  112.739  -13008. 7668.06
>> cobol.appello.n 128.250.37.2     2 u   14   64  177  162.234  -897.55 11922.0
>> ntp.thistledown .GPS.            1 u   19   64  177  203.800  -3927.4 9253.24
>> gen2.ihug.co.nz 130.217.76.49    2 u   14   64  177  140.795  -7057.9 7349.37

Wolfgang S. Rupprecht:
> Actually that looks good as far as ntpd synch-ing to outside servers
> goes.  The servers it is syncing to, or the network connection it is
> syncing over, on the other hand suck big-time.  Notice the "offset"
> fields all differ from one another by a very large number of
> milliseconds.  I see an offset of 0.7 0.8 3.9 7 13 seconds!  No 3
> servers seem to agree as to what time it really is.  Thats not good at
> all.  If your network connection is really overloaded (with up to a 13
> second delay in a packet), then ntp is going to have a very hard time
> setting the time on your system.

I notice that it seems to be the usual case that server's don't agree
with each other (see below).  There's some that are close, but no two
are the same.


When NTPD had been left running for weeks:
# ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*211.29.132.139  128.250.36.3     2 u   20 1024  377   47.222    2.593   3.019
+192.36.143.153  193.10.7.250     2 u  978 1024  377  352.492   18.964   3.206
 203.86.196.7    .STEP.          16 u  41d 1024    0    0.000    0.000 4000.00
-193.224.70.7    195.111.96.158   2 u  990 1024  377  442.890   41.293  39.813
+202.49.59.6     203.109.252.7    3 u 1014 1024  377  101.923   20.470 192.509
 127.127.1.0     LOCAL(0)         9 l   50   64  377    0.000    0.000   0.002

After restarting NTPD, while writing this email:
# ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
-202.125.40.143  128.250.36.2     2 u   59   64    3   61.756    3.541   0.648
+211.29.132.139  128.250.36.3     2 u   59   64    3   45.508    1.467   0.375
-194.146.145.193 192.53.103.108   2 u   57   64    3  356.367    3.220   6.608
*192.245.169.15  .PPS.            1 u   56   64    3  374.875    0.402   7.593
+194.100.206.70  192.36.134.17    2 u   54   64    3  420.466    0.377   7.462
-202.49.59.6     203.109.252.7    3 u   52   64    3   72.288    3.462   4.945
 127.127.1.0     LOCAL(0)         9 l   53   64    3    0.000    0.000   0.004

# grep server /etc/ntp.conf
server au.pool.ntp.org iburst
server time.optusnet.com.au iburst
#server pool.ntp.org iburst
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst
server 1.nz.pool.ntp.org iburst
server 127.127.1.0

-- 
(Currently testing FC5, but still running FC4, if that's important.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]