Ubuntu time not updating
Approved by Ubuntu Technical Board # on 2011-02-08 (LP: #104525). server gov burst iburst server 0burst iburst server 1burst iburst server 2burst iburst server 3burst iburstremote refid st t when poll reach delay offset jitter ============================================================================== *utcnist2.colora . 1 u 571 1024 217 55.804 4.462 0.077 -ntp184.108.40.206.251 3 u 193 1024 377 26.450 12.704 0.062 ualber 220.127.116.11 2 u 514 1024 377 46.636 3.115 0.122 penguin.hopcoun 1.13 2 u 954 1024 377 16.160 -5.821 0.229 147.ip-144-217- 18.104.22.168 2 u 596 1024 377 0.296 -3.495 1.894 STEP 10: Now check the status of timedatectl and you should see the following.
PLEASE NOTE: my time zone is Africa/Johannesburg 0200 so what you see below as the output from timedatectl is correct.
Be very careful of guides telling you to run hwclock —systohc, unless your system time and entire server is running in UTC time, do not set your hardware clock with local time using hwclock —systohc.
Local time: Tue 2017-04-11 SAST Universal time: Tue 2017-04-11 UTC RTC time: Tue 2017-04-11 Time zone: Africa/Johannesburg (SAST, 0200) Network time on: yes NTP synchronized: yes RTC in local TZ: noremote refid st t when poll reach delay offset jitter ============================================================================== *nist1-lnk.binar . 1 u 872 1024 377 32.028 4.001 0.026 2.70 22.214.171.124 2 u 481 1024 377 23.152 -11.972 0.237 -ntp126.96.36.199.252 2 u 1026 1024 377 26.160 -7.960 0.032 ntp188.8.131.52.251 3 u 798 1024 377 19.403 -0.363 0.029 -ntp184.108.40.206.251 3 u 316 1024 377 14.377 9.362 4.976Local time: Tue 2017-04-11 SAST Universal time: Tue 2017-04-11 UTC RTC time: Tue 2017-04-11 Time zone: Africa/Johannesburg (SAST, 0200) Network time on: yes NTP synchronized: yes RTC in local TZ: no STEP 14: If everything checks out we want one final step now to make sure NTP is monitored and if it ever happens to fail for some reason it will get restarted and you will get notified by email about it.
Then it dawned upon me to check NTP as I have been experiencing problems with NTP crashing on both upgrades from Ubuntu 14.0 16.04 and even on fresh 16.04 installs.
In order to have an accurate time and time synchronization to work properly, the system has to be configured with the correct timezone.I will simply just provide you with the correct fix and it will take you all of a minute or two to fix.First let me confirm 100% that ntpdate is deprecated in Ubuntu 16.04 which means it is no longer used, yet some genius at Canonical decided not only to include it with fresh new installs of Ubuntu 16.04 despite the fact that it has been replaced with something called timedatectl, but also to keep it when people upgrade instead of warning them during the upgrade process about this very mission critical thing that can totally screw up your server time as happened to me.During the upgrade this NTP bug surfaced and I was not aware of it. When my DNSSEC on bind re-signed a bunch of domain names using DNSSEC it signed them with a date about 16 hours into the future, this resulted in a bunch of signed records in the domains being detected as BOGUS and immediately caused several web sites of mine to go down.
Not immediately knowing the cause of the issue I temporarily disabled DNSSEC on the domains until I could investigate further.
An incorrect system date and time can cause untold problems and it seems a lot of people have encountered a bug with NTP in Ubuntu 16.04 Xenial with the service either not starting up after a reboot or simply crashing all the time.