Skip to content

Fix NTS time sync: use 5s retry interval for faster NTS-KE handshake#590

Merged
kvinwang merged 1 commit intomasterfrom
fix/nts-time-sync
Mar 20, 2026
Merged

Fix NTS time sync: use 5s retry interval for faster NTS-KE handshake#590
kvinwang merged 1 commit intomasterfrom
fix/nts-time-sync

Conversation

@kvinwang
Copy link
Collaborator

@kvinwang kvinwang commented Mar 20, 2026

Summary

  • Change chronyc waitsync 20 0.1 to waitsync 30 0.1 0 5
  • The default 10s retry interval was too slow for NTS-KE TLS handshakes which typically complete in ~10s, causing the first retry to almost always be needed
  • 5s interval reduces unnecessary wait while keeping up to 150s total timeout for reliability
  • 30 retries (up from 20) maintains a longer safety window
  • chronyc prints per-attempt status lines natively, so boot logs show sync progress

Test plan

  • Boot a VM with secure_time enabled and verify sync completes within ~10s
  • Verify per-attempt output is visible in boot logs

@kvinwang kvinwang changed the title Fix time sync: wait for chrony to actually sync Improve time sync logging visibility Mar 20, 2026
@kvinwang kvinwang force-pushed the fix/nts-time-sync branch 2 times, most recently from 770daff to db89b49 Compare March 20, 2026 08:55
Add retry loop with per-attempt logging for NTS time sync, making it
easy to diagnose slow NTS-KE handshakes in boot logs.
@kvinwang kvinwang force-pushed the fix/nts-time-sync branch from db89b49 to f4c2f43 Compare March 20, 2026 09:05
@kvinwang kvinwang changed the title Improve time sync logging visibility Fix NTS time sync: use 5s retry interval for faster NTS-KE handshake Mar 20, 2026
@kvinwang kvinwang merged commit 35db0ec into master Mar 20, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant