Opened 8 years ago

Closed 19 months ago

#2742 closed enhancement (wontfix)

Improved flushing of bw auth scanner log message output?

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

Description

We've gotten a few random crashes for the bw auths without so much as a traceback. This could be due to the oomkiller, but it could also be due to an issue with flushing our log files when we get various exceptions. We should make sure no exceptions can kill us without us flushing first.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by aagbsn

Cc: aagbsn@… added

Any more details here? Does syslog correlate with the oomkiller theory?

comment:2 Changed 8 years ago by mikeperry

No.. I wouldn't worry about this bug until after we deploy the parent/child stuff, though. So far its crashes are always producing logs :)

comment:3 Changed 8 years ago by mikeperry

Priority: majorminor
Summary: Flush Bw Auth scanner output somehowImproved flushing of bw auth scanner log message output?

Demoting priority to keep it off the radar until this shows up again.

comment:4 Changed 8 years ago by mikeperry

Priority: minornormal

No longer minor. We got a logless deadlock in #4015. Not quite a crash, but logless nonetheless.

comment:5 Changed 7 years ago by aagbsn

Keywords: bwauth-logging added

comment:6 Changed 19 months ago by teor

Parent ID: #13630
Severity: Blocker

This is a feature that belongs in the new bwauth replacement project, see #13630.

comment:7 Changed 19 months ago by teor

Resolution: wontfix
Severity: BlockerNormal
Status: newclosed

Actually, it's a bugfix that will be obsoleted etc. etc.

Note: See TracTickets for help on using tickets.