Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#1882 closed defect (fixed)

"Failed to find node for hop 0 of our path. Discarding this circuit." log spam after guard went down

Reported by: Sebastian Owned by:
Priority: High Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I noticed this issue with my torperf setup. A tor client that is started with a single node allowed as entry node will freak out if that entry guard goes offline, however briefly.

It keeps logging "Failed to find node for hop 0 of our path. Discarding this circuit." repeatedly, and doesn't seem to recover well at all. I wonder if that means that we are also willing to give up on guards in a regular setup as soon as they go down once, and stop using them.

This might be related to issue #675

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by arma

Milestone: Tor: 0.2.2.x-final
Priority: normalmajor
Status: newneeds_review

Check out bug1882 in my arma.

Marking as 0.2.2.x milestone since I plan to use some of this patch for my #1090 hacks.

comment:2 Changed 9 years ago by arma

See bug1882_2 after comments from nickm

comment:3 Changed 9 years ago by arma

nickm merged it. Leaving open for a bit in case Sebastian wants to take a look first.

comment:4 Changed 9 years ago by Sebastian

Resolution: fixed
Status: needs_reviewclosed

looks sane to me.

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.