Opened 8 years ago

Last modified 2 years ago

#4079 new enhancement

Comb bw auth logs and fix or demote frequent ERRORs and WARNs

Reported by: mikeperry Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords: bwauth-logging
Cc: #4445 Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Apparently the bw auths are noisy, and log several connection issues as ERROR and WARN, when they probably should be NOTICE.

However, some of them might represent more serious issues, such as nodes improperly being chosen as exits:
ERROR[Wed Sep 21 20:48:40 2011]:An unknown HTTP error occured
Socks5Error: (2, 'connection not allowed by ruleset')

So some care should be taken, rather than just demoting everything.

Child Tickets

TicketTypeStatusOwnerSummary
#24216defectreopenedtomMake p global in the sigterm handler
#24219defectneeds_revisionAvoid aggregate.py error when no nodes are measured
#24224defectnewtomWhen a bwauthority circuit fails, it is very noisy
#24242defectnewtomResolve warnings on NEWCONSENSUS / NEWDESC events

Change History (5)

comment:1 Changed 8 years ago by aagbsn

Keywords: bwauth-logging added

comment:2 Changed 2 years ago by teor

Cc: #4445 added
Severity: Normal

Needs to be done for #4445.

comment:3 Changed 2 years ago by teor

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:4 Changed 2 years ago by teor

Owner: aagbsn deleted
Status: newassigned

aagbsn was the default owner, unassigning

comment:5 Changed 2 years ago by teor

Status: assignednew

Mark all tickets that are assigned to nobody as "new".

Note: See TracTickets for help on using tickets.