Opened 18 months ago

Last modified 15 months 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:

Description

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.

Subtickets (add)

Change History (3)

comment:1 Changed 18 months ago by zzz

  • Status changed from new to infoneeded_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 18 months ago by Reportage

  • Status changed from infoneeded_new to new

The system clock iirc was about 10 minutes behind before network sync, enough for a warning to appear in the logs, due to a hardware fault.

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

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.

Last edited 18 months ago by Reportage (previous) (diff)

comment:3 Changed 15 months ago by str4d

  • Keywords error heisenbug time added; router clock sync removed
  • Status changed from new to open
Note: See TracTickets for help on using tickets.