Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Linux NTP troubleshooting: fix clock drift and failed time sync

Published August 2026 · 2 min read · Updated 2026-09-05

NTP problems show up as more than a wrong wall clock. Time drift can invalidate TLS, break signed tokens, distort logs, confuse distributed jobs, and make incident timelines impossible to correlate across systems.

Measure synchronization state, not only date output

Use timedatectl, chronyc, or the configured time client to check whether the system is synchronized, which sources are selected, offset, reachability, and recent corrections. A clock that looks close by eye can still be outside the tolerance of authentication systems.

Virtual machines should normally use a real time-sync service; occasional hypervisor clock correction is not enough by itself.

Check source reachability and firewall policy

NTP commonly uses UDP 123. Confirm the configured sources resolve and are reachable from the server. Corporate/VPN routing or restrictive outbound rules can isolate time service while web traffic still works.

Use multiple appropriate sources so one unavailable endpoint does not leave the machine drifting indefinitely.

Treat large jumps carefully

A large time correction can affect scheduled jobs, logs, leases, databases, and software expecting monotonic progression. Understand whether the client will step or slew and whether the workload needs a maintenance window for a severe correction.

Fix the underlying source or RTC/virtualization issue if drift repeatedly returns.

Verify dependent systems after recovery

Retest TLS, authentication, scheduled jobs, monitoring timestamps, and distributed application behavior. Alert on unsynchronized state or excessive offset so the next failure is detected before certificates or tokens start failing.

  • Check sync status and offset.
  • Verify source reachability.
  • Understand step versus slew behavior.
  • Monitor time health continuously.

Next step

Check time sources, synchronization state, reachability and clock offset so TLS, logs, authentication and scheduled jobs are not broken by bad system time.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move