Ntp not updating time
This means you can have a somewhat correct clock in case there are network issues when you boot up.
Normally, ntpd exits if the offset exceeds the sanity limit, which is 1000 s by default.Yesterday, I got to dive into a computer that had been setup by a vendor and was receiving a different time than the domain computers even though it had been joined to the domain.A configuration must have been changed manually somewhere, which meant I got to dive into all of these settings in order to track down where the change had been made.Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. So we asked the server hosting provider to allow NTP for our machines, and now it works fine.Visit Stack Exchange driftfile /var/lib/ntp/ntp.drift statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable server 0.server 1.server 2.server 3.I know NTP doesn't necessarily bring the clock in time immediately. For example, remote refid st t when poll reach delay offset jitter ============================================================================== ns1.1.23 2 u 10 64 1 1.043 0.258 0.001 ns2.62.1 2 u 9 64 1 0.671 0.135 0.001 ns3.62.1 2 u 8 64 1 0.750 0.277 0.001 (We also switched to servers recommenced by the hosting company, but that is beside the point.) The commands in brent's answer were helpful because they made me realise the problem was in network access to the NTP servers, not in NTP configuration itself. If I had to guess as to why and assuming you have network connectivity and can see your NTP Host without a problem then it could be you have drifted to a large value.