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

system clock weirdness #16

Open
stapelberg opened this issue Nov 28, 2018 · 1 comment
Open

system clock weirdness #16

stapelberg opened this issue Nov 28, 2018 · 1 comment

Comments

@stapelberg
Copy link
Contributor

From my most recent boot:

2020/05/27 21:37:53 listeners.go:141: now listening on 127.0.0.1:80

The time being way off resulted in an update not succeeding:

2018/11/28 07:08:22 unhealthy after 39.59549534s: unhealthy: dhcp6: lease expired at 2018-11-28 07:28:03.860663142 +0100 CET

Note that the expiration timestamp is in the future.

Not sure what’s happening here. We’re setting the RTC in https://github.com/gokrazy/gokrazy/blob/2216841c80ef508f43b5b742ff423124f965f868/cmd/ntp/rtc.go

@stapelberg
Copy link
Contributor Author

One possible theory is that the NTP client set the system time based on a misconfigured NTP pool server. Maybe we should always query 3 NTP servers and set the time only if 2 of them are within a 5s window of each other.

@stapelberg stapelberg changed the title apu hardware clock weirdness system clock weirdness Dec 25, 2018
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

No branches or pull requests

1 participant