Opened 6 months ago

Last modified 5 weeks ago

#30352 new defect

Tor fails to recover if it was started with incorrect date settings

Reported by: Vort Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.4.0.3-alpha
Severity: Minor Keywords: tor-guard, 041-deferred-20190530, 042-deferred-20190918
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

After power failure, I accidently set date to 05.02.2019 instead of 02.05.2019.
It is ok that Tor can't work with such misconfiguration.
But problem is that it was not able to work even after correct date was restored.
Last lines in log are:

May 02 01:57:41.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
May 02 02:01:09.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
May 02 02:01:09.000 [notice] Our circuit 0 (id: 63) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configuration issue, or a bug.
May 02 02:05:47.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
May 02 02:10:27.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
May 02 02:15:08.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
May 02 02:20:16.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.

Related ticket: #8766.

Child Tickets

Attachments (1)

notices.log (16.5 KB) - added by Vort 6 months ago.
Full log

Download all attachments as: .zip

Change History (5)

Changed 6 months ago by Vort

Attachment: notices.log added

Full log

comment:1 Changed 6 months ago by dgoulet

Keywords: tor-guard added
Milestone: Tor: 0.4.1.x-final

There was a clock correction:

May 02 01:57:31.000 [warn] Your system clock just jumped 7430399 seconds forward; assuming established circuits no longer work.

Now what I wonder if why tor never was able to pick a Guard after the clock correction... ?

comment:2 Changed 5 months ago by nickm

Keywords: 041-deferred-20190530 added

Marking these tickets as deferred from 041.

comment:3 Changed 5 months ago by nickm

Milestone: Tor: 0.4.1.x-finalTor: 0.4.2.x-final

comment:4 Changed 5 weeks ago by nickm

Keywords: 042-deferred-20190918 added
Milestone: Tor: 0.4.2.x-finalTor: unspecified

Deferring various tickets from 0.4.2 to Unspecified.

Note: See TracTickets for help on using tickets.