Opened 12 years ago
Closed 11 years ago
#11 closed defect (fixed)
bug with peer time sync
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.7.11 |
Component: | router/clock | Version: | |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description
i recently discovered a bug with the time syncronization with peers.
every 2h or so i got an error message like this and all peers where dropped:
ERROR [Timestamper ] net.i2p.util.Clock : Ignoring clock offset 111458ms (current 197940ms) since it would increase peer clock skew from 1s to -85s. Broken server in pool.ntp.org?
my clock is indeed not correct, but i think thats what the ntp servers are for.
after setting router.clockOffsetSanityCheck=false the error didn`t occure again. at least until now after more than a week uptime (thanks complication )
this bug is reproducible (withturning clockOffsetSantiyCheck back on).
For discussion see: http://zzz.i2p/topics/149
Subtickets
Change History (4)
comment:1 Changed 12 years ago by
Milestone: | → 0.6.5 |
---|
comment:2 Changed 12 years ago by
Component: | router/general → router/clock |
---|
comment:3 Changed 12 years ago by
Priority: | major → minor |
---|
comment:4 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Maybe fixed, maybe not.
Perhaps a "real" fix is to implement "real" NTP, that slews the clock gradually, instead of simply making (or not making) step changes.
However, if your system clock glitches every two hours, I don't know how to fix that. Run NTPD.