meta data for this page
  •  
Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book(0 page(s))
 Help

This is an old revision of the document!

ntptime

Issues

Not synchronized clock

Cannot set correct time. Manual setting time by date command is ignored. 

$ sudo timedatectl 
               Local time: Mon 2019-10-28 18:11:50 CET
           Universal time: Mon 2019-10-28 17:11:50 UTC
                 RTC time: Mon 2019-10-28 15:58:24
                Time zone: Europe/Warsaw (CET, +0100)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
$ sudo ntptime
ntp_gettime() returns code 5 (ERROR)
  time e161a024.e5878318  Mon, Oct 28 2019 18:13:08.896, (.896599762),
  maximum error 16000000 us, estimated error 16000000 us, TAI offset 0
ntp_adjtime() returns code 5 (ERROR)
  modes 0x0 (),
  offset 0.000 us, frequency 93.212 ppm, interval 1 s,
  maximum error 16000000 us, estimated error 16000000 us,
  status 0x2041 (PLL,UNSYNC,NANO),
  time constant 3, precision 0.001 us, tolerance 500 ppm,

Reason is: there is no possibility to set clock to past. It is possible to adjust kernel clock to slow down. Also some AMD platform are known for big clock drifts. 

You can only set times in the future, setting past times with date command will do nothing and no error will be shown. Ntpd service will correct slowly the time at small steps. It's not like in Windows     where you can set any time and see the result immediately.