Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#20177 closed defect (implemented)

When checking existing fallbacks, report those fallbacks at warning log level

Reported by: teor Owned by: haxxpop
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Fallback Scripts Version: Tor:
Severity: Normal Keywords: fallback, tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:


When the fallback script excludes some relays, it only logs at info level. This is usually what we want, but when checking existing fallbacks, it would be great to see any message about those fallbacks at WARNING log level.

This would make it easier to work out why fallbacks are broken.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by teor

We should also do this for new (candidate/potential) fallbacks.

Last edited 4 years ago by teor (previous) (diff)

comment:2 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:3 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:4 Changed 4 years ago by haxxpop

Owner: set to haxxpop
Status: newassigned

comment:5 Changed 4 years ago by haxxpop

Status: assignedneeds_review

comment:6 Changed 4 years ago by haxxpop

The patch is in the attachment of #20174. I'm not sure whether this patch also solves #20178.

comment:7 Changed 4 years ago by haxxpop

Resolution: implemented
Status: needs_reviewclosed

comment:8 Changed 4 years ago by haxxpop

Component: Core Tor/TorCore Tor/Fallback Scripts
Note: See TracTickets for help on using tickets.