Opened 4 years ago

Last modified 4 years ago

#2113 open defect

Clock adjust during startup prevents router from starting

Reported by: Reportage Owned by:
Priority: major Milestone: undecided
Component: router/general Version: 0.9.32
Keywords: error, heisenbug, time, startup Cc:
Parent Tickets: Sensitive: no


If the system's clock is updated during the router's startup, the router fails to start with no indication that it failed other than the lack of the router console opening in the browser (if configured). I think this issue may have been reported before.

To reproduce, manually sync the computer's clock during router startup.


Change History (3)

comment:1 Changed 4 years ago by zzz

Status: newinfoneeded_new

Can't reproduce, trying with i2prouter start; sleep xxx; timedatectl set-time hh:mm

How long after start are you setting the time, how far are you adjusting the clock, and is it forward or backward?

comment:2 Changed 4 years ago by Reportage

Status: infoneeded_newnew

Try: i2p start && watch -n 10 "sudo ntpdate"
or maybe: i2p start && watch -n 5 "timedatectl set-time wrong:time && sudo ntpdate"

The behavior described was intermittent and was conditional upon crontab job firing at startup to sync the computer's clock with a remote server. Not the easiest of bugs to troubleshoot, but the remote time sync appeared to be the event that caused the router to fail to start, in the event that the system clock was inconsistent with network time.

Version 1, edited 4 years ago by Reportage (previous) (next) (diff)

comment:3 Changed 4 years ago by str4d

Keywords: error heisenbug time added; router clock sync removed
Status: newopen
Note: See TracTickets for help on using tickets.