Re: Chrony on Asus router - no reduction of offset
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZIbHb+i3C3jfKnfU@localhost> |
On Sat, Jun 10, 2023 at 08:09:04PM +0200, Torsten Wolf wrote: > Name/IP Address           NP NR Span Frequency Freq Skew Offset Std > Dev > ============================================================================== > 192.168.1.105             44 19  46m -2691.479   161.086   -91ms 242ms > zeit.fu-berlin.de         48 21  50m -2636.146   123.263   +17ms 218ms > ptbtime1.ptb.de           57 25  60m -2632.208   101.466   +45ms 232ms > ptbtime2.ptb.de           54 23  57m -2651.780   111.097   -18ms 234ms > ptbtime3.ptb.de           55 24  58m -2601.458   110.065  +114ms 233ms > ns.tu-berlin.de           49 21  51m -2600.763   126.308   +79ms 245ms The skew is too large for the frequency to be accepted with that maxupdateskew you have configured. This causes the clock to drift away between updates (sawtooth wave). There is something wrong with the system or hardware. Stddev of 240ms to a local server is too high. Is ping to the server better? -- Miroslav Lichvar -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]