Opened 3 months ago

Last modified 2 months ago

#31707 new defect

Better handling and UX for missing and expired guard descriptors

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.0.1-alpha
Severity: Normal Keywords: log, tor-guard, tor-bridge, tor-client
Cc: catalyst Actual Points:
Parent ID: #21969 Points:
Reviewer: Sponsor:

Description (last modified by teor)

Split off #31657:

Replying to teor:

How do we reliably detect pathological cases?
Suppress the message, until it occurs a few times within a short timeframe?

dgoulet:

That's a good question I don't have an answer for.

Unfortunately, I don't think that's the kind of message that occurs multiple times, looking at #30746 (and friends) this seems to be able to cause havoc with just a single repeatition.

I'm not sure why this is the case, since router_have_minimum_dir_info() seems to be called all the time and that should eventually call entry_guards_get_err_str_if_dir_info_missing() which is the source of the log message... Things are kinda messy between these two functions tho, so it's kinda hard to understand what's the issue.

Child Tickets

Change History (2)

comment:1 Changed 2 months ago by teor

Keywords: fast-fix BugSmashFund 042-should removed
Version: Tor: 0.3.3.1-alphaTor: 0.3.0.1-alpha

comment:2 Changed 2 months ago by teor

Description: modified (diff)
Note: See TracTickets for help on using tickets.