Opened 6 years ago

Last modified 11 months ago

#8962 new defect

pathbias_count_use_attempt strange path state log lines

Reported by: jefnag Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.5.8-rc
Severity: Normal Keywords: tor-client, logging, annoyance, pathbias
Cc: mikeperry, ioerror Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

"pathbias_count_use_attempt(): Bug: Used circuit is in strange path state build attempted. Circuit is a General-purpose client currently open.

Child Tickets

Change History (17)

comment:1 Changed 6 years ago by jefnag

Version: Tor: 0.2.4.7-alphaTor: 0.2.4.11-alpha

comment:2 Changed 6 years ago by karsten

Component: - Select a componentTor
Keywords: tor-client added

comment:3 Changed 6 years ago by nickm

Cc: mikeperry added
Milestone: Tor: 0.2.4.x-final
Status: newneeds_information

Does this occur with more recent Tor versions at all? It looks like some bugs that we fixed since then...

comment:4 Changed 6 years ago by nickm

Resolution: user disappeared
Status: needs_informationclosed

comment:5 Changed 5 years ago by arma

Cc: ioerror added
Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final
Version: Tor: 0.2.4.11-alphaTor: 0.2.5.8-rc

Jake reports seeing these on Tails 1.2, with Tor 0.2.5.8-rc:

He sees a big pile of lines like

Oct 25 23:23:06.000 [notice] pathbias_mark_use_success(): Bug: Used
circuit 416 is in strange path state new. Circuit is a General-purpose client
currently open.
Oct 25 23:23:06.000 [notice] pathbias_count_use_attempt(): Bug: Used
circuit is in strange path state new. Circuit is a General-purpose client
currently open.

He also at one point saw

Oct 25 23:26:24.000 [notice] Short path bias probe response length field (1).

but maybe that is a separate bug.

comment:6 Changed 5 years ago by arma

Resolution: user disappeared
Status: closedreopened

comment:7 Changed 5 years ago by nickm

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

comment:8 Changed 5 years ago by mikeperry

Summary: pathbias_count_use_attemptpathbias_count_use_attempt strange path state log lines

comment:9 Changed 4 years ago by nickm

Status: reopenedneeds_information

comment:10 Changed 3 years ago by hira

Severity: Normal

I am seeing this exact same message while fetching sites using pycurl (with a custom circuit made using stem). I have tor version v0.2.4.27 and the message goes something like this:

Mar 20 16:15:59.000 [notice] Bootstrapped 100%: Done.
Mar 20 16:17:16.000 [notice] New control connection opened.
Mar 20 16:17:19.000 [notice] pathbias_count_use_attempt(): Bug: Used circuit is in strange path state new. Circuit is a General-purpose client currently open.
Mar 20 16:17:20.000 [notice] pathbias_mark_use_success(): Bug: Used circuit 5 is in strange path state new. Circuit is a General-purpose client currently open.
Mar 20 16:17:20.000 [notice] pathbias_count_use_attempt(): Bug: Used circuit is in strange path state new. Circuit is a General-purpose client currently open.


comment:11 Changed 3 years ago by arma

See also #20362 (apparently the bug is still present in Tor 0.2.8.7)

comment:12 in reply to:  10 Changed 3 years ago by teor

Replying to hira:

I am seeing this exact same message while fetching sites using pycurl (with a custom circuit made using stem). I have tor version v0.2.4.27 and the message goes something like this:

Mar 20 16:15:59.000 [notice] Bootstrapped 100%: Done.
Mar 20 16:17:16.000 [notice] New control connection opened.
Mar 20 16:17:19.000 [notice] pathbias_count_use_attempt(): Bug: Used circuit is in strange path state new. Circuit is a General-purpose client currently open.
Mar 20 16:17:20.000 [notice] pathbias_mark_use_success(): Bug: Used circuit 5 is in strange path state new. Circuit is a General-purpose client currently open.
Mar 20 16:17:20.000 [notice] pathbias_count_use_attempt(): Bug: Used circuit is in strange path state new. Circuit is a General-purpose client currently open.


Custom circuits often trigger this bug, because of __LeaveStreamsUnattached 1 (I think, or it's something else to do with control-port based circuit building).
When I am building paths myself, I set UseEntryGuards 0 to work around this.
(This disables the pathbias detector.)
But that doesn't work for the general case.

comment:13 Changed 3 years ago by teor

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

Milestone renamed

comment:14 Changed 3 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:15 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:16 Changed 2 years ago by nickm

Keywords: logging annoyance added
Status: needs_informationnew

comment:17 Changed 11 months ago by traumschule

Keywords: pathbias added

Put open pathbias bugs on the radar of #27879.

Note: See TracTickets for help on using tickets.