Clock not syncing
- Dominant language
- No language data
- Stars
- 149
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Every time I boot my printer, the date is way wrong. My CB2 is not setting time via NTP servers, even though they're reachable.
after setting the time, `timedatectl` shows:
``` Local time: Thu 2026-03-12 13:21:04 EDT
Universal time: Thu 2026-03-12 17:21:04 UTC
RTC time: Fri 2017-08-04 10:55:19
Time zone: America/New_York (EDT, -0400)
System clock synchronized: no
NTP service: active
RTC in local TZ: no
```
For some reason the RTC is way off
`timedatectl show-timesync` shows
```SystemNTPServers=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org
FallbackNTPServers=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
RootDistanceMaxUSec=5s
PollIntervalMinUSec=32s
PollIntervalMaxUSec=34min 8s
PollIntervalUSec=0
Frequency=0
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the problem after boot and inspect the output of `timedatectl` and `timedatectl show-timesync`. Done means the RTC retains the correct time across boots and the system reports successful NTP synchronization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100