Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#3826 closed defect (fixed)

fluxe3 reports 0 observed bandwidth in its descriptor

Reported by: Sebastian Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: #3561 Points:
Reviewer: Sponsor:

Description

fluxe3 might not have lost the fast flag due to switching to filtering bufferevents, but rather because it stopped reporting observed bandwidth higher than 0. I assume in the beginning this still worked because it still had some bw in its state file, and now it doesn't. More investigation necessary

Child Tickets

Change History (7)

comment:1 Changed 7 years ago by Sebastian

Yes. My statefile says:

BWHistoryReadEnds 2011-08-26 15:45:14
BWHistoryReadValues 0
BWHistoryReadMaxima 0
BWHistoryWriteEnds 2011-08-26 15:45:14
BWHistoryWriteValues 0
BWHistoryWriteMaxima 0
BWHistoryDirReadEnds 2011-08-26 15:45:14
BWHistoryDirReadValues 0
BWHistoryDirReadMaxima 0
BWHistoryDirWriteEnds 2011-08-26 15:45:14
BWHistoryDirWriteValues 0
BWHistoryDirWriteMaxima 0

comment:2 Changed 7 years ago by Sebastian

(even after reverting back to non-filtering bufferevents and running for 10 hours or so)

comment:3 Changed 7 years ago by nickm

Oh, hm. Maybe #3803 is to blame here. Need to investigate that.

comment:4 Changed 7 years ago by nickm

Resolution: fixed
Status: newclosed

The #3803 fix should have fixed this too . Please reopen if it hasn't. :)

comment:5 Changed 7 years ago by Sebastian

Yup, this is fixed. The statefile is getting new bandwidth entries.

comment:6 Changed 6 years ago by nickm

Keywords: tor-relay added

comment:7 Changed 6 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.