Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

force-sync output contains wrong time #1789

Open
AGWA opened this issue Jan 11, 2025 · 1 comment · May be fixed by #1803
Open

force-sync output contains wrong time #1789

AGWA opened this issue Jan 11, 2025 · 1 comment · May be fixed by #1803

Comments

@AGWA
Copy link

AGWA commented Jan 11, 2025

Version:

# ntp-daemon --version
ntp-daemon 1.4.0

I did:

# date --set="now + 48 hours"
Mon Jan 13 21:25:41 UTC 2025
# ntp-ctl force-sync
Determining current time...
The current local time is: Mon Jan 13 21:25:43 2025
It looks like the time should be: Mon Jan 13 21:25:43 2025
It looks like your clock is ahead by 1 day(s) 23 hour(s) 59 minute(s) 60 second(s)
Please validate externally that this offset is correct
Do you want to update your local clock? [y/N]

Note that the "current local time" and the "looks like the time should be" time are the same. I expected to see:

The current local time is: Mon Jan 13 21:25:43 2025
It looks like the time should be: Sat Jan 11 21:25:43 2025
@davidv1992 davidv1992 linked a pull request Jan 24, 2025 that will close this issue
@davidv1992
Copy link
Member

Thank you for reporting this, we have found the bug and a PR is in the pipeline.

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 a pull request may close this issue.

2 participants