Opened 5 years ago

Last modified 19 months ago

#10922 needs_information defect

tor connected to bwauth produces lots of pathbias_count_use_attempt BUG messages

Reported by: Sebastian Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.20
Severity: Normal Keywords: tor-client, bwauth, regression bug-message pathbias
Cc: mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm setting up a new bwauth currently. I'm seeing many (~1000 / hour) BUG messages in its logfile:

[notice] Tor 0.2.4.20 (git-0d50b03673670de6) opening new log file.
[notice] pathbias_count_use_attempt(): Bug: Used circuit is in strange path state new. Circuit is a General-purpose client currently open.

The config for the tor process (it is a relay to evade static throttling):

SocksPort 9110
ControlPort 9111
Log notice file ./data/tor/tor.log
DataDirectory ./data/tor
PidFile ./data/tor/tor.pid
CookieAuthentication 1

Nickname gabelmoobwscan

RelayBandwidthRate 20480
RelayBandwidthBurst 20480

OrPort 9999

ContactInfo Sebastian <tor@sebastianhahn.net>

ExitPolicy reject *:*

Child Tickets

Change History (16)

comment:1 Changed 5 years ago by Sebastian

Cc: mikeperry added

comment:2 Changed 5 years ago by nickm

Keywords: tor-client bwauth 024-backport added
Milestone: Tor: 0.2.5.x-final

Note that this is apparently happening in a bwauth. Probably this is a bug in the pathbias code handling controller-managed circuits somehow.

comment:3 Changed 5 years ago by nickm

Keywords: regression added

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

comment:5 Changed 4 years ago by nickm

Keywords: 026-triaged-1 added; 024-backport removed
Status: newneeds_information

comment:6 Changed 4 years ago by Sebastian

What kind of information does this need? Did you flag it as such because you don't want to have to look at it, and someone else should?

comment:7 Changed 4 years ago by arma

moria1's bwauth experiences this bug too.

comment:8 Changed 4 years ago by nickm

What we need to figure out here is... why is this happening? What would help me most is instructions on how to reproduce this, either without running a bwauth, or as some kind of "bwauth lite". Alternatively, if we could stick a proxy between the bwauth and tor to make it log all the control commands, that might help narrow it down too.

comment:9 Changed 4 years ago by mikeperry

If I remember right, this was due to an interaction between __LeaveStreamsUnattached and the pathbias code. There may be other interactions with how the bw auths build their own circuits and attach streams here, too.

It may make more sense just to disable the pathbias code in the bw auths (or perhaps automatically in tor if __LeaveStreamsUnattached is set) rather than trying to make the pathbias accounting work properly in all arbitrary controller-driven situations of custom circuit and stream handling...

At any rate, this is just log noise at this point, until the PathBias code actually does something other than log about low success rates.

comment:10 Changed 4 years ago by mikeperry

Oh, also the bandwidth auths don't use guards, so that's another big thing likely to cause problems here in terms of coming up with a proper, generalized fix.

comment:11 Changed 4 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

comment:12 Changed 2 years ago by teor

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

Milestone renamed

comment:13 Changed 2 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:14 Changed 19 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 19 months ago by nickm

Keywords: 026-triaged-1 removed

comment:16 Changed 19 months ago by nickm

Keywords: bug-message pathbias added
Severity: Normal
Note: See TracTickets for help on using tickets.