Opened 8 years ago

Closed 3 years ago

#5362 closed defect (user disappeared)

If StrictExitNode is set to 1 tor start using 100% cpu after a few minutes

Reported by: Phoenix87 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.2.35
Severity: Normal Keywords: tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

As the title says, I have Tor 0.2.1.30 installed on my system along with a correctly configured polipo. I've noticed that when I manually restrict tor to use a certain set of exit nodes (using StrictExitNodes 1 and endnodes <...>) and restart it, after a few minute it reaches 100% cpu usage. Although tor seems to be still running fine (i can still open websites etc...), I prefer to avoid such a massive load. I then comment those two line out, restart tor, and everything is back to normal.

Is this a bug or just some predictable behaviour?

Thank you.

Child Tickets

Attachments (2)

torrc (7.5 KB) - added by Phoenix87 8 years ago.
my tor configuration. replace <country_code> with a valid country code.
config (3.8 KB) - added by Phoenix87 8 years ago.
the standard polipo configuration file

Download all attachments as: .zip

Change History (17)

comment:1 Changed 8 years ago by Sebastian

Resolution: invalid
Status: newclosed

That indicates a bug, but Tor 0.2.1.30 is obsolete. Please upgrade to an actually supported version (atm 0.2.2.35 or 0.2.3.12-alpha) and reopen this bug if it still occurs.

comment:2 Changed 8 years ago by Phoenix87

Resolution: invalid
Status: closedreopened

comment:3 Changed 8 years ago by Phoenix87

Milestone: Tor: 0.2.1.x-finalTor: 0.2.2.x-final

comment:4 Changed 8 years ago by Sebastian

Please provide more information about your configuration, OS, etc.

comment:5 Changed 8 years ago by Phoenix87

Updated to Version: 0.2.2.35-1~oneiric+1 but problem is still there. I'm using StrictNodes instead of StrictExitNodes, for it seems that the latter has become deprecated with the new release.

Changed 8 years ago by Phoenix87

Attachment: torrc added

my tor configuration. replace <country_code> with a valid country code.

Changed 8 years ago by Phoenix87

Attachment: config added

the standard polipo configuration file

comment:6 in reply to:  4 Changed 8 years ago by Phoenix87

Version: Tor: 0.2.2.35

Replying to Sebastian:

Please provide more information about your configuration, OS, etc.

Please find the configuration files attached to this ticket. I'm running ubuntu oneiric and used the official tor repositories for oneiric.

comment:7 Changed 8 years ago by Sebastian

hrm ok, if it really is UK then there should be a few nodes available. I'll see if I can reproduce it, otherwise you should get ready to profile your Tor to see where it spends its time

comment:8 in reply to:  7 Changed 8 years ago by Phoenix87

Replying to Sebastian:

hrm ok, if it really is UK then there should be a few nodes available. I'll see if I can reproduce it, otherwise you should get ready to profile your Tor to see where it spends its time

Well actually I've tried a few other country codes other than UK, and all seem to lead to the very same issue. I've also tried to manually specify some node nicknames with again the same result.

comment:9 Changed 8 years ago by nickm

Oh hey, if you're on Linux, this should be pretty easy to track down with profiling: just run Tor under 'perf', and see where the cycles are spent. To do this, just run "perf record tor (options)" instead of "tor (options)". Once the CPU has spiked for a while, exit Tor, then use "perf report > output" to get a breakdown of where Tor is spending its time. (I'd do this myself, but I can't make the bug happen: I just tried for about 20 minutes to reproduce with the current maint-0.2.2 branch on my computer, and didn't get any weird CPU issues.)

(BTW, as far as I can tell, "UK" isn't likely to work... the maxmind geoip database thinks that the country code in question is "GB".)

Also, is this

comment:10 Changed 8 years ago by nickm

Status: reopenedneeds_information

comment:11 Changed 8 years ago by arma

Correct, {UK} is not going to get you what you want.

See also #3296 -- I wonder if some info-level logs would help here (in addition to, or instead of, the perf results above).

comment:12 Changed 7 years ago by nickm

Milestone: Tor: 0.2.2.x-finalTor: unspecified

comment:13 Changed 7 years ago by nickm

Keywords: tor-client added

comment:14 Changed 7 years ago by nickm

Component: Tor ClientTor

comment:15 Changed 3 years ago by nickm

Resolution: user disappeared
Severity: Normal
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.