Opened 11 months ago

Last modified 5 months ago

#29245 new defect

Tor 0.4 eventually hits "Delaying directory fetches: No running bridges" after some period of inactivity with bridges

Reported by: ArmalsLoveArmalsLife Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 040-regression, snowflake, 040-deferred-20190220, network-team-roadmap-november
Cc: dcf, cohosh Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor28-must

Description

Tor NOTICE: Delaying directory fetches: No running bridges 
Tor NOTICE: Application request when we haven't received a consensus with exits. Optimistically trying known bridges again. 
Tor NOTICE: Delaying directory fetches: No running bridges 
Tor NOTICE: Application request when we haven't received a consensus with exits. Optimistically trying known bridges again. 
Tor NOTICE: Delaying directory fetches: No running bridges 
Tor NOTICE: Application request when we haven't received a consensus with exits. Optimistically trying known bridges again. 

Tested on latest Tor Browser alpha with snowflake bridge.

Child Tickets

Change History (11)

comment:1 Changed 10 months ago by nickm

Keywords: 040-regression snowflake? added
Milestone: Tor: 0.4.0.x-final

Does this happen only with snowflake, or non-snowflake?

comment:2 in reply to:  1 Changed 10 months ago by ArmalsLoveArmalsLife

Replying to nickm:

Does this happen only with snowflake, or non-snowflake?

I'm in a censored area for the moment so I can't answer that question (meek is a no-no since it's too damn slow).

comment:3 Changed 10 months ago by ArmalsLoveArmalsLife

One note though: It's not an issue with the snowflake server since all it takes for me to get Tor working again is to just restart the browser and then it immediately works again.

comment:4 Changed 10 months ago by nickm

Keywords: 040-deferred-20190220 added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

Deferring 51 tickets from 0.4.0.x-final. Tagging them with 040-deferred-20190220 for visibility. These are the tickets that did not get 040-must, 040-can, or tor-ci.

comment:5 Changed 10 months ago by ahf

Sponsor: Sponsor19

comment:6 Changed 10 months ago by dcf

Cc: dcf added
Keywords: snowflake added; snowflake? removed

Adding the "snowflake" keyword because while this situation can arise with any kind of transport/bridge, it's more likely to happen with snowflake because snowflake is more likely to drop connections and make tor think its connection is unreliable.

I don't think this is a regression; I've managed to get tor into a loop of Delaying directory fetches: No running bridges many times in the past while testing other pluggable transports. It's likely that the preceding log message was

[warn] Your Guard flakey ($2B280B23E1107BB62ABFC40DDCC8824814F80A72) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug.

comment:7 Changed 10 months ago by cohosh

Cc: cohosh added

comment:8 Changed 6 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:9 Changed 6 months ago by phw

Sponsor: Sponsor19Sponsor28-can

Moving from Sponsor 19 to Sponsor 28.

comment:10 Changed 5 months ago by gaba

Keywords: network-team-roadmap-november added; ex-sponsor-19 removed
Sponsor: Sponsor28-canSponsor28-must

comment:11 Changed 5 months ago by cypherpunks

By the way this still happened lately.

Note: See TracTickets for help on using tickets.